Huboo adapter - process maps

Huboo adapter - process maps

How every flow in the LataSys 3PL Connector runs when the Huboo adapter is installed. Transport: Huboo public REST API v2 over HTTPS (https://api.huboo.uk/v2; a sandbox base URL, if issued during Huboo onboarding, goes in the instance's Base URL field). Auth: a plain API token sent as a Bearer token. Warehouse mappings hold numeric site ids (Huboo's goods-in sites).

Shared behaviour for every flow below:

  • Triggers - the scheduler (per-instance cadences on the Synchronisation tab), the Run-an-Operation wizard, or per-record buttons. There is no webhook - polling carries every flow.
  • Logging - every run writes a Sync Log entry: full request and response (URL, headers with the token redacted, body), every Odoo action taken, and every record touched. Errors are retryable from the log entry.
  • Rate limit - 120 requests/minute per account. A 429 logs a retryable error carrying Huboo's Retry-After value; the next scheduled run retries.
  • Watermarks - each flow stamps its last-run time on the instance; the scheduler only fires when the cadence has elapsed.
  • License - flows pause if the licensing service reports the installation suspended for non-payment.

1. Connection test and site fetch
Test Connection GET /sites - validates the token AND lists every Huboo site with its numeric id
Fetch Warehouses Offers the same sites on the warehouse mapping line, so the site id is picked rather than typed

2. Order push

Process diagram
Trigger Cron (order cadence), wizard, auto-send on confirmation
Direction Odoo -> Huboo
Data sent Recipient name, address (line_two required - street2 or city), email, phone; product identifiers (barcode, SKU fallback) with quantities and per-unit sales values; shipping service (when resolved); order note
Odoo records 3PL Order binding (pending -> sent)
Failure Retryable Sync Log error; nothing partially written

3. Status poll and despatch write-back

Process diagram
Trigger Cron (status cadence), manual
Direction Huboo -> Odoo
Data received Order status (Complete / Hold / In Progress / Cancelled / Error / Unprocessable); per-parcel tracking groups with carrier name, carrier service, tracking number and URL, and the lines in each parcel
Odoo records Delivery picking validated; backorders; carrier + tracking on the picking; binding state despatched
Failure Savepoint-protected - a failed write-back leaves no partial documents; error is retryable

4. Order amendment and holds

Not available in Huboo's public API. To change a submitted order, cancel it (while Huboo still allows it) and resend, or amend it in the Huboo portal. Huboo itself may place an order on Hold - that surfaces through the status poll.

5. Order cancellation
Trigger Order cancelled in Odoo
Calls DELETE /order/{id}
Outcome 204 closes the binding. Once fulfilment has progressed, Huboo answers 400 (ORDER_COMPLETED / ORDER_LOCKED / ...) and the order is flagged instead

6. Inventory sync

Process diagram

Honest maths: allocated units are already promised to open Huboo orders, so the available quantity is what Odoo can still sell. Batch totals are Huboo's total per batch (not reduced by allocations), so lot detail can sum above the available quantity. Batch control is an account feature Huboo enables on request.

7. Product match and push
Match GET /products (client SKU, identifier/barcode, title, Huboo P-Number); Odoo products match by SKU and bindings are created
Push POST /products, CREATE-ONLY: identifier (barcode or SKU fallback), title, client SKU, weight in integer grams, customs (commodity code, country of origin, sales price, description). A binding already synced raises - Huboo has no product update endpoint; amend in the Huboo portal

8. ASN and GRN

Process diagram
ASN cancel Not available in the API - cancel in the Huboo portal (the local ASN can be reset manually)
Batches on ASNs Sent only when a move has exactly one known lot; requires Huboo batch control (on request)

9. Returns

Not available: Huboo's public API has no returns endpoints. Returns are processed in the Huboo portal; book the resulting stock movements in Odoo manually.

10. Webhooks

Not available - all flows run on the polling cadences. Size the status and stock cadences with the 120 requests/minute account rate limit in mind.

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

    • Related Articles

    • Huboo adapter - setup and reference

      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 Flow Supported Order ...

    • ShipHero adapter - process maps

      How every flow in the LataSys 3PL Connector runs when the ShipHero adapter is installed. Transport: GraphQL over HTTPS. Auth: Bearer JWT with refresh - enter the developer-user email/password (the adapter obtains and refreshes tokens itself) or paste ...

    • MintSoft adapter - process maps

      How every flow in the LataSys 3PL Connector runs when the MintSoft adapter is installed. Transport: REST v1 over HTTPS. Auth: the MintSoft username/password are exchanged for a 24-hour API key (POST /api/Auth), cached ~23h and sent as the ms-apikey ...

    • ShipBob adapter - process maps

      How every flow in the LataSys 3PL Connector runs when the ShipBob adapter is installed. Transport: ShipBob Developer API 2026-07 (REST/JSON) over HTTPS - api.shipbob.com, or sandbox-api.shipbob.com on sandbox instances. Auth: Personal Access Token as ...

    • Clarus WMS adapter - process maps

      How every flow in the LataSys 3PL Connector runs when the Clarus WMS adapter is installed. Transport: hybrid - writes are JSON:API REST under /api/..., reads are GraphQL via POST /graphql, both on the tenant's own subdomain ...