Start with four non-destructive checks
COMMUNITY WORKFLOW Most missing-item reports are placement or visibility problems, not proof that the save is damaged. Work through the current map once without relocating a finished aisle.
Confirm the map and count. The original map, Dream Convenience Store, and Super Super Supermarket use different inventories. A guide for one map cannot certify another.
Read every unresolved tag. White suggests a correct but incomplete shelf. Red suggests a category or shelf mismatch. Yellow indicates completion in the community-documented tag system.
Scan floors, corners, and handoff zones. Check behind product piles, near spawn points, around furniture, and wherever multiplayer teammates leave uncertain products.
Use a known product as the key. Hold or select a matching family, then use Match Finder, Request More, or Shelf Finder if those skills are available.
Diagnose the tag before moving stock
| What you see | Likely meaning | Next move |
|---|---|---|
| White tag | Correct shelf, not complete | Search for more matching products before reorganizing. |
| Red tag | Wrong shelf or wrong section | Recheck the category directory and exact label. |
| Yellow tag | Community-documented completed shelf | Leave it alone and inspect unresolved shelves. |
| No loose product visible | Hidden, carried, misplaced, or save-state issue | Check players and floor zones, then save recovery. |
Check every player in multiplayer
Only the host save keeps multiplayer progress. Before calling a product lost, ask every guest to empty carried items into an agreed handoff area and stop moving the affected family. Let the host inspect the unresolved tag and verify the save after the team exits.
Run the checklist from the host's continuing save. A guest opening a separate run may see a different store state; that is expected under the official host-only save rule. Ask the host to note the last completed shelf, the unresolved tag color, and the moment the session was saved. Those details make an earlier backup easier to identify without trial-and-error overwrites.
Recover progress without risking the save
OFFICIAL Patch 1.1.3 introduced a backup selection function. On patch 1.1.6, update the game, close active multiplayer sessions, and look for the built-in backup choice before editing or replacing files. Confirm Steam Cloud state as a second safety check.
Stop and preserve the current state. Do not repeatedly overwrite a questionable run.
Open the game's backup selector. Choose a known earlier state using the built-in recovery route.
Check Steam Cloud synchronization. Resolve any sync prompt deliberately before relaunching.
Verify the map and shelf count again. A restored save can return you to an earlier completion point.
When to report a reproducible bug
If the same product remains absent after restoring a known backup, capture the patch number, map, player count, tag color, approximate aisle, and whether the run was hosted or solo. That evidence is more useful than a general “last item missing” report.
Use current Steam discussions for a reproducible patch 1.1.6 case. Keep the original save intact and avoid circulating old workarounds as universal fixes for missing products. Include a short reproduction sequence: load the named map, visit the affected section, show the tag, repeat the finder action, and state whether restoring the selected backup changed the result. Never upload a personal save unless you understand what it contains and the recipient is a trusted support channel.
For Supermarket Chaos missing items, the strongest report identifies the exact map, the host, the unresolved shelf color, and the last recovery step that produced the same result.