Clarus WMS adapter - process maps

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 (https://<subdomain>.api.clarus.ws; the Base URL is mandatory, there is no default host). Auth: email/password sign-in returning a token sent as Authorization: Token token="...", email="..."; ONE concurrent session per user (dedicated API user required); the adapter re-signs-in once on a 401.

Shared behaviour (identical to every adapter): scheduler/wizard triggers, full request+response capture in the Sync Log with redacted credentials, retryable errors, per-flow watermarks, and license suspension pausing all flows.

1. Token lifecycle

Process diagram

2. Connection test and catalogue fetches
Test Connection warehouses query; Draft -> Connected
Fetch Warehouses warehouses.all -> numeric ids into the Warehouse Mappings
Fetch Carriers / Load Requested Methods carriers.all with services - the same catalogue resolves codes to the numeric ids orders take

3. Order push

Process diagram
Data sent Recipient name, address, email, phone; SKUs (as Clarus product ids) and quantities; warehouse and account; order notes
Odoo records 3PL Order binding (pending -> sent)

4. Status poll and despatch write-back

Process diagram

5. Order amendment and cancellation
Amend PATCH /api/goods_outs/{id} - PENDING only; header + ADD lines; skipped quantity changes are reported in the sync log for manual adjustment inside Clarus
Cancel POST /api/goods_outs/{id}/cancel - PENDING only; later cancellations happen inside Clarus
Hold Not available - no hold API

6. Inventory sync

stock_balances query per mapped warehouse (scoped to the Account ID), cursor-paginated -> per-SKU available quantity (allocated, picked, held and non-pickable excluded) -> inventory adjustments applied immediately or staged for review (per instance setting). No batch detail: Clarus has no first-class lots.

7. Product match and push
Match products query (code, description, barcode), cursor-paginated; match by SKU then barcode; bindings created
Push POST /api/products for new SKUs; PATCH /api/products/{id} when the SKU already exists at Clarus (looked up by code) - no personal data

8. Supplier push
Trigger Supplier queued on the Suppliers screen
Calls POST /api/suppliers (code, name, description, active)
Data sent Supplier name and contact reference only

9. ASNs and GRNs

Process diagram

No ASN cancel endpoint - withdraw receipts inside Clarus.

10. Returns

Not available: Clarus WMS has no returns API - handle returns inside Clarus. The connector hides the returns flows on Clarus instances.

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

    • Related Articles

    • Clarus WMS adapter - setup and reference

      Everything you need to connect the LataSys 3PL Connector to Clarus WMS: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. What this adapter provides Flow Supported Order push and despatch write-back Yes 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 ...

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