Requested-method mappings

Requested-method mappings

Requested-method mappings

Sales channels record what the shopper chose at checkout in the requested-delivery-method field on the order (x_studio_rdelivery_method). This table translates those values into a service the 3PL accepts at order creation - the shape differs per provider: Sprint takes a single Service Level string (Standard, Express, NextDay), while ShipHero takes a shipping-lines object (title, carrier and method).

Load Requested Methods does three things in one click: fetches the services the 3PL accepts into Accepted Services (Sprint: its fixed vocabulary; ShipHero: compiled from the orders already created on the account); collects every requested-method value already used on this company's orders into the mapping table; and auto-matches the two by name. Both tables stay hand-editable, so future services or checkout values can be added any time - re-running only adds and never overwrites an existing link.

At order push a mapped value wins. An unmapped value keeps the previous behaviour: Sprint sends the raw value (Standard when empty); ShipHero falls back to the carrier-mapping service and shows the raw requested value as the shipping title so the operator can see the intent.

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

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

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

    • Sprint Logistics adapter - setup and reference

      Everything you need to connect the LataSys 3PL Connector to Sprint Logistics: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. What this adapter provides Flow Supported Order push and despatch write-back Yes ...

    • ShipHero adapter - setup and reference

      Everything you need to connect the LataSys 3PL Connector to ShipHero: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. What this adapter provides Flow Supported Order push and despatch write-back Yes Order ...