Systems guide · 3 August 2026
Quick-commerce replenishment process: from purchase order to proof
Quick-commerce replenishment moves stock to another stock point against a purchase order. A reliable process checks the request, holds stock, prepares the load, records dispatch, proves receipt, and closes gaps.
This guide explains a neutral operating model. It does not claim a relationship with any quick-commerce platform. It also does not promise acceptance, delivery time, fill rate, appointment access, or any other service level.
Process map
Give each purchase order a clear state
A purchase order, or PO, tells a supplier what a buyer has asked for. It is not proof that stock exists or that a delivery will be accepted. The first task is to log the PO, version, due terms, destination, item lines, units, labels, and any booking need.
Use simple states that every team can read. For example: received, checked, held, short, ready, dispatched, received, disputed, and closed. Each state needs an owner and proof. Without shared states, sales, planning, warehouse, and finance teams may all hold a different view of the same PO.
| Stage | Main check | Proof to keep | Issue to route |
|---|---|---|---|
| PO intake | Right version, place, items and due terms | Time-stamped source file | Missing or changed data |
| Stock hold | Usable units by item and batch | Hold record and shortage note | Short or blocked stock |
| Pick and pack | Units, dates, labels and cartons | Check sheet and carton list | Wrong or damaged units |
| Dispatch | Vehicle, papers, load and handoff | Dispatch record | Late or failed handoff |
| Receipt | Accepted units and any rejection | Proof of delivery | Short receipt or rejection |
| Close | PO, dispatch, receipt and stock match | Reconciliation record | Open quantity or money gap |
PO checks
Validate the request before stock is touched
Start with the document, not the shelf. Check the PO number, issue date, version, destination, item code, unit of measure, quantity, due date, tax or invoice needs, label rules, and booking steps. Use qualified advisers for legal and tax points that affect your case.
Decide how changes will arrive. A new email, file, portal update, or buyer note can create two live versions. Keep one source record and mark older versions as closed. If a change arrives after picking starts, pause the affected lines and record who approved the next step.
Set a reply path for bad data. A wrong item code, unclear case size, missing address, or past due time should not move into silent manual work. Log the gap, send it to the named owner, and keep the reply with the PO record.
Stock allocation
Hold usable stock and show shortages early
Check more than the total count. Units may be blocked, damaged, too close to an agreed date limit, already held for another order, or stored under a different item code. The hold should point to the stock that can be used for this exact request.
If the full PO cannot be met, do not hide the gap by changing quantities without approval. Record the asked units, usable units, short units, cause, and decision owner. The buyer may accept a partial load, a later load, a substitute, or a full stop. That choice belongs in the written process.
Allocation also affects other sales channels. A large replenishment hold can remove stock from D2C or marketplace orders. Agree on channel priority, safety stock, and release rules. The fulfillment role guide explains how one stock pool can serve different order paths.
Pick, check, and pack
Turn the PO into work the floor can follow
Translate each PO line into a pick task with the right item, batch, unit, and location. Keep the pick order clear. A second check may compare picked units with the PO and stock record. The exact control should match the goods and risk in the written scope.
Packing rules may cover inner packs, master cartons, labels, barcodes, carton count, weight, seals, and papers. Do not copy a rule from another buyer or destination. Keep an approved work note with a start date, owner, sample, and version so the floor uses the current rule.
Capture issues before the load leaves. Wrong units, weak cartons, unreadable labels, missing papers, or count gaps are easier to fix at the site. Record the fault, units held back, action, and sign-off. Do not turn a late fix into an unlogged change.
Dispatch and proof
Use a chain of proof, not one vague status
“Dispatched” can mean picked, packed, loaded, handed to a driver, or recorded in a system. Define the event. Keep the load time, carton count, papers, vehicle or carrier record, destination, handoff person, and any image or scan that the agreed process needs.
Proof of delivery should link back to the same PO and load. It may show received time, units, cartons, receiver, and notes on damage, shortage, or rejection. A signature alone may not settle every gap. Agree on what proof is needed and where it will be stored.
A failed handoff needs its own state. Record the reason, time, place, stock condition, next action, and cost owner if agreed. Do not claim a service level unless it appears in the account's written terms. Public platform or provider pages do not set the terms for your load.
Reconciliation
Match ordered, sent, received, and returned units
Close the loop with a line-by-line match. Compare the PO quantity, held quantity, picked quantity, dispatched quantity, accepted quantity, rejected quantity, and any returned quantity. Then compare the stock record and any money record that depends on those units.
Give each gap a reason code and owner. Common groups include data error, stock shortage, pick error, damage, label issue, late handoff, short receipt, and buyer rejection. Keep the first facts separate from the later cause finding. That keeps the review fair and useful.
Review repeat causes over time. If one label rule causes many holds, fix the work note. If PO changes arrive late, change the intake rule. If receipt proof is weak, improve the proof step. The value comes from changing the system, not only closing old tickets.
Set a regular review with planning, warehouse, finance, and the account owner. Look at open POs, old gaps, short lines, rejected units, and repeat causes. Close actions with a name and date. This keeps the control loop active after launch, when small gaps can otherwise become normal work.
Pilot and written scope
Test the control loop with a small set of POs
Choose a small item set that still shows the real work. Include more than a clean full PO. Test a short line, a changed version, a label fault, a failed handoff, and a receipt gap. Agree on pass rules for data, stock, packing, proof, and issue handling.
Measure what the team can control. Check whether each state had proof, whether stock stayed clear, whether issues reached an owner, and whether the final match closed. Do not turn pilot results into a broad promise. Goods, places, volumes, teams, and buyer rules can change.
Before launch, put PO inputs, cut-offs, booking roles, stock rules, item and pack rules, dispatch steps, proof of delivery, rejected-load handling, reports, fees, and service terms in writing. Also list exclusions. A platform name must not be used as proof of a partnership, integration, or accepted service level.
Related buyer tools
Check the partner as well as the process
Use the quick-commerce fulfillment centre checklist to review a provider's PO controls, stock rules, labels, proof, and issue path. Use the provider comparison and cost questions to ask which receiving, storage, handling, transport, and exception costs apply.
If replenishment is one path within a wider operation, map D2C and marketplace work as well. A purchase order flow should not hide stock risk in other channels. The India provider comparison offers an unranked start for a wider provider check.
Review your replenishment control loop
Bring sample POs, stock rules, pack notes, proof needs, and issue cases. We can review the steps and open points before a written scope is agreed.
See our core ecommerce fulfillment services in India page for the wider stock-node review.
Review the process