Skip to content
ERP Builders

Integration · Commerce

Shipping carrier integration: labels and tracking from the ERP

Copying addresses into a carrier website and pasting tracking numbers back is one of the most common manual tasks in a warehouse. Carrier integrations let the ERP get rates, print labels and record tracking at the packing station.
Integration flow from Shipping Carriers through an integration layer with queueing, mapping and retries into ERPSOURCEShipping Carrierswebhook · RESTINTEGRATION LAYERValidate + mapQueue (idempotent)Retry w/ backoffDead-letter + alertSYSTEM OF RECORDERPorders · stock · ledgerINBOUND (ORDERS, CUSTOMERS)OUTBOUND (STOCK, STATUS, INVOICES)

Overview

What this integration is for

Odoo provides connectors for several major carriers, and Odoo 20 adds a ShipStation connector. Where no connector exists, we integrate directly with the carrier's API or through a multi-carrier platform.

01Data

What data syncs, and in which direction

Data synchronised between Shipping Carriers and the ERP
EntityDirectionNotes
RatesApp → ERPLive rates on quotations and at checkout, by service level.
Shipments & labelsERP → AppPackages, weights and addresses sent to the carrier; labels returned for printing.
TrackingApp → ERPTracking numbers and delivery status recorded on the delivery order.

02Use cases

Common use cases

01

Faster packing

Print labels from the packing screen in one step.

02

Accurate shipping charges

Charge customers real carrier rates.

03

Customer updates

Tracking numbers sent automatically.

03 — Architecture

API architecture

Labels are requested synchronously at packing time with short timeouts and a clear fallback. Tracking updates are polled or received by webhook in the background and attached to delivery orders.

Integration flow from Shipping Carriers through an integration layer with queueing, mapping and retries into ERPSOURCEShipping Carrierswebhook · RESTINTEGRATION LAYERValidate + mapQueue (idempotent)Retry w/ backoffDead-letter + alertSYSTEM OF RECORDERPorders · stock · ledgerINBOUND (ORDERS, CUSTOMERS)OUTBOUND (STOCK, STATUS, INVOICES)

04Reliability

Authentication, errors and retries

01

Authentication

Carrier account API keys or OAuth credentials, stored securely per warehouse or company.

02

Error handling

Address validation errors are shown to the packer immediately with the carrier's message; failed label requests can be retried or switched to another service.

03

Retry strategy

Background tracking updates retry with backoff; label requests are retried manually by the user.

05 — Data mapping

Field mapping essentials

Field mapping between Shipping Carriers and the ERP
Shipping CarriersERP
Delivery orderShipment
Package typeCarrier packaging code
Carrier trackingDelivery tracking reference

06 — Automation

Automation opportunities

  • Carrier chosen by rules: weight, destination, service level
  • Tracking emails sent when the label is created
  • Exceptions flagged when deliveries are late

07 — Security

Security considerations

Carrier credentials stored encrypted; addresses sent only to the chosen carrier.

Related

Where this integration fits

Insights

Related reading

ERP Integrations2 min read

RFID Integration with Odoo: A Practical Architecture

How to integrate RFID readers with Odoo inventory: middleware design, mapping EPCs to products and serials, receiving and counting flows, performance and what to build vs buy.

FAQ

Frequently asked questions

Which carriers can you connect?

Major international carriers through existing connectors, and regional carriers or multi-carrier platforms through their APIs.

Can we print labels on thermal printers?

Yes. Labels are requested in the format your printer needs, such as ZPL or PDF.

Next step

Connecting your carriers to your ERP?

Tell us your volumes, channels and data rules. We will outline the architecture and the risks before anything is built.