Help Index → Working with inventories → Use case 35
Separate the six supported item categories into six dedicated containers using explicit category destinations rather than the legacy Sorter’s target lists.
Before you start
- Load the intended save and confirm its active Main or Expedition context. Make a full backup before changing data.
- Before sync, formatting or structured refresh, copy EACH pending Raw JSON pane to its own external file: one sync can overwrite all others. Reapply non-inventory edits one pane at a time, syncing and comparing exact values before the next. Parse errors can leave an old tree with green status; [] is ignored, and Pretty Print can erase invalid text.
- Do not sync/Pretty Print Inventory Raw JSON: dictionary assignment is defective. Use Organizer for supported moves or Replace Items from Backup for supported replacement.
Steps
- Preserve EACH pending pane externally before refresh: one sync can overwrite the others. Reapply non-inventory edits one pane at a time, syncing and verifying exact values. Stop after parse errors even if green; [] is ignored and Pretty Print may erase invalid text. Use structured tools, never defective Inventory Raw JSON sync/Pretty Print. (control reference)
- If Inventory Organizer is not already open, choose Inventory Processing → Node View → Inventory Organizer before using the dialog controls below. (control reference)
- Click Mobile Storages to check Exosuit, Freighter, Fish Platform and available starships. Leave all stationary source boxes unchecked. (control reference)
- Choose Resources → Container 1, Crafted products → Container 2, Technology → Container 3, Consumables → Container 4, Trade goods → Container 5 and Special items → Container 6. (control reference)
- Uncheck Overflow: if destination is full, overflow to other 'Container' type storages. Uncheck Expand all Destination storages to 120 cells. Each category will use only its assigned container’s existing free cells. (control reference)
- Click Review Moves. Check the source/category/destination lines, then click Apply to app data if the proposed separation is wanted. (control reference)
Expected result
- Each original record is classified by its saved InventoryType, not its displayed item name.
- Container contents already present are not automatically removed or reorganized just because that container receives a category. Full destinations can leave records in the mobile sources.
What changes, and when to save
Review Moves changes no inventory data. Apply to app data publishes the reviewed candidate in memory, marks it modified and closes the dialog. File → Save is separate and writes the loaded save target. Organizer preferences persist even when Close cancels the proposal; neither a review nor preferences create a save backup. Before a live write, compare every intended edit with its preserved copy; a refreshed pane can hide lost pending work.
Check the result
- Inspect all six containers after applying and inspect source inventories for retained stacks. Confirm no incorrect category destination was inherited from preferences.
Important details and recovery
- Use this example only when Containers 1–6 appear as available destinations; unavailable inventory records are not created.
- Parts counts are stack records, not the total units inside them. Assigned containers are excluded from overflow if overflow is later enabled.