Carrier mappings

Carrier mappings

Carrier mappings

Each line links an Odoo delivery method to the 3PL's carrier and service codes (e.g. delivery method "ROYAL MAIL - 070 UK-48 RM TRK-PKT" -> carrier ROYAL MAIL, service 070 UK-48 RM TRK-PKT).

Used in both directions:

  • Outbound (order push). The order's delivery method is looked up here and the mapped service is requested from the 3PL. No mapping? The delivery method's name is sent as-is - fine for 3PLs that accept free-text service levels, risky otherwise, so map what you use.
  • Inbound (despatch confirmations). The carrier/service the 3PL actually shipped with is matched back to an Odoo delivery method and written onto the delivery. Matching is tolerant of formatting - ROYAL MAIL, RoyalMail and royal-mail all match; an exact carrier+service line wins, and a carrier-only line (service left empty) acts as the fallback for that carrier.
  • Returns. The Return Carrier offered when creating a return is restricted to services of the carrier the order originally shipped with, using these mappings.

Fetch Carriers (where the provider supports it) pre-fills the table from the 3PL's own service catalogue so you only have to link the Odoo delivery methods.

If the 3PL despatches with a service you have not mapped, behaviour follows the Auto-create Delivery Methods setting: fail with a clear retryable error, or create the method and mapping automatically.

    • Related Articles

    • Status mappings

      Status mappings 3PLs report order progress in their own vocabulary (RDY2PK, PICKIP, COMPLT…). The status map translates each raw code into a human label and one of the connector's canonical statuses: Received > Processing > Picked > Packed > ...

    • Warehouse mappings

      Warehouse mappings One line per Odoo warehouse this instance fulfils, linking it to the 3PL's identifier for that warehouse (Sprint uses a warehouse GUID - ask your Sprint contact; ShipHero warehouses can be fetched with Fetch Warehouses). What the ...

    • Connect your first 3PL

      Everything from a blank instance to a live connection, in the order you should do it. Install the app and assign roles first (see the previous articles). Step 3 - Create the instance Go to 3PL Connector > Configuration > Instances > New. Name - how ...

    • Custom providers from a swagger specification

      Sprint Logistics and ShipHero are built in. Any other 3PL with a REST API described by a swagger/OpenAPI specification can be added from the UI - no code - through the Provider Designer at Configuration > Providers. This is an Admin-only, technical ...

    • What is the 3PL Connector?

      LataSys: 3PL Connector joins your Odoo database to one or more third-party logistics warehouses (3PLs). Once an instance is connected and activated, the connector pushes confirmed sales orders to the warehouse, polls their progress, writes despatch ...