Security, data protection and the Help menu

Security, data protection and the Help menu

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, how many 3PL providers you can connect (up to unlimited), the license expiry and how long your support entitlement runs; Help - About shows the current status.

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 more instances than the licensed provider count 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.

    • Related Articles

    • Trust, security & privacy

      We built Amazon Seller Sync to do one job well, keep your Shopify store and your Amazon Seller Central account in sync, while holding as little of your data as possible and protecting everything we do hold. This page explains, in plain language, ...
    • Install the app and assign roles

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

      This page is organised by symptom. Find the thing that is happening to you, read the cause, apply the fix. Almost every problem merchants hit with this app has one of a small number of causes, and the great majority are a gate that has not been ...
    • Settings reference

      Settings is where you manage the app's connection to Amazon, decide which marketplaces your store maps to, choose which AI engine writes your listing content, and look after the data the app stores in your Shopify store. It is organised into five ...
    • Working an error - retry, acknowledge, support tickets

      The three ways to act on a failed entry, plus the support tooling behind them - all built so nothing personal ever leaves your database. Working an error Retry. Re-executes the exact operation the entry refers to. A successful retry links back to the ...