bpost Shipping Connector for Odoo

ECOSIRE builds a proper bpost delivery.carrier provider for your Odoo. We extend delivery.carrier with a new delivery_type selection (bpost), store your bpost account ID, passphrase and contract reference on the carrier record, and implement the provider methods Odoo expects — bpost_rate_shipment, bpost_send_shipping, bpost_get_tracking_link and bpost_cancel_shipment. Rating calls your negotiated bpost contract so the price shown on the sale order and the delivery order is the real bpost price for that weight, destination and product (bpack 24h, bpack World, etc.), not a flat guess.

Technically, the connector sits on Odoo's stock and delivery layer. When a warehouse user validates the stock.picking, the module calls the bpost Shipping Manager API, receives the label (PDF or PNG), stores it as an ir.attachment, and writes the returned barcode into the picking's carrier_tracking_ref so the QWeb delivery slip and the customer email both carry it. A scheduled action (ir.cron) polls bpost for tracking events and updates a status field via a computed method decorated with @api.depends, so "Shipped → In transit → Delivered" flows into the chatter without anyone refreshing a portal. Parcel-locker and pickup-point shipments are handled by capturing the chosen point (with its bpost point ID) on the order and passing it through as the delivery address on the label call — including the eCommerce checkout path when you run Odoo Website. International shipments carry the required customs data (contents, value, HS code fields) so bpack World labels are accepted. All credentials and endpoints are stored in res.config.settings, and access is locked down with ir.model.access.csv plus record rules so only Inventory users touch carrier configuration.

Because this is a build-to-order module, you are not downloading a fixed app and hoping it fits. We start from your actual bpost contract, your Odoo version (17.0, 18.0 or 19.0), your Community or Enterprise edition, and your real shipping flows (drop-ship, multi-warehouse, returns), then build, test on a staging copy, and hand over installable source. Typical delivery is 2–4 weeks from confirmed scope. You keep the git repository and full source — nothing is obfuscated or license-locked.