Everything you need to connect the LataSys 3PL Connector to Huboo: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. The adapter speaks Huboo's public REST API v2.

What this adapter provides

Prerequisites

• The LataSys 3PL Connector (core app) installed and licensed.
• A Huboo account with API access and an API token generated in the Huboo dashboard.
• If you want batch/expiry traceability (lots): batch control is an account feature Huboo enables on request - contact Huboo support before switching on "Products Use Batch/Lot Tracking".

Installation

Install the LataSys 3PL Connector: Huboo Adapter module. The provider then appears in the provider list when creating a 3PL instance, along with its provider card (API operations reference) under Configuration - Providers.

Connection setup

Authentication is a plain bearer token. On the instance's Connection tab:

1. Paste the Huboo API token into the API Key field - it is sent as Authorization: Bearer ... on every call.
2. Choose the environment. Huboo's sandbox base URL is not publicly documented - both environments default to the production URL (https://api.huboo.uk/v2). If your Huboo onboarding pack includes a sandbox base URL, put it in the Base URL field of the sandbox instance.
3. Press Test Connection - it validates the token and lists your Huboo sites with their numeric ids, which you need for the warehouse mappings next.

Mappings

• Warehouses are Huboo sites - press Fetch Warehouses and put the numeric site id in the warehouse mapping's remote code. The site id tells ASNs which goods-in site the stock is heading to.
• Shipping service is a free string - Huboo publishes no carrier/service catalogue; the shipping_service value on an order is a name agreed with Huboo (for example "Two day delivery"). Map your Odoo delivery methods onto those names in the carrier mapping table (like the Sprint adapter), or map requested-method values in the Requested Methods table. Where no mapping matches, the instance's Default Shipping Service is sent; leave everything empty to let Huboo apply the account's default service.
• Statuses - press Load Missing Defaults. Complete triggers the despatch write-back; Hold, Error and Unprocessable surface as Hold; Cancelled follows your remote-cancel policy.

Huboo Options tab

Provider-specific behaviour

• Order reference - the configured order reference (Odoo order number or customer reference) is sent as Huboo's client_order_id; Huboo's own order id (for example 1001-1618395894-6076c2...) becomes the remote reference.
• Product identifier - Huboo identifies stock by the product identifier, usually the barcode. The adapter sends the product's Barcode, falling back to the Internal Reference (SKU) when there is no barcode; a product with neither is refused.
• Address line two is mandatory - Huboo requires line_two on every order address. When the delivery address has no second street line, the city is sent instead.
• Sales values - Huboo requires a per-unit sales value (minimum 0.01) on every order line; free items are declared at the minimum.
• Despatch - GET /order/{id}/tracking reports one group per parcel. All dispatched groups are aggregated: quantities per SKU, every tracking number (comma-joined), carrier/service/URL from the first parcel. The tracking feed carries no batch detail, so despatches book un-batched.
• Stock - the canonical quantity is the available quantity: total_quantity - total_allocated_quantity (units already allocated to open Huboo orders are not sellable again). With lot tracking on, GET /batches merges batch references, quantities and best-before dates into the stock lines - note batch totals are Huboo's total per batch (not reduced by allocations), so lot detail can sum above the available quantity.
• ASNs - announced with the estimated date, package type, site id and item identifiers (plus batch reference/BBE date when the receipt move has exactly one known lot). Huboo's response includes a label address that must appear exactly on the shipment label (its first line is the ASN id) - the adapter posts it to the receipt's chatter. There is no ASN cancel endpoint.
• GRNs - polled from GET /delivery-receipts, matched by the Huboo ASN id; multiple receipts for one ASN aggregate, batch detail included where present.
• Product push is create-only - Huboo's public API has no product update endpoint. Pushing a binding that is already synced raises instead of silently re-creating; amend products in the Huboo portal.
• Rate limit - 120 requests/minute per account. A 429 response is logged as a retryable error including Huboo's Retry-After value; the flow's next scheduled run retries (no in-process retry).
• No webhooks - polling only - all updates arrive via the scheduled polls; set the status and stock cadences accordingly.

Troubleshooting

See also: Huboo adapter - process maps for the end-to-end flow diagrams.

Huboo is a trademark of its respective owner; the name is used solely to identify the service this module interoperates with.