Buyer checklist · 3 August 2026
Quick-commerce fulfillment centre checklist: qualify the provider before launch
Quick commerce often needs stock to move from a warehouse into small local sites, often called dark stores. The hard part is not the label. It is doing each purchase order, pack, booking, handoff, and record in the required way.
| Stage | Buyer action | Proof |
|---|---|---|
| Map | List goods, sites, and order rules | Written input pack |
| Walk | Trace one purchase order | Process map |
| Test | Run agreed cases | Results and issue log |
| Decide | Review fit and open risks | Signed scope |
Start with demand
Define the job before you shortlist a provider
Write the job in plain terms. List the goods, source site, target dark-store sites, purchase-order source, order frequency, unit and case rules, label needs, shelf-life or batch fields, booking steps, transport owner, and proof needed after handoff. Mark any field that is not yet known instead of asking providers to guess.
Separate work the provider must do from work owned by the brand, a carrier, or the buying channel. A warehouse may prepare goods but not book the slot or run the transport. Another may accept the full flow only after a review. The contract and process map must show each handoff rather than use broad words such as “end to end.”
Goods and stock
Check whether the site can handle the real SKU profile
Share item names, dimensions, weights, pack sizes, case rules, batch or lot needs, expiry fields, storage needs, and damage risks. Do not assume that general ecommerce storage covers food, beauty, fragile, high-value, temperature-sensitive, regulated, or oversized goods. Ask for a clear accept, reject, or review status for each item group.
Ask how stock for quick-commerce orders is held and reserved. Find out which record is the source of truth, when changes are posted, and who reviews a mismatch. If the same stock pool also serves website or marketplace orders, define the rule that stops one channel from using stock meant for an open purchase order.
Order intake
Trace a purchase order from arrival to release
Walk through one real or masked purchase order. Note how it arrives, who checks it, which fields are needed, and what happens when a SKU, quantity, price field, site code, or date is unclear. A named software tool does not show that this exact document and workflow can pass without manual work.
Set a rule for late, changed, cancelled, duplicate, or partly filled orders. The provider should show who can approve a change and how the brand sees it. Agree on the record that confirms the final order released to the floor. Without that step, a clean pick can still be wrong against the buyer’s latest request.
Floor work
Review pick, case pack, label, and quality steps
Turn each buyer rule into a work instruction that a warehouse worker can follow. Show the unit of measure, inner and outer pack, case quantity, labels, placement, barcodes, batch fields, expiry checks, and any site-specific marks. Use approved samples when appearance or label position matters. Keep version numbers on the instruction and sample.
Ask where checks happen and what proof remains. Some checks may be by item, case, order, or sample, but the method should match the risk and written scope. Define what happens when stock is short, a code will not scan, a label is wrong, a case is damaged, or the order misses a buyer rule.
Provider scorecard
Use the same questions for every provider
| Area | Question | Evidence to request | Decision |
|---|---|---|---|
| Goods | Which SKUs and storage needs can the site accept? | Item-level scope and limits | Accept, reject, review |
| Purchase orders | How are new, changed, and cancelled orders handled? | Walkthrough and sample record | Clear or open |
| Packing | Can case, label, batch, and expiry rules be followed? | Work instruction and test pack | Pass or revise |
| Booking | Who books each receiving slot and handles change? | Role map and issue path | Owned or unknown |
| Dispatch | Who arranges transport and checks handoff? | Dispatch checklist and proof | In or out of scope |
| Exceptions | What happens after a short fill or rejected load? | Issue log and owner | Agreed or open |
| Records | How do stock, order, and receipt records agree? | Sample report and review rule | Tested or untested |
Booking and handoff
Name the owner of every slot and dispatch step
Dark-store receiving may depend on a booking or time window set outside the warehouse. Ask who receives that rule, requests the slot, confirms changes, and tells the floor when to stage goods. The provider should not promise a receiving result that depends on another party it does not control.
Set the transport boundary in writing. Name who selects the vehicle, checks documents, loads goods, records seal or package details where needed, tracks the trip, and gets receipt proof. Also name who acts when the vehicle is late, the site will not receive, or only part of the load is accepted.
Exceptions
Design the rejected-load path before it happens
A strong normal flow can fail when one case is short, a date rule is missed, a barcode fails, a site closes a slot, or the receiving team rejects the load. Ask the provider to walk through each likely event. Record where the goods go, who counts them, who changes stock, and who contacts the buyer.
Define the proof needed for each outcome. Photos, signed documents, scan logs, and system records may help, but their use depends on the agreed process. Decide how long open issues can wait before escalation and who can approve rework, redelivery, return to stock, or another action. Keep commercial and tax treatment for adviser review where needed.
Pilot
Test the workflow before adding more stock or sites
Choose a small set of goods and target sites that still shows the hard parts of the flow. Test clean orders as well as a changed order, stock shortfall, label issue, booking change, and rejected-load case. Write what counts as a pass before the pilot starts. A pilot with no pass rules becomes a sales demo.
Review order accuracy, pack and label checks, stock changes, booking steps, dispatch proof, receipt proof, open issues, and the time each handoff took. Do not turn pilot results into a broad service promise. Use them to confirm the exact scope, training, data, review rhythm, and limits for the planned launch.
Commercial review
Compare scope before you compare the quote
Two quotes can use the same service label while covering different work. List storage, inbound handling, pick, case packing, labels, extra materials, booking, transport, waiting, redelivery, returns, rework, reports, setup, support, minimums, taxes, and other charges as separate rows. Mark each row as included, extra, passed through, or unknown.
Check the provider comparison and cost questions for a wider quote method. Also review exit terms, stock handover, record access, change control, and liability with the right advisers. A low headline fee does not settle the risk if key work or failed-flow costs sit outside the quoted scope.
Network fit
Decide whether one stock node fits the wider plan
A quick-commerce flow may share stock and people with D2C orders, yet its buying rules can be different. Study demand by place, refill needs, stock cover, ageing, channel allocation, and the cost of split stock. One pool can aid control only when the order and reservation rules are clear and tested.
Use the quick-commerce replenishment process guide to map the control loop. The fulfillment role guide can help when several order sources use one inventory plan. Neither model proves that every channel, tool, or site will be supported by a given provider.
Provider review
Ask for a bounded answer from TheSameDay.Club or any provider
Bring sample purchase orders, item data, case and label rules, target-site needs, booking steps, dispatch boundaries, exception cases, and report needs. Ask the provider to mark each item as supported, conditional, outside scope, or unknown. Require a test when the answer depends on a tool, document, or third party.
TheSameDay.Club can review quick-commerce work within its wider ecommerce fulfillment services in India. This is not a claim of endorsement, partnership, live platform access, fixed coverage, or a service level. The exact goods, sites, workflows, roles, systems, and terms must be checked and agreed in writing.
Limits
What this provider checklist cannot decide
This checklist does not rank providers or name a preferred quick-commerce fulfillment centre. It does not prove that a provider can serve a platform, city, site, item, or workflow. It also does not replace a contract, facility review, data test, tax review, product-safety review, or legal advice.
Use the questions to find unknowns while change is still cheap. Then test the important paths and keep the agreed evidence. A provider is ready for your use case only when the planned work, roles, controls, and limits are clear enough for your team to accept—not because its marketing page uses the right channel words.
Review your quick-commerce workflow
Bring sample orders, item rules, target-site needs, and exception cases. We will map the work and mark what needs proof before a pilot.
Book a requirements review