This is a build-to-order module, not an instant apps.odoo.com download — nothing installs automatically at checkout. After purchase we confirm which couriers you need, collect your carrier account credentials and pickup details, then build, test on a staging copy and install it in your database. Typical lead time is 2–4 weeks depending on how many carriers you activate and how each courier's API and COD remittance format behaves. You get a clear timeline in your quotation before work starts.

When you book a COD shipment, the module sends the collectable amount to the courier and stores the COD reference on the delivery. When the courier pays out, you import their remittance/payout file and the module auto-matches each collected-cash line to its source picking and invoice, flagging short-paid, over-paid, returned (RTO) and still-outstanding parcels. Finance reconciles from a matched list instead of chasing cash across a spreadsheet. We tailor the matching to your specific courier's file format during the build.

We build against Odoo 17, 18 and 19, on both Community and Enterprise. Each carrier is implemented as a native delivery.carrier delivery_type extension, so it plugs into the standard delivery framework your version already ships with. Tell us your exact version and edition and we build and test specifically for it; if you later upgrade Odoo, carrier-API adjustments are handled under support or a scoped update.

You only pay to activate the couriers you actually use — a two-carrier build is smaller and faster than an eight-carrier one. The module is built on a reusable base connector contract, so adding a further regional courier (or a new one you sign with later) reuses the same architecture rather than starting over. If your courier exposes a REST or SOAP API, we can almost always integrate it — send us their API docs and we'll confirm in the scoping call.

Every build includes a post-go-live support window (duration stated in your quotation) covering bug fixes and adjustments when a courier changes its API. Because we hand over the full, documented source with security rules, your own team — or your Odoo partner — can also maintain and extend it independently. Beyond the included window you can take an ongoing support/maintenance retainer, or engage us per-change for new carriers, new COD formats or Odoo version upgrades.

No. Everything sits on standard Odoo models — delivery.carrier, stock.picking and account moves — so your existing Studio fields, QWeb reports and XML-RPC/JSON-RPC integrations keep working. Credentials are stored on configuration records rather than hard-coded, access is scoped with ir.model.access.csv and record rules, and we validate the whole thing on a staging copy of your database before touching production, with a rollback plan in hand.