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 confirmations (carrier, tracking, batch numbers) back into Odoo as real stock moves, keeps your stock levels aligned with what the warehouse counts, announces inbound deliveries, reconciles goods-received notes, and manages customer returns end to end - all with a complete audit trail.
This page is the whole first-run journey in one place: install the module, assign roles, connect your first 3PL, map warehouses and carriers, choose what to sync, and activate.
Instance. One configured connection to one 3PL account - for example "Sprint (Sandbox)" or "Sprint Live". An instance owns its credentials, its mappings, its sync settings and its history. You can run several instances at once (different 3PLs, or the same 3PL's staging and live environments side by side). Everything else in the app hangs off an instance.
Provider. The kind of 3PL an instance talks to. Sprint Logistics and ShipHero are built in - their API behaviour is implemented in code. Additional providers can be added from a swagger/OpenAPI specification without code changes (see Custom providers).
Capabilities. Not every 3PL supports every feature. Each provider declares what it can do (orders, stock, products, suppliers, ASNs, GRNs, returns, cancellation, batch tracking). The app uses this everywhere: settings that do not apply are hidden, instances are not offered for operations their provider cannot perform, and dashboard cards for unsupported functions are greyed out with an "Inactive" badge. If you cannot find a setting described in this documentation, your provider most likely does not support that capability.
Flows. The individual synchronisation operations: order push, status poll, despatch, stock sync, product push, product match, supplier push, ASN push, GRN poll, returns poll, return label, order cancel. Every execution of every flow is recorded in the Sync Log with its full request and response payloads.
Sync Log. The audit ledger. Every API call the connector makes - scheduled or manual, successful or failed - creates a log entry you can open, inspect and retry. If you ever wonder "what did the app actually send?", the answer is always in the Sync Log.