ShipHero adapter - process maps

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 an existing refresh token. Access tokens live ~28 days; the daily token cron renews them two days early. ShipHero request quotas (credits) are respected.

Shared behaviour (identical to every adapter): scheduler/wizard/webhook 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 warehouse fetch
Test Connection Authenticated probe; Draft -> Connected
Fetch Warehouses Pulls ShipHero warehouse ids into the Warehouse Mappings

3. Order push

Process diagram
Data sent Recipient shipping/billing name, address, email, phone; SKUs and quantities; warehouse assignment
Odoo records 3PL Order binding (pending -> sent)

4. Status poll and despatch write-back

Process diagram

5. Order cancellation
Trigger Order cancelled in Odoo
Calls order_cancel mutation
Outcome Binding closed, or flagged if already despatched

6. Inventory sync

Stock query per mapped warehouse -> per-SKU/lot targets -> inventory adjustments applied immediately or staged for review (per instance setting), with the ShipHero counts authoritative and an Inventory Sync report of adjusted/unchanged/discrepancies.

7. Product match and push
Match Product catalogue query; match by SKU then barcode; bindings created
Push product_create mutation for new items - no personal data

8. Supplier push (ShipHero-specific)
Trigger Supplier queued on the Suppliers screen
Calls vendor_create mutation
Data sent Supplier company name, contact, address, email, phone (business contact data)

9. Returns

Process diagram

10. Webhook (inbound)

Per-instance secret-token URL; events are logged and trigger a targeted status check; polling remains the safety net.

11. ASNs / GRNs (purchase orders)

Implemented on ShipHero's PO API (po_create / po_get) but not released in this version - hidden and disabled by default.

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

    • Related Articles

    • ShipHero adapter - setup and reference

      Everything you need to connect the LataSys 3PL Connector to ShipHero: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. What this adapter provides Flow Supported Order push and despatch write-back Yes Order ...

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

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