Orders (create, amend, cancel), despatch write-back with multi-parcel tracking, available stock, item create and update, ASNs, goods received confirmations from item receipts, warehouse and carrier lookups.
Not part of this integration: returns, order holds, the supplier master and ASN cancellation - all handled in the Infoplus UI.
Install LataSys 3PL Connector: Infoplus Adapter alongside the core app. The provider appears in the instance form's Provider list as soon as the module is installed - no configuration is needed to register it.
| Field | Value |
|---|---|
| Provider | Infoplus |
| Base URL | required - https://<yourcompany>.infopluswms.com/infoplus-wms/api |
| API Key | sent in the API-Key header |
| LOB ID | on the Infoplus Options tab |
| Customer No | on the Infoplus Options tab |
| API Version | v1.0 by default; goods-received lookups always use v2.0 |
Press Test Connection - it lists the warehouses with their numeric ids and echoes the LOB and Customer No in use.
Warehouses. Press Fetch Warehouses and put the numeric warehouse id in each mapping's remote code, or set a default.
Carriers. Press Fetch Carriers. Infoplus requires a numeric carrier id on every order - map your Odoo carriers or set a default carrier id, otherwise pushes fail with a message telling you so.
Statuses. Press Load Missing Defaults: Pending, Processing, On Hold, Shipped, Complete, Cancelled.
| Field | Meaning |
|---|---|
| LOB ID | Line of Business - the brand whose stock is drawn on. Required. |
| Customer No | The customer record within that LOB that orders are raised against. |
| Default Carrier ID | Numeric carrier id used when the carrier mapping does not resolve one. |
| Default Warehouse ID | Numeric warehouse id for unmapped Odoo warehouses. |
| API Version | Default version for orders and items (v1.0 / v2.0 / v3.0 / beta). |
LOB is not optional. The Line of Business identifies whose stock an order draws on. A wrong LOB files orders against another brand's inventory, so the adapter refuses to run without it rather than guessing.
Base URL is per account. Infoplus hosts every customer on its own domain, so there is no default. Setting it wrong produces a clear error instead of a mystery 404.
Amendment merges rather than replaces. Infoplus updates through a PUT carrying the whole record, so the connector reads the current order first and merges the changed parts in - fields it does not manage survive instead of being blanked.
GRNs come from item receipts. Infoplus records receipts separately from the ASN, so goods received are summed from the receipts matching the ASN's PO number, always at v2.0 regardless of the instance's configured version.
Weights are pounds. Odoo kilograms are converted on item push.
| Symptom | Cause and fix |
|---|---|
| "No Infoplus Base URL on the instance" | Set https://<yourcompany>.infopluswms.com/infoplus-wms/api. |
| "No Infoplus LOB ID on the instance" | Ask your warehouse for the LOB ID and set it on the Options tab. |
| "No Infoplus carrier id for this order" | Map the Odoo carrier to its numeric Infoplus id, or set a default. |
| 401 on every call | Missing or invalid API key - regenerate it in the Users table. |
| GRN shows nothing received | Receipts are matched by PO number; check the ASN reference matches the PO in Infoplus. |
Part of the LataSys 3PL Connector. Support: support@latasys.com | Help Center