Operating a dark store: from choosing the location to the first shift

What changes in the working day?

In a conventional shop, the customer selects products and takes them to checkout. In a dark store, the team performs that selection: receiving an order, locating items, checking quantities, packing and handing over for delivery. Space should support those tasks rather than maximise presentation to browsing shoppers.

That does not make the operation merely a warehouse. A warehouse may handle large receipts and bulk movements, while local fulfilment involves varied baskets and frequent handoffs. Storage capacity can be adequate while the packing point becomes congested. A product can be recorded correctly but awkward to reach during a live order.

Think of the location as a sequence of actions. Goods arrive, are checked, are stored, are picked, are reviewed and leave. Each transition needs information and responsibility. Sketch the sequence before buying shelving or selecting software.

A platform can organise records; it cannot widen a narrow aisle or remove the disruption caused by a poorly placed packing table. Designing the physical and information flows together is a better starting point than expecting the software to compensate for an unsuitable layout.

Should you start in your existing shop?

Start with the problem you want to solve. If digital demand can be handled inside the current site, a defined picking route, packing space and driver handover may be enough to test the channel. If walk-in traffic and preparation repeatedly obstruct one another, examine a different layout or separate space before assuming a complete move is necessary.

Do not reduce the comparison to expensive rent versus cheap rent. A cheaper location might add travel, complicate goods receipt or require equipment. An existing site may appear to have no new cost while consuming staff time that was previously used elsewhere. Record the resources each option uses.

Write down what should improve and how you will recognise it. Otherwise, a larger location can simply provide more room for the same unresolved process.

How do you assess a location through the order journey?

Start with the customers and area you intend to serve, then evaluate locations that fit. Choosing the premises first can tempt you to create an oversized service area to justify it. Review access, departure routes, receiving arrangements, driver waiting and how the address is described.

Inside the premises, check whether the different activities can be organised sensibly. Products requiring specialised storage or handling need assessment by the appropriate specialists. A photograph or a label such as “suitable for quick commerce” does not establish that a location meets your activity’s needs.

Walk through a hypothetical receipt. Where does the delivery stop? Where are items checked? How do they reach storage? Then walk a picked order towards packing and dispatch. If the routes converge at one point, consider what happens when several people use it together.

This guide describes operating questions, not licensing or technical storage specifications. Review the applicable requirements with qualified people before committing to premises or equipment. The location should fit the repeated journeys and activities, not just look close to customers on a map.

How should receiving, storage and packing connect?

Give incoming goods a recognisable place before they become available stock. This separates arrival from verification and storage. If everything goes straight onto shelves, discovering a difference later makes it harder to identify whether it came from the supplier, counting or recording.

Make storage locations describable. An aisle, shelf or position convention can help someone cover a colleague’s task without relying on personal memory. If an item moves, update the way the team finds it. This might be a simple operating method or a supported system function; do not assume every platform includes location management.

Picked orders need separation and identification. Products waiting for customer approval should not be indistinguishable from a completed order. Decide where each state belongs and how a colleague recognises it.

Test the arrangement with real movement before treating the drawing as final. Consider someone carrying a box, another person moving in the opposite direction and a driver waiting for handover. These practical interactions can expose issues that are invisible in a clean diagram. Improve the route before asking the team to work around permanent obstacles every day.

What product information is needed before the first order?

A product name alone rarely defines what the customer and picker need to agree on. Pack size, unit, relevant brand information, image and price should describe the same item. A picture of one unit does not establish that a case is being sold. Start with products that can be presented unambiguously.

Review the relationship between purchasing and selling units. You may receive a case and sell individual pieces. If the team records cases as pieces, the stock number can look plausible while representing something different. Weighed products require an explicit review of weight, final price and settlement rather than assuming a unit-price workflow covers them.

Assign responsibility for prices and availability. Where several channels or systems exist, identify the source of truth and how changes reach the others. Maintaining one list while leaving another unchanged creates a service promise the operation may not support.

Check a sample after entry. Can somebody who did not write the description choose the correct item? Does the size make sense in both languages? Use the grocery app launch guide for preparation and the inventory product page to review the current platform’s scope.

How do you record receipts, loss and returns?

Separate physical arrival from an accepted quantity in the record. The receiving person follows your checking procedure, records what was accepted and identifies any unresolved difference. A useful movement record explains why a balance changed, rather than only showing the balance afterwards.

Loss or damage also needs a defined route. Leaving an unsaleable item among available products and relying on everyone to remember it is fragile. Decide where it goes and who records the movement. Product safety or suitability decisions belong to the relevant qualified people; this guide does not establish whether an item can be resold.

A return is not automatically a stock increase. The product may need inspection or another action under the activity’s policy. Test how the returned order, settlement and quantity relate. A button’s name does not explain every consequence of using it.

Review recurring discrepancies by item, unit, location and timing. Correcting the number may fix today’s display but leave the underlying cause untouched. The inventory accuracy guide develops that distinction between reconciliation and prevention.

How do you organise picking and packing?

Define when an order is accepted for picking and who takes ownership. Give the picker a way to see what is needed and what remains. If a decision is outstanding, make that status visible rather than allowing the order to disappear from attention while another task is started.

Check the match between the requested item and the selected one. Similar packaging, a different size or the wrong quantity can survive several handoffs if nobody has a clear checking responsibility. Choose a process suited to your operation. Do not assume barcode scanning or automatic validation is available without seeing it in the proposed version.

Packing is a working stage with requirements determined by the products. Maintain order identification and a clear distinction between completed and unresolved orders. At driver handover, agree who checks the order reference and the bags or units being transferred.

If you want to collect several orders in one picking round, test separation and review before adopting the method. Less walking is not useful if products are mixed between baskets. The order preparation guide gives a more detailed view of the handoffs to examine.

Who owns each task during the shift?

One employee may perform several roles, but a task should not have an undefined owner. Identify acceptance, picking, customer issue handling, delivery assignment and stock investigation. Give each a backup when the responsible person is absent or busy.

At handover, review open orders, products requiring attention and issues awaiting an external response. “It is all in the messages” is insufficient if the next team does not know where to begin. Write the information so another person can act on it without reconstructing the conversation.

Training means performing these tasks, not watching a tour once. Ask the team to complete a normal journey and one involving a shortage or delay. Use the merchant portal demonstration to distinguish supported functions from the responsibilities your operation defines.

How does the site connect to realistic delivery coverage?

Coverage begins at the location actually preparing the order. With several sites, establish which serves each address and what happens when stock exists in one but not another. Total company stock should not be treated as locally available without a workable allocation and fulfilment process.

Test representative addresses instead of only the nearest, easiest journey. Review departure, travel and handover, including the time a driver waits for an incomplete order. Reducing preparation waiting may matter more than adding delivery capacity; a difficult service area may require a different response.

Specify what happens with an incomplete address or one outside coverage. Test what the customer sees, what the store team knows and what reaches the driver. A small information gap can create repeated calls during fulfilment.

Service boundaries, charges and estimates should follow those observations. The delivery-area guide connects geographical setup with operating time and responsibilities. Avoid offering the same promise everywhere simply because the map can display a larger shape.

How do you test before announcing the launch?

Run a controlled rehearsal that does not unintentionally charge customers or send them messages. Include a simple basket, a varied basket, an unavailable item and an appropriate address or order change. Record where the process stopped, why it stopped and who needed information they could not find.

Do not judge success only by a bag reaching its destination. The owner may have intervened at every stage, hiding the fact that the team cannot repeat the process independently. Check whether a backup person can work from the available information and whether decisions can be traced afterwards.

Fix the barriers to a stable basic journey before adding more products or areas. Keep a short issue list with an owner, next action and evidence needed to close it. A supplier response or internal approval still outstanding should remain visible as an unresolved dependency.

There is no universal rehearsal that guarantees success. Your tests need to represent your products, team and delivery model. The purpose is to expose uncertainty early enough to address it, not to produce a ceremonial launch checklist with every box ticked.

What should you review before expanding?

Ask about the last order that required unusual intervention. Reconstruct what information appeared, what was missing, who decided and where the decision was recorded. This is more precise than asking whether people “like the system,” and may reveal a training or process issue rather than a missing feature.

Look for waiting, repeat errors, stock discrepancies and difficulty locating products. Congestion around one table suggests a different problem from repeated questions about pack size. Both can appear as slow orders, but require different corrective actions.

Choose a defined change and check its result. Relocating frequently picked products, clarifying receipt ownership or identifying held orders are examples to assess against your operation, not guaranteed sources of a particular saving.

Brocli operates its own dark store, which shaped the platform. That experience does not make every practice in this guide a confirmed software feature. Illustrations are not photographs of the operating site. In a dark-store platform discussion, separate the current technology, project setup and the premises, stock and team you operate yourself.

What belongs in a practical opening and closing routine?

Before a shift, check the items the team needs to begin: access to the working interfaces, a clear preparation area, known unresolved orders and the current service arrangement. The routine should reflect your actual responsibilities and product requirements rather than a generic checklist copied without review.

At closing or shift change, identify what remains unfinished. Record whether an issue needs a customer response, a stock check or a supplier action, and name the next owner. Avoid marking work complete merely because the current employee’s shift has ended.

Keep the routine short enough to use and specific enough to expose a problem. Review it when the operation changes. A document nobody follows provides less protection against confusion than a small set of actions the team can explain and repeat.