The 3PL Connector ships with a Help menu (3PL Connector - Help) that gives every installation self-service access to the facts an operator, auditor or insurer needs.

What is in the Help menu

• Support & Documentation - opens the in-app help widget on the Help Center home.
• Data Protection Report (Admin role only) - generates a live, printable report about your database: configured instances, which flows are active, exactly which data categories each flow sends to and receives from your 3PL, who holds each connector role, log retention, and the security measures built into the module. Print it from the browser (Ctrl+P) to attach to compliance or insurance paperwork.
• License - the module's license (Odoo Proprietary License v1.0) and the third-party components it uses.
• About - module version, author, database, support contact.

How the connector protects data

• Role-based access. Three roles (Read Only, Ops, Admin) cover every screen and every model. Users without a role see nothing of the app. On shared databases, multi-company rules keep each company's 3PL data separate.
• Credential protection. API keys, secrets, passwords and tokens are readable only by the Admin role - enforced in the database layer, not just hidden in the UI. They are masked on screen, never copied when a record is duplicated, and automatically redacted from every logged HTTP header.
• Encrypted transport. All calls to your 3PL go over HTTPS with certificate verification and explicit timeouts.
• Authenticated webhooks. The inbound webhook URL contains a long random secret unique to each instance; calls without it get HTTP 403.
• Sync Log retention. Each instance has a "Keep Logs (days)" setting (default 90). A daily cleanup deletes older entries, including any transmitted payloads they contain.
• Redacted support tickets. "Raise Support Ticket" replaces names, addresses, emails and phone numbers with ***redacted*** before anything leaves your system, and only sends when a user presses the button.

What personal data leaves Odoo

Only fulfilment data, and only to the 3PL you configured: typically the delivery recipient's name, address, email and phone on order push and return labels, plus supplier business contact details if supplier push is enabled. The module never reads payment card data and sends nothing to LataSys automatically. The full per-flow breakdown is in your Data Protection Report.

License keys

The app is licensed per purchase with a signed license code from LataSys. Paste it under Settings - 3PL Connector - License Key. The code carries who it is licensed to, which 3PL providers you can connect, the license expiry and how long your support entitlement runs; Help - About shows the current status.

Newer keys name the built-in providers they include (Sprint Logistics, ShipHero, Amazon MCF). A named provider allows any number of its instances - staging and live share 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. Provider changes are made centrally by LataSys and apply on the next daily license check - no new key needed.

A license can also name the capability packs (companion apps) it includes. A pack works only when its module is installed and the license includes it; Help - About shows Included Apps with each pack's install state. Inclusions are changed centrally by LataSys and apply on the next daily license check - nothing to reinstall. Keys issued before app entitlements existed include every pack.

Codes are cryptographically signed (Ed25519) by LataSys. Your Odoo only holds the verification key, so codes cannot be forged or altered - changing a single character invalidates the signature. Without a key the app runs in evaluation mode; with a key, connecting a provider or custom slot the license does not cover is declined with a message to contact sales@latasys.com.

What stays your responsibility

Your contract and lawful basis with the 3PL, granting and reviewing user roles, server hosting and backups, the outgoing mail server, and assessing where your 3PL stores its data.