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

Prerequisites

• The LataSys 3PL Connector (core app) installed and licensed.
• A Sprint Logistics account with API access, and from their team:
• your API key and key password;
• the warehouse GUID for each warehouse that will fulfil for you;
• confirmation that the API key is enabled for the environment you are connecting (staging keys and live keys are enabled separately - ask for both, ahead of go-live).

Installation

Install the LataSys 3PL Connector: Sprint Logistics 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 HTTP Basic: the API key is the username and the key password is the password. On the instance's Connection tab:

1. Choose the environment - start with Sandbox/Staging.
2. The API root URL is set automatically per environment; override only if Sprint gave you a different host.
3. Enter the API key and key password, then press Test Connection. The instance moves from Draft to Connected and the full HTTP exchange is captured in the Sync Log.

Mappings

• Warehouses - this provider does not expose a warehouse list API: enter each mapping manually with the warehouse GUID Sprint issued you as the remote code.
• Carriers - press Fetch Carriers to pull the carrier/service list, then map each remote carrier to your Odoo delivery methods. Order in the list matters: the first matching mapping wins.
• Statuses - press Load Missing Defaults. The adapter seeds the provider's status codes with canonical meanings, including which codes count as despatched (triggering the write-back) and which as cancelled. Adjust labels freely; the canonical column is what drives behaviour.
• Requested Methods - press Load Requested Methods to pull the services Sprint accepts into the Accepted Services list and add a mapping row for every requested-delivery-method value your orders have used. Mapped values decide the service level sent on each order; anything unmapped falls back to the Default Service Level below.

Sprint Options tab

Shared options worth reviewing

These live on the core instance form and apply to every provider:

• Requested Method Field - the technical name of the sale-order field carrying the customer's requested delivery method. It feeds the Requested Methods mapping and the service sent to Sprint. Leave the default on databases migrated from the legacy integration; clear it if your orders only ever use Odoo's native Delivery Method.
• Order Reference Sent - whether Sprint receives the Odoo order number or the customer reference (falling back to the order number). The customer reference option suits sales-channel setups where the shop's own number should appear on despatch paperwork.
• Create Returns Locations (Returns settings) - creates a returns holding location per mapped warehouse under a '3PL Returns' parent outside every warehouse's stock tree, so restockable returned goods do not count towards availability, reservations or replenishment until someone transfers them back into stock.

Provider-specific behaviour

• Despatch statuses - orders are written back to Odoo when the status reaches a code the mappings mark as despatched; hold and approval-error codes surface as Hold on the order binding.
• Product updates - the product-update endpoint is enabled per-environment by the provider. If pushes of product changes return success-with-no-effect, ask their support to enable the endpoint for your key (creation is unaffected).
• IOSS - where the instance is IOSS-registered, the number is passed on non-UK orders (GB, NI, Channel Islands and Isle of Man count as UK).
• Returns - discovered returns include undeliverable parcels; processed returns are acknowledged back to the provider so they are not re-fetched.

Troubleshooting

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

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