Illustrative previewBuild-to-order Odoo x PostEx integration:
create shipments, print AWB labels, automate COD reconciliation and returns. Built, installed and supported by ECOSIRE.
What is PostEx Courier Connector for Odoo?
Build-to-order Odoo x PostEx integration: create shipments, print AWB labels, automate COD reconciliation and returns. Built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Odoo.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
Technical Specifications
- Odoo Compatibility
- Odoo 17, Odoo 18, Odoo 19
- Editions
- Enterprise & Community
- License
- Licence confirmation required
- Python Requirement
- Python 3.10+
- Database
- PostgreSQL 12+
About this Product
Pakistani e-commerce runs on cash-on-delivery, and PostEx is one of the fastest-growing COD-first couriers in the country. But most Odoo sellers still book PostEx shipments by hand: copy the customer address into the PostEx merchant portal, generate the AWB there, paste the tracking number back into Odoo, and then spend the end of every month trying to reconcile which COD orders were actually paid out. That manual loop leaks hours, invites address typos, and leaves your Odoo delivery orders permanently out of sync with reality.
The PostEx Courier Connector closes that loop. This is a net-new, build-to-order Odoo module that ECOSIRE designs, builds, installs and supports specifically for your PostEx merchant account and your workflow. It is NOT an off-the-shelf apps.odoo.com download you install yourself in five minutes — it is a real integration engineered against the PostEx Merchant API and wired into your Sale, Inventory (stock.picking) and Accounting flows, then handed over with documentation, training and a warranty support window.
Under the hood the module ships as a proper Odoo app: a versioned __manifest__.py declaring dependencies on sale, stock and delivery; new ORM models (models.Model) such as a postex.shipment record and a delivery.carrier extension with your PostEx API token stored securely in ir.config_parameter; compute fields (@api.depends) that derive the COD collectable amount from the linked sale order; QWeb PDF reports for the AWB label with a scannable barcode; automated actions and scheduled ir.cron jobs that poll PostEx for tracking status; and access control via ir.model.access.csv plus record rules so warehouse users see only what they should. We target Odoo 17, 18 and 19 and work on both Community and Enterprise.
The result: your team creates a delivery order in Odoo as usual, clicks "Book with PostEx", and the shipment is created over the PostEx API, the AWB label prints straight from Odoo with a barcode, the COD amount is computed automatically from the order, tracking updates flow back onto the picking without anyone logging into the portal, and returned/failed parcels are captured so your stock and COD ledgers stay honest. Because ECOSIRE builds it, you also get a partner who fixes it when PostEx changes their API — not a frozen listing you have to abandon.
What you get
- Complete, installable Odoo module (source code) targeting your chosen versions among Odoo 17, 18 and 19, delivered as a versioned app with a clean __manifest__.py
- Installation and configuration on your Odoo instance (Community or Enterprise), including secure wiring of your PostEx merchant API token and origin/warehouse address
- Configured PostEx delivery.carrier, COD compute logic, AWB QWeb label report and the ir.cron tracking sync tuned to your dispatch schedule
- Security layer set up for your roles: ir.model.access.csv access rights and record rules mapped to your warehouse and finance teams
- UAT/sandbox validation: test bookings against PostEx, AWB print check, COD computation check and a tracking round-trip before go-live
- Written documentation — an admin configuration guide plus a step-by-step operator guide for booking, printing, returns and reconciliation
- A live training session for your dispatch and finance staff, with a recording you keep
- Post-launch support and bug-fix window (defect warranty) plus a source handover so the module is fully yours to keep and extend
Who this is for
COD-heavy online seller / D2C brand
A Pakistani e-commerce seller shipping a high daily volume of cash-on-delivery parcels through PostEx. They need bookings, labels and COD reconciliation to happen inside Odoo instead of juggling the PostEx portal and spreadsheets, so the team can dispatch faster and actually know which orders got paid.
Warehouse / dispatch operations lead
The person who validates delivery orders and gets parcels out the door each day. They want one-click and bulk booking from the stock.picking view, an AWB label that prints straight from Odoo with a barcode, and returned/failed parcels flowing back automatically so inventory stays accurate.
Finance / accounts manager
Responsible for reconciling COD collections against the PostEx payout. They need a trustworthy view of computed COD amounts per order, delivery vs. collection status, and returns — so month-end reconciliation stops being a manual, error-prone chase.
How PostEx Courier Connector for Odoo Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| PostEx API integration (booking, AWB, tracking sync) | Built specifically for PostEx against the official Merchant API, wired into your sale/stock flows | Possible, but you fund the full R&D and PostEx API learning curve yourself | Rarely exists for PostEx specifically; generic listings target other couriers | Not included |
| Automatic COD amount computation from the sale order | Yes — @api.depends compute field derived from the order total, discounts and prepayments | Only if your developer builds and tests the compute logic | Partial support | Not included |
| COD payout reconciliation view for finance | Yes — delivered-vs-collected reconciliation view built into the module | Buildable, but extra scope and cost | Not included | Not included |
| AWB label as a printable QWeb PDF with barcode | Yes — branded QWeb report with PostEx barcode, prints straight from Odoo | Requires custom QWeb template work | Partial support | Not included |
| Return / failed-delivery (RTS) handling tied to stock and COD | Yes — returns captured against the order, drive stock moves and exclude from COD | Only if explicitly built and tested | Not included | Not included |
| Security via ir.model.access.csv + record rules for warehouse vs finance | Yes — role-based access mapped to your teams during setup | Depends on your developer's diligence | Partial support | Partial support |
| Fixes when PostEx changes its API | Yes — defect warranty plus optional ongoing maintenance | You maintain it yourself indefinitely | Not included | Not included |
| Delivery model | Build-to-order in one working week, installed and validated on your instance | Long in-house project, unpredictable timeline | Instant download, but generic and unsupported for PostEx | Not included |
Frequently Asked Questions about PostEx Courier Connector
How long does delivery take, and is this an instant download?
This is a build-to-order module, not an instant apps.odoo.com download — please don't expect a self-install ZIP. After we confirm your requirements and PostEx merchant details, typical delivery is one working week: scoping and API access, build against the PostEx Merchant API, sandbox/UAT validation on your instance, then go-live. Simpler single-warehouse setups land near the shorter end; multi-warehouse, POS or website-triggered flows take longer. We give you a firm timeline before starting.
What support and updates are included after go-live?
Every build includes a post-launch defect-warranty window during which we fix any bug in the delivered scope at no extra charge. Because PostEx occasionally changes its API, we also offer ongoing maintenance so the connector keeps working through those changes and across Odoo point releases. You receive the full source, so you're never locked in — but most clients keep us on a support plan precisely because we maintain the PostEx side for them.
Do I need PostEx Enterprise / a merchant account and API credentials?
Yes. You need an active PostEx merchant account and access to your PostEx Merchant API token — we integrate against the official API, we don't scrape the portal. If you're not sure how to obtain API access, we help you request it from PostEx as part of onboarding. Your token is stored securely in Odoo's ir.config_parameter, never hard-coded in the module.
Which Odoo versions does it support, and does it work on Community?
We build for Odoo 17, 18 and 19, and the module works on both Community and Enterprise editions — it depends only on the standard sale, stock and delivery apps, not on Enterprise-only features. Tell us your exact version and edition and we target that build; we can also deliver a multi-version build if you plan to upgrade.
How does automatic COD computation and reconciliation actually work?
The COD collectable amount is derived with an Odoo compute field (@api.depends) from the linked sale order total, so it respects your prices, discounts and any partial prepayment automatically rather than being typed in. On the finance side, we build a reconciliation view that matches delivered shipments against PostEx COD status, so you can see at a glance which orders were collected, which are pending, and which came back as returns.
What happens with returns and failed deliveries?
Return-to-sender and failed-delivery events are captured against the original order via the tracking sync, so the parcel status is visible in Odoo without checking the portal. We wire the return so it can trigger the appropriate stock move back into inventory and flag finance to exclude it from COD collections — keeping both your stock levels and your COD ledger accurate.
Can it push shipments from my website, POS or another system, not just the Odoo backend?
Yes. Beyond the backend button and bulk action, we can expose PostEx booking through Odoo's JSON-RPC/XML-RPC API or automated actions, so an order confirmed on your website or POS can create a PostEx shipment automatically. We scope this with you up front since it affects the design and the timeline.
Related Modules
OTTO Market Marketplace Connector
A build-to-order Odoo connector that syncs OTTO Market orders, listings, stock and settlements directly into your Odoo database. ECOSIRE scopes, builds, installs and supports it for your exact Odoo version and warehouse setup.
Palletized Freight Network Shipping Integration
A build-to-order Odoo integration that connects your delivery workflow to a European palletized freight distribution network, automating consignment booking, label and manifest generation, and shipment tracking straight from the sales and inventory flow. ECOSIRE builds, installs, and supports it for your Odoo 17/18/19.
PostEx Courier Connector
Build-to-order Odoo x PostEx integration: create shipments, print AWB labels, automate COD reconciliation and returns. Built, installed and supported by ECOSIRE.
- One-click PostEx shipment booking directly from an Odoo sale order or delivery order (stock.picking) — no re-typing addresses into the PostEx merchant portal
- PostEx Merchant API integration for order creation, cancellation and status sync, with the API token stored securely in ir.config_parameter (not hard-coded)
- Automatic AWB (tracking number) capture written back onto the delivery order and sale order the moment PostEx accepts the shipment
- Printable AWB shipping label as a QWeb PDF report, including the PostEx barcode, consignee details, order reference and COD amount for warehouse packing