Why placed COD revenue can mislead
A prepaid order usually confirms payment before fulfillment. A COD order records customer intent, but collection depends on successful delivery. Counting both as equally realized at placement can overstate cash generation and product performance.
Track placed, shipped, delivered, refused, unreachable, and returned outcomes. The timing gap between these states is part of the business model and should appear in the operating view.
Calculate the cost of an RTO
A return-to-origin order can include outbound shipping, return shipping, packaging, handling, and inventory delay while producing no collected revenue. Some products also return damaged or become harder to resell.
Calculate the average loss per RTO and allocate the total across delivered COD orders. This produces a more useful delivered-order contribution than looking only at the margin of successful shipments.
Diagnose the source, not just the rate
Segment RTO by product, location, courier, acquisition source, order value, and confirmation status. A store-wide average can hide one campaign or region creating most of the loss.
Use the diagnosis to choose a response: address validation, clearer delivery expectations, confirmation workflows, prepaid incentives, courier changes, or pausing a poor-quality source.
Keep growth and collection aligned
- Report placed COD demand separately from delivered COD revenue.
- Include both shipping legs when evaluating RTO loss.
- Judge campaigns on delivered contribution after enough time has elapsed.
- Compare prepaid incentives with the losses they are designed to prevent.