Polish e-commerce and distribution teams live and die on parcel-locker delivery, but Odoo core ships with no native connector for the dominant Polish carrier network. Out of the box you get the generic delivery.carrier model with fixed-price or rule-based rates — no live rate lookup, no locker/point-of-collection selection, no automated label PDF, and no back-and-forth of tracking numbers into the shipment. Warehouse staff end up copy-pasting parcel details into a separate carrier portal, printing labels there, and hand-typing tracking references back into Odoo. That double entry is slow, error-prone, and breaks the moment order volume climbs.

ECOSIRE builds a made-to-order delivery integration that extends Odoo's shipping framework so the carrier lives natively inside your workflow. We add a dedicated provider on delivery.carrier (extending provider selection), wiring rate_shipment, send_shipping, get_tracking_link, and cancel_shipment to the carrier's REST API through Odoo's standard requests/JSON handling. Credentials, sandbox-vs-production endpoints, and default parcel dimensions are held in encrypted config parameters and per-warehouse settings. When a picking is validated, the connector requests the shipment, receives the tracking number and a label, stores the label as an ir.attachment on the stock.picking, and writes carrier_tracking_ref back automatically — no portal, no retyping.

Technically, the build spans new fields and compute methods (models.Model, fields, @api.depends) for parcel weight/size rollups, an OWL/JS widget or website checkout selector for parcel-locker point-of-collection where relevant, QWeb templates for the branded label and a picking-list report, and automated actions to push status transitions and notify customers on dispatch. Security is enforced with ir.model.access.csv for new models plus record rules so multi-company setups only see their own carrier accounts. All API calls run server-side and are safe to trigger from the standard XML-RPC/JSON-RPC API, so your own middleware or marketplace connectors can create shipments programmatically. We target your exact Odoo line — 17.0, 18.0, or 19.0 — and handle Community vs Enterprise differences (Enterprise's studio/field-service hooks vs Community's plain stock flow) during scoping.

Because this is build-to-order, nothing is downloaded and dropped in blind. After a short scoping call we confirm your carrier account type, parcel profiles, checkout flow, and Odoo edition, then build against a staging copy of your database, run UAT together, and deploy with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company rollouts, extra carrier services (COD, returns, cross-border), website-checkout locker selection, and data migration of historical shipments increase the quoted scope. You receive a fixed quote after the scoping call — the from-price is indicative only.