Black Friday Janitor Organization Guide

Black Friday Janitor contains more than 21,000 products to return, spread across many stores with different product ranges. At that scale, a bad organizational habit creates more work than a slow pickup speed.

The safest rule is: preserve location context until you are confident about the destination.

Use three product states

State	Meaning	Action
Obvious match	Store and shelf family are clear	Place it during the current pass
Likely match	Store seems right, shelf placement is uncertain	Keep it in a local staging group
Unknown	Destination is not supported by nearby context	Record it and do not carry it far

The goal is not to be cautious forever. It is to delay only the decisions that would be expensive to undo.

Why local context matters

The official Steam page says the mall contains multiple stores with their own ranges of products.

Player reports add a useful pattern: items generally appear in or near the store they belong to. That is not a developer-published radius, so the wiki does not claim an exact distance, but it supports a practical search rule:

search local before global.

If a product is confusing, first inspect:

• the store where it was found;
• the entrance area;
• neighboring shelves;
• nearby corridor spillover;
• your local uncertainty pile.

Only widen the search after those options are exhausted.

Build one uncertainty queue per active zone

An uncertainty queue is a deliberate temporary group, not a random pile.

Keep it:

• inside or directly beside the active store;
• away from obviously completed shelf rows;
• small enough to review in one pass;
• separate from products belonging to another store.

When obvious items are finished, the remaining shelf pattern often makes uncertain items easier to identify.

If the queue keeps growing, stop moving uncertain products. Continue rubbish, spills or fallen objects instead, then return with more context.

Use departments inside large stores

Stores such as Gilberts or Peers are large enough that “the whole store” may be a poor working unit.

Use smaller boundaries:

• one signed supermarket department;
• one aisle face;
• one department-store section;
• one fixture cluster;
• one room in the cinema.

Finish one boundary before opening another. This makes the uncertainty queue local and prevents the store from becoming one giant mixed inventory.

How Gather changes organization

The developer’s v1.0.4 patch notes say Gather became much less likely to pull from another store for the few items that are shared across stores.

Two conclusions follow:

1. some items can be shared across stores;
2. Gather’s selection became safer, but not described as perfectly store-isolated.

So Gather should support organization, not replace identification.

A better sequence is:

1. identify the active store/department;
2. understand the local shelf families;
3. Gather;
4. place obvious items;
5. isolate ambiguous items;
6. move on only after the group is resolved or deliberately staged.

See the abilities guide for the exact limit of what the patch note confirms.

Color is useful, but not absolute proof

Patch v1.0.4 changed affected color variants to distribute evenly in new runs. Existing saves keep their original generated colors.

That means an uneven row in an older save is not automatically wrong.

Patch v1.0.5 also changed normal shelf placement to work back-to-front unless the item has multiple colors. Old videos may therefore show a different placement sequence.

Use color to organize a known product family, not to guess which store an unknown product belongs to.

The color sorting guide covers new-save and old-save differences.

A practical store workflow

Pass 1 — survey

Identify shelf families, department signs and the local staging spot.

Pass 2 — obvious products

Place only high-confidence matches.

Pass 3 — likely products

Compare the remaining shelf gaps and local product groups.

Pass 4 — unknown queue

Resolve what can now be supported. Leave unresolved products grouped rather than spreading guesses.

Pass 5 — store audit

Walk the entrance, endcaps and boundaries, then check remaining rubbish/spills/fallen objects before treating the store as complete.

How to handle products near two stores

Do not decide from distance alone.

Record:

• where the product was found;
• which storefronts are nearby;
• whether the same item appears on a known shelf;
• whether Gather behavior suggests a store context;
• whether the item is one of the shared-item cases.

If the evidence is still ambiguous, leave the item local until the route naturally returns.

Long-session organization

Before ending a session:

• finish one aisle/department if possible;
• consolidate unknown items into one marked group;
• note the next shelf or sign to resume from;
• avoid leaving several stores half-sorted;
• wait for normal save/sync behavior.

This is especially useful because the official description explicitly says not to expect the whole mall to be finished in one go.

Evidence and limitations

Developer-published: stores have their own product ranges; abilities can speed cleanup. Developer patch evidence: v1.0.4 says a few items are shared across stores and Gather was adjusted; v1.0.4 changes color generation for new runs; v1.0.5 changes shelf placement ordering. Player-reported: products generally remain local to their store. Editorial method: obvious / likely / unknown states and local uncertainty queues.

The wiki does not claim a complete per-store inventory until product/store/shelf data can be reproduced directly.

Sources: official Steam store, official Steam Community updates and source-linked store guides.

Use the items hub when the remaining question is about product evidence rather than route order.