Skip to content

COD vs prepaid: compare operations, risks and cash flow

Compare payment on delivery with payment before shipment without invented conversion rates: orders, returns, costs and evidence of settlement.

Updated on · 3 min read

AI-generated illustration of cash and card payments, a parcel and a return

The main difference: when payment happens

With COD, the customer pays when the parcel is handed over, according to the selected service. With prepaid orders, payment is requested before shipment. This distinction changes order processing, exception tracking and funds reconciliation, but it does not establish that one model is more profitable for every store.

Your procedure should define what “prepaid” means. With some card payments, authorization, capture and payout are separate stages. An authorization is not an available bank payout. Similarly, a delivered COD order does not prove that the carrier settlement has been received.

Compare order workflows

For COD, check the details needed for parcel handover: recipient, address, amount and accepted payment method. Agree on the confirmation process and which cases must be addressed before shipment. In Shopify, a manual method such as COD leaves an order pending payment until payment is confirmed.

For payment in advance, check the payment status at its source and the events required before shipping. Avoid using the same label for a created order, an authorized payment and a settled order. Your logistics tool should receive instructions that reflect the actual status.

Address risks without inventing percentages

With COD, an absent recipient or refusal may lead to another attempt or a return, depending on the agreed conditions. With prepaid orders, you must also plan for cancellations, refunds and potential payment disputes. Their consequences depend on products, contracts and procedures; no universal percentage is claimed.

To compare models, collect events observed in your own store. Define what counts as delivered, returned, refunded or settled. Compare consistent periods and indicate whether any orders remain open. An incomplete status should not be interpreted as a final outcome.

Prepare returns and customer information

Payment on delivery does not remove the need to clearly inform customers about the seller, total price and applicable terms. Prepare an understandable return procedure and a contact for requests. Distinguish refusal before receipt from a return requested after the product has been handed over.

In the European Union, distance sales generally include a right of withdrawal, subject to exceptions relating in particular to the product and service. The Your Europe source explains the general framework. Check the conditions applicable to your business rather than assuming that choosing COD or prepaid removes this obligation.

Compare costs at batch level

Build a comparison sheet using your documented costs: product purchase, advertising, preparation, shipping, returns and applicable payment or service fees. Revenue should correspond to funds actually collected. Keep estimates separate from verified entries.

Compare a batch of orders that has completed its lifecycle with the corresponding expenses. If parcels are still in transit or settlements still need reconciliation, show them separately. Multiplying average order value by an order count is not sufficient to calculate profit.

  • Use the amounts and currencies actually recorded.
  • Apply the fee contracts relevant to the batch.
  • Distinguish observed expenses from assumed expenses.
  • Track open orders without treating them as successful outcomes.

Understand when cash becomes available

COD involves a collection stage and a settlement stage that must be reconciled. Request payout references and a breakdown of deductions for the relevant orders. No payment deadline can be inferred solely from the delivery date.

In CODShipEurope, evidence of received funds and admin validation come before COD availability. A withdrawal request then reserves the requested amount. Its approval remains separate from confirmed payment, and an uncertain outcome retains a processing status. Confirm the exact terms with the team.

Decide using an operational test

Choose a test scope suited to your resources, destinations and procedures. The right model is one whose workflow and costs you can verify without hiding exceptions. You can evaluate several payment methods if their statuses and responsibilities remain clearly separated.

Before offering a service, confirm its availability and conditions for your activity. Explore the market guides and wallet overview, then prepare the remaining questions with your team. This comparison does not establish any guaranteed conversion rate, revenue gain or profit.

Sources and references

Read next

COD operations in Europe: from order to settlement