Odoo logistics and shipping integrations
Published on the Apps Store
DelhiveryOne connects Delhivery’s carrier network to Odoo — the shipping method appears at checkout and in the back office, rates are calculated against the account, shipments are booked, labels are generated and consignments track back into the order.
Built for a Nordic partner
Not every carrier has a module waiting on the store. Logistra is a shipping connector we built for a Norwegian partner — the same shape of work as DelhiveryOne, delivered where no off-the-shelf option existed. Live rates, booking, packaging, labels and tracking, on the Odoo website and in the back office, against the carrier’s Nordic network.
It is not a published product. It is what the shipping integration looks like when it is built to order, and it runs in production.
- Carrier network
- Nordics
- Odoo
- 17, 18 and 19
- Scope
- Rate calculation, booking, packaging, labels, tracking — website and back office
- Credentials
- The partner’s carrier account, procured by the client
- Availability
- Built to order — talk to us
Last-mile dispatch, Kuwait
Roboost is not a shipping method at checkout. Delivery tickets on Odoo POS become driver tasks; status comes back onto the order the kitchen already printed. Built for a Kuwait estate. The operator is unnamed.
Rates, booking and labels stay with DelhiveryOne and Logistra. This is the driver half: a task, a stored reference, and a callback when the courier moves. It is not a published module. The mapping, the address parts the driver actually uses, and what a failed delivery does to the POS order live on the Roboost page.
- Market
- Kuwait last-mile
- Into
- Odoo POS. Driver status on the order.
- Delivered
- Task create, reference stored, driver status callbacks, per-company on/off and store code
- Client
- Unnamed
- Availability
- Built to order. Roboost detail →
The common shape
DelhiveryOne and Logistra do the same job against different carriers: the shipping method surfaces at checkout, rates calculate live against the carrier account, shipments book, labels generate and tracking flows back to the order. Roboost is the other job: a delivery task and a status callback, not a rate at checkout.
Where a carrier you use is not covered, it is a scoped integration against their API. Same shape as these, which is where the estimate comes from rather than guesswork. A custom DHL integration for sample dispatch is that label-and-tracking shape, built to order.
We have delivered 20+ integrations. Shipping and dispatch are one category; banks, payments, e-invoicing and utility metering sit alongside it and mostly stay bespoke.
Roboost · Integration engineering · Payments · Odoo implementation
Which carrier, which market?
Tell us the carrier and the market you ship in, and the Odoo version you run. DelhiveryOne installs from the store; last-mile dispatch and anything else is a scoped build, and we can size it in one reply.