Stocking and deliveries are easy to read as separate chores, but Shift At Midnight ties them to customer service and survival. The Steam Store says you keep shelves full, take deliveries, keep the store clean, and sell enough products to meet each night’s quota. Use that official loop as the goal, then build a route that lets you return to the customer and the computer without crossing a blind corner every time.
Start with the task that can interrupt you
Before carrying a delivery or walking to a far shelf, look at the counter and the current customer prompt. Complete a check that is already in progress, or tell a teammate you are leaving it. A physical task can wait a few seconds; an identity decision that is half-read may not be recoverable from memory. In solo play, put the task in a short mental queue: customer decision, immediate objective, physical action, return.
Do not assume the first visible box or shelf is the correct next target. Read the objective, interact, and confirm that the game accepted the action. If it did not, return to the prompt rather than wandering around until another object seems plausible. This reduces false reports about missing deliveries and keeps the guide honest when an update changes interactions.
Make one repeatable loop
- Read the current store objective and identify the destination.
- Finish the customer or database check if one is active.
- Walk along the route with the clearest view of entrances and return paths.
- Complete one stocking or delivery interaction and confirm its result.
- Return to the service area before taking another distant task.
The order is a control method, not an official quest sequence. If the interface calls for an urgent delivery, follow it; the guide does not invent a fixed clock or quota. The important part is returning to a familiar position after each task so you know where to go when the game stops being a normal shop simulation.
When playing with teammates
Use short calls such as “delivery route,” “customer waiting,” and “database check.” One player can handle a physical objective while another remains available for a customer, but the roles should be explicit. Proximity chat is an advertised feature; its exact range and audio behavior should be tested in the current build. Do not assume a teammate saw the same ID or prompt you saw.
A second player can also serve as a route check. Ask them whether an aisle, door, or hiding place is reachable before the store becomes unsafe. This is better than assigning a permanent “runner” role that ignores what the current shift actually asks for.
Recovery after a missed task
If stocking did not register, read the interaction again and check whether the item belongs to a different shelf or objective state. If a delivery disappeared, record what the game displayed, the shift, and the branch before calling it a bug. Official announcements include bug and crash fixes, so a reported problem is useful only when it contains the current context.
If a creature has already escaped, stop debugging the shelf. Move to Survival and tell your team what you were doing when the transition happened. A perfect quota is not useful if the route leaves everyone trapped behind a delivery or a shelf.
What is deliberately not fixed here
The public Store page does not publish exact shelf counts, delivery rewards, prices, quota values, or timing. Do not copy a number from the separate Multiplayer Demo or a dated video and present it as the base-game rule. Recheck live values after the next official patch, especially when the update mentions new weapons, customers, or balancing.
Handoff before leaving the shelf
Before walking away from a box or shelf, call out what is complete and what remains. The next player can then continue the task without assuming that a partial delivery or cleaning interaction is finished. Keep this handoff short when a customer is waiting, because the detective check may be more time-sensitive than a routine shop action.