Step 1 - Install

Install LataSys: 3PL Connector from the Apps menu. The module depends on Sales, Inventory (with delivery), Purchase and Expiration Dates - Odoo installs these automatically if they are missing.

After installation a new 3PL Connector app appears in the main menu with: Dashboard, Operations (Orders, Products, Suppliers, Returns, Inventory Syncs), Sync Log and Configuration.

Companion apps. The core app covers orders, stock and returns. Three capability packs unlock more when installed alongside it: LataSys 3PL Connector: Products (product push and enrichment - see Products), LataSys 3PL Connector: Inbound (ASNs, GRNs and supplier sync - see ASNs and GRNs) and 3PL Connector: Order Routing (rules that decide which 3PL fulfils what - see Orders and despatch). Install a pack from the Apps menu and its menus and settings appear automatically; without it those flows simply stay off. Existing installations upgrading from the earlier all-in-one build get Products and Inbound installed automatically, so nothing they were using disappears; Order Routing is new and purchased separately.

A pack must also be included on your license: a license can name the packs it covers, and a pack only works when it is both installed and included. Newer keys also name the built-in providers they include (Sprint Logistics, ShipHero, Amazon MCF): a named provider allows any number of its instances, with staging and live sharing one entitlement. Custom (swagger-defined) providers are licensed as slots counting distinct provider definitions - one slot is included with the core app, and slot packs add 1, 5 or 10 more (available on the Odoo store or from sales@latasys.com). Keys issued before this model keep their original numeric provider count. Inclusions - packs and providers alike - are changed centrally by LataSys and apply on the next daily license check, with nothing to reinstall and no new key needed. Help > About shows Included Apps with each pack's install state; keys issued before app entitlements existed include every pack.

Step 2 - Choose your privacy settings

The first item on the Getting Started checklist asks you to decide whether the connector may send all errors automatically to LataSys. When enabled, sync errors are sent to LataSys support as PII-redacted incident reports (the failing request and response, error details, module versions) and a support ticket is opened for you - nothing to collect, nothing to send manually. Recurrences of the same error are grouped and not re-reported for 24 hours, and every report sent is recorded in the instance chatter and the Sync Log.

This is off by default and entirely your choice: nothing leaves your database unless you enable it. You can change your mind at any time under Configuration > Settings > Privacy. With it off you can still share diagnostics on your own terms - Help > About > Submit Diagnostic Report sends a one-off redacted report, and Download Report lets you review exactly what it contains first.

Step 3 - Assign roles

Open Settings > Users, pick a user, and set the 3PL Connector role. There are three levels; each includes everything below it:

• Read Only - sees the dashboard, all operations data and the Sync Log. No buttons, no changes. For finance, customer service or anyone who needs visibility without risk.
• Ops - everything Read Only can, plus every day-to-day operation: send orders, poll statuses and returns, run inventory syncs, push products, create returns, retry and acknowledge log entries. Ops users cannot see credentials or change configuration.
• Admin - full access including credentials, providers, mappings and sync settings.

See Roles and security for the complete permission matrix.