Sprint Logistics adapter - process maps

Sprint Logistics adapter - process maps

How every flow in the LataSys 3PL Connector runs when the Sprint Logistics adapter is installed. Transport: REST v2 over HTTPS. Auth: HTTP Basic - the Sprint API key is the username, the key password is the password. Warehouses are identified by Sprint-issued GUIDs.

Shared behaviour for every flow below:

  • Triggers - the scheduler (per-instance cadences on the Synchronisation tab), the Run-an-Operation wizard, per-record buttons, or the inbound webhook.
  • Logging - every run writes a Sync Log entry: full request and response (URL, headers with credentials redacted, body), every Odoo action taken, and every record touched. Errors are retryable from the log entry.
  • 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
Trigger Test Connection button (instance form)
Calls Probe request against the API root
Outcome Draft instance moves to Connected; failure logged with the full HTTP exchange

2. Order push

Process diagram
Trigger Cron (order cadence), wizard, auto-send on confirmation
Direction Odoo -> Sprint
Data sent Recipient name, address, email, phone; SKUs and quantities; carrier/service from the carrier map; IOSS number where configured
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), webhook event, manual
Direction Sprint -> Odoo
Data received Status codes (mapped via the instance's Status Mappings), despatched lines, batch numbers, tracking
Odoo records Delivery picking validated; stock moves with lots; 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 cancellation
Trigger Order cancelled in Odoo
Calls Order cancel (or hold where cancel is no longer possible)
Outcome Binding closed; if Sprint already despatched, the order is flagged instead

5. Inventory sync

Process diagram

6. Product match and push
Match Fetch the Sprint item master; match Odoo products by SKU, then barcode; create bindings
Push Product-create for new items (SKU, name, barcode, dimensions - no personal data)
Update Product-update on changes (subject to Sprint enabling the endpoint per environment)

7. Returns

Process diagram

8. Carrier and status setup
Fetch Carriers Pulls Sprint's carrier/service list into the Carrier Mappings
Status defaults Load Missing Defaults seeds Sprint's status codes with canonical meanings

9. Webhook (inbound)
Endpoint Per-instance URL with a cryptographically random secret token
On event Payload logged; a targeted status check runs for the referenced order - polling remains the safety net

10. ASNs / GRNs

Implemented (announce inbound purchase receipts, reconcile goods received) but not released in this version - hidden and disabled by default.

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

    • Related Articles

    • Sprint Logistics adapter - setup and reference

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

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