The D2C ecommerce shipping workflow, from order to proof of delivery
The seven stages of D2C shipping in India, from order to AWB, manifest, tracking, NDR, RTO and COD, and the leak to watch at each step.
Most D2C brands don’t lose money on shipping in one place. They lose it in the gaps: an order that waits for a label, a manifest that misses a carton, an NDR nobody acts on, a COD parcel delivered but never matched to cash. This guide walks through the seven stages a D2C order goes through after checkout in India. For each stage it covers what has to happen, where it usually leaks and what to check in your own operation. The guide is useful whether or not you use Fretron.
Stage 1 — Order capture and allocation
What has to happen. Every order from your store and marketplaces lands in one queue. It is checked against stock that is really available, and allocated to a warehouse.
Where it leaks. SKUs that don’t map, orders allocated against stock already promised elsewhere, and risky orders (for example high-value COD) that ship before anyone looks.
Check. Can you hold an order and be sure it can’t be picked or shipped until you release it?
Stage 2 — Pick, pack and validate
What has to happen. The right items are picked, scanned into the right carton and weighed or checked before a label exists.
Where it leaks. Wrong-item or short shipments, which become returns two weeks later.
Check. Is every piece scanned at pack, or only the order?
Stage 3 — AWB booking and label
What has to happen. The shipment is booked with a courier, an AWB is issued and the label printed.
Where it leaks. Double bookings after a timeout, labels for cancelled orders, manual copying between portals.
Check. What happens when the courier API times out mid-booking?
Stage 4 — Manifest and handover
What has to happen. Shipments are grouped per courier into a manifest. Cartons are scanned at handover and the courier signs for the count.
Where it leaks. “Packed but never picked up” cartons and disputes over what was handed over.
Check. Can you prove, carton by carton, what each courier took?
Stage 5 — Tracking
What has to happen. Courier status updates flow back onto the order, so support and ops see one status.
Where it leaks. Statuses that live only in courier portals, and support teams checking five dashboards.
Check. Does your order record show the courier status, or do you have to look it up?
Stage 6 — NDR and RTO
What has to happen. A failed delivery (NDR) is raised as an exception with a reason and an owner. If the parcel returns to origin (RTO), the return is expected, received and inspected at the warehouse.
Where it leaks. NDRs nobody actions before the courier gives up, and RTO parcels that arrive unannounced and sit uninspected.
Check. Is every NDR an open task with an owner? Is every RTO received against the original order?
Stage 7 — Proof of delivery and COD cash
What has to happen. Delivery is confirmed with proof. For COD orders, the cash collected is tracked against the order until it is deposited.
Where it leaks. COD delivered but cash unaccounted for, or cash matched only in a spreadsheet weeks later.
Check. For any COD order, can you see where the cash is right now?
One record from checkout to cash
The pattern across all seven stages is the same: the leak happens where one system hands off to another. One way to close these gaps is to keep the order, the shipment, the exception and the cash on one record.
How Fretron Commerce OS does it:
- Orders from your connected channels arrive in one queue. Allocation is FEFO/FIFO-aware, and order holds block pick through dispatch. See order management.
- Each piece is scanned at the pack bench, the carton is closed, then the shipment is booked and the label printed. See the scan-to-dispatch warehouse floor.
- AWB booking has a double-booking defence. Bookings with an uncertain result are held, not repeated.
- Manifests come with a handover sheet, and cartons are scanned at dispatch handover.
- Courier status is polled back onto the order for couriers with a tracking connection. See how to ship and track every order.
- Failed delivery attempts are recorded on the order, and the RTO is started from the same record. Returns to origin are expected and received through returns inbound with QC. See NDR, RTO and returns.
- POD files are attached to the shipment. COD collected on delivery is recorded, and your team logs the cash deposit against it.
Courier connections include Delhivery; see all integrations. Stores include Shopify and WooCommerce.
For the wider picture, see D2C ecommerce operations and order management software. If you are choosing a system, use the order management software evaluation checklist.