Warehouse mappings

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 mapping drives:

  • Order eligibility. An order belongs to an instance when its Odoo warehouse is mapped there. This is how multiple instances coexist: orders from "Warehouse UK" go to your UK 3PL, orders from "Warehouse US" to ShipHero, automatically.
  • Order push. The mapped remote code is sent as the warehouse on every order.
  • Inventory sync. Stock snapshots are reconciled against the mapped warehouse's stock location.
  • Activation guard. An instance will not activate without at least one mapped warehouse.

Only one active instance may claim a given warehouse - re-activating an instance checks for double claims, so two instances can never fight over the same orders.

Example: you fulfil UK web orders from "Noughty (Sandbox)" via Sprint. One mapping line: Noughty (Sandbox) -> Sprint warehouse GUID. Later you add a US warehouse fulfilled by ShipHero: create the second instance, map the US warehouse there, and orders route themselves by warehouse with no further configuration.

    • Related Articles

    • 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 ...

    • 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 > ...

    • 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 ...