Everything you need to connect the LataSys 3PL Connector to ShipHero: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour.
| Flow | Supported |
|---|---|
| Order push and despatch write-back | Yes |
| Order cancellation | Yes |
| Inventory sync (lot level) | Yes |
| Product match and push | Yes |
| Supplier push | Yes |
| Returns (labels, discovery, grading, credits) | Yes |
| Warehouse list fetch | Yes |
| Carrier list fetch | Yes - from the experimental API (where the account has it) or compiled from historical order labels |
| ASNs / GRNs (purchase orders) | Implemented, not released in this version |
Install the LataSys 3PL Connector: ShipHero 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.
Authentication is a Bearer token with refresh:
Tokens live around 28 days. The daily token cron renews them two days before expiry; you never manage tokens manually. If credentials are revoked on the provider side, flows log a clear token error in the Sync Log until they are re-entered.
Press Register Webhooks (Synchronisation tab) to subscribe ShipHero's push events - shipment updates, order cancellations, inventory updates, return updates and purchase-order updates - to this instance's webhook URL. Events trigger a targeted check the moment they arrive; polling stays on as the safety net. Registering again is safe: already-registered subscriptions are recorded and skipped.
| Field | What it does |
|---|---|
| Customer Account ID | Only for ShipHero 3PL master accounts: the client account this instance acts for. Sent with every order, product, return and purchase order call, and used to filter reads so this instance only sees that client's data. Leave empty on a normal (non-3PL) ShipHero account |
| Fallback Carrier | Carrier sent on outbound orders when neither the carrier mapping nor the requested-method mapping resolves one. 'Cheapest' lets ShipHero rate-shop |
| Fallback Service | Shipping method sent on outbound orders when no mapping resolves one |
| Order Tags | Comma-separated tags added to every order sent to ShipHero, alongside the customer reference |
| Return Carrier | Carrier for return labels when the return has no mapped carrier. 'generic' produces an unbranded label |
| Return Service | Shipping method requested on return labels |
| Return Weight | Where the return parcel weight comes from: the fixed box dimensions below, or the total weight of the returned products (falling back to the fixed weight when the products have no weight set) |
| Return Box Weight / Length / Width / Height | Parcel dimensions sent on return labels, in the units of the ShipHero account (weight usually lbs) |
| Returns Window (days) | Only fetch returns created in the last N days on each returns poll. 0 sweeps the full return history every poll - slow on accounts with many returns |
The carrier-source toggles (Use Historical Orders / Use Experimental Functionality) also live here - see Mappings above.
These live on the core instance form and apply to every provider:
| Symptom | Likely cause |
|---|---|
| Token error on every flow | Developer-user credentials changed or revoked - re-enter them |
| Connection ok but no despatches | Status Mappings missing despatched codes - Load Missing Defaults |
| Slow syncs on large catalogues | Quota pacing - reduce cadence or stagger product pushes |
| Carrier not applied to deliveries | No matching carrier mapping - add the remote carrier/service pair |
See also: ShipHero adapter - process maps for the end-to-end flow diagrams.
ShipHero is a trademark of its respective owner; the name is used solely to identify the service this module interoperates with.