Cross-border sellers hit a wall the moment an order needs a real landed cost. Odoo's native delivery framework (delivery.carrier, fixed and rule-based methods, plus the handful of Enterprise carrier connectors) can quote a shipping price, but it has no concept of comparing dozens of global couriers in one API call, no pre-paid duties-and-taxes (DDP) calculation, and no automated customs paperwork. Teams end up copy-pasting HS codes into a courier portal, guessing at import duties, then pasting tracking numbers back into stock.picking by hand — which is exactly where margin and delivery promises leak away.

ECOSIRE builds a dedicated Easyship connector that lives inside Odoo as a first-class delivery integration. We add an easyship provider type on delivery.carrier, wire a service layer to the Easyship REST API (with your API token stored in ir.config_parameter, never in source), and surface real-time rates at quotation and eCommerce checkout. A rate request sends parcel dimensions, weight, origin and destination, and declared item values; each returned option — courier, service level, delivery estimate, insurance, and the DDP-inclusive landed cost — is written back to the sale order so your team or your website customer picks with full visibility.

Technically, the module extends delivery.carrier with easyship_rate_shipment, easyship_send_shipping, easyship_get_tracking_link, and easyship_cancel_shipment methods that plug into Odoo's standard carrier interface, so the rest of the app behaves normally. HS codes, country of origin, and declared customs values live on product.template; a compute field with @api.depends on order lines, packages, and destination keeps the landed cost live as the cart changes. On validation of the delivery order we call Easyship to buy the label, store the returned PDF as an ir.attachment, write the tracking reference and courier onto the picking, and generate the commercial invoice / CN22 / CN23 customs documents as a QWeb report. An Odoo scheduled action (ir.cron) polls Easyship for status updates and posts tracking events to the picking chatter, while branded tracking notifications go out through Odoo's mail templates.

Because every backend field is real Odoo data, everything downstream works as expected: ir.model.access.csv plus record rules scope who can see rates and buy labels, automated actions can trigger label purchase on a stage change, and the whole thing is reachable over the XML-RPC / JSON-RPC API if you drive fulfillment from an external OMS or WMS. We build against your exact edition and version — Community or Enterprise, Odoo 17.0, 18.0, or 19.0 — and account for the differences (for example, Enterprise's studio-generated fields or delivery workflow tweaks) during scoping.

This is a build-to-order engagement, not an instant apps.odoo.com download. After a short scoping call we confirm your couriers, countries, DDP rules, and label/customs requirements in writing, then build, test on a staging copy of your database, and hand over installable source plus a git repository. Typical delivery is one working week from confirmed scope, followed by user training and a post-go-live support window.