Settings Reference
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 - ...
Instance states and connection settings
Settings live on the instance form (3PL Connector > Configuration > Instances). Only Admins can change them, and every change is tracked in the instance's chatter. Settings whose capability the provider does not support are hidden throughout. Header ...
Choosing what to sync and how often
What to sync Each switch enables one scheduled flow. Turning a switch off never deletes anything - it only stops the scheduler running that flow; manual runs from the Operations pages remain possible. Sync Orders (default on). Enables the two order ...
Order behaviour settings
These settings decide how orders leave Odoo and what happens when reality at the warehouse disagrees with the plan. Each entry covers what the setting does, its default, and a scenario where it matters. The Order Field Mappings section at the end ...
Stock, inbound, returns and housekeeping settings
The remaining Sync Settings sections: returns, multi-company, inbound and stock, operational limits, provider-specific options, background jobs and housekeeping. Returns Behaviour (shown when the provider supports returns) Damaged Returns Location. ...
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 ...
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 > ...