WMS & Fulfilment Integration

ShipHero, connected
to everything around it.

Five bidirectional data flows. Orders in, purchase orders as ASNs, receipts out, stock updates out, shipments out. Supply Lens connects ShipHero to your ERP, storefronts, and finance systems — with every courier, channel, SKU, bundle, and warehouse configuration handled correctly.

ShipHero connects to
ShipHero data flows Supply Lens integration layer
Inbound to ShipHero
Orders BI-SYNC
ERP / Storefront
Purchase Orders → ASNs INBOUND
ERP → ShipHero
Outbound from ShipHero
Receipts (GRN) OUTBOUND
ShipHero → ERP
Stock / Inventory OUTBOUND
ShipHero → ERP / Channels
Shipments (fulfilment) OUTBOUND
ShipHero → ERP / Storefront
The five flows in detail

Every ShipHero data flow.
Every direction. Handled.

Each flow has its own logic, timing, and edge cases. Supply Lens handles all five, including the configuration decisions that make each one work correctly for your operation.

Orders
Bi-directional sync

Orders flow from your ERP or storefront into ShipHero as pick and pack instructions, and ShipHero order status events flow back to keep source systems current. Whether the order originates from Shopify, Unleashed, WooCommerce, or a marketplace, Supply Lens transforms it into the format ShipHero expects — with the correct channel mapping, warehouse assignment, and SKU resolution applied before transmission.

ShipHero's pick and pack workflows depend on receiving clean, complete order data. Partial or malformed orders stall on the warehouse floor. Supply Lens validates and enriches each order before it reaches ShipHero so your team works from accurate pick lists from the moment the order lands.

ERP → ShipHeroStorefront → ShipHeroChannel mappingSKU cross-referenceWarehouse routingOrder status sync back
Shopify / ERP / Marketplace
Supply Lens
ShipHero
Status updates
Purchase Orders → ASNs
ERP → ShipHero

When a purchase order is raised in your ERP — a supplier delivery, an intercompany transfer, or an inbound from a trading partner — Supply Lens transforms it into an Advanced Shipment Notice and sends it to ShipHero ahead of the goods arriving. ShipHero can prepare for the inbound, pre-allocate bin locations, and confirm receipt against expected quantities. SKU mapping, supplier references, and expected arrival dates are all carried through correctly.

PO → ASN transformationSupplier reference mappingInbound preparationExpected quantitiesIntercompany transfers
ERP Purchase Order
Supply Lens (ASN transform)
ShipHero ASN
Receipts (GRN)
ShipHero → ERP

When goods are received and confirmed in ShipHero — whether against an ASN or as an unplanned receipt — Supply Lens captures the goods received event and creates the corresponding receipt in your ERP. Stock levels update immediately, purchase orders are marked fulfilled to the received quantity, and discrepancies between expected and received quantities are recorded against the original PO for reconciliation. This closes the loop between what was ordered, what physically arrived, and what is now available to sell.

GRN creation in ERPStock level updatePO fulfilment matchingDiscrepancy handlingUnplanned receipts
ShipHero GRN
Supply Lens
ERP Receipt + Stock Update
Stock / Inventory
ShipHero → ERP / Channels

ShipHero is the physical source of truth for what is available in the warehouse. Supply Lens takes inventory position updates from ShipHero and pushes accurate available-to-sell quantities to your ERP, Shopify, and any other connected channel. Where you operate multiple warehouses or locations in ShipHero, each location's stock is handled independently and routed to the correct downstream ERP warehouse record or channel availability figure.

Available-to-sell quantityWarehouse / location mappingMulti-locationERP stock updateChannel availabilityScheduled or triggered
ShipHero Stock
Supply Lens (location map)
ERP + Shopify + Channels
Shipments (fulfilment)
ShipHero → ERP / Storefront

When ShipHero confirms a shipment — pick complete, label printed, carrier collected — Supply Lens captures the despatch event and distributes it to all connected downstream systems. The ERP sales order is marked dispatched. The Shopify fulfilment is created with the carrier name and tracking number. The customer notification fires. Where an order ships in multiple consignments, each shipment event records separately against the open order, keeping the remaining balance accurate throughout.

ShipHero's native carrier integrations cover a wide range of services. Supply Lens maps the carrier and service codes ShipHero uses to the labels each downstream system expects, so tracking URLs resolve correctly and carrier records land in the right ERP field every time.

ERP despatch updateShopify fulfilment creationTracking pushCarrier code mappingPartial shipmentsCustomer notification
ShipHero Despatch
Supply Lens
ERP + Shopify + Customer
Configuration layer

The decisions that make
a ShipHero integration
actually work.

Connecting to the ShipHero API is the easy part. Getting it working correctly for your operation requires a configuration layer that knows how your couriers, channels, SKUs, bundles, and warehouse locations map across every system. That is what Supply Lens handles.

Courier service mapping
ShipHero uses its own carrier and service codes. Supply Lens maps these to the labels your ERP, storefronts, and customers expect — and translates inbound service preferences back into ShipHero's format for order routing.
Royal Mail 48 → RM48 in ERP
UPS Ground → UPS-GND
FedEx Priority → FDX-P
Per-channel carrier preferences
Channel mapping
Orders from different sources need to reach ShipHero tagged to the correct store. Each source system maps to a defined ShipHero store so picking workflows, SLAs, and packing rules apply correctly per channel.
Shopify DTC → DTC store
ERP B2B orders → wholesale store
Marketplace → channel store
Multi-brand routing
SKU mapping
Your ERP, Shopify, and ShipHero may hold the same product under different codes. Supply Lens maintains the cross-reference table so every order, ASN, receipt, and stock update carries the right identifier for each system without manual lookup.
Shopify variant ID → ERP code
ERP code → ShipHero SKU
Retailer barcode → internal SKU
Persistent, maintained mapping
Bundle & kit handling
Bundles sold as a single SKU in your storefront or ERP need to reach ShipHero as their component parts for individual pick lines. Supply Lens explodes bundles at the integration layer so ShipHero always receives the correct items to fulfil each order.
Bundle SKU → components
Quantity multipliers applied
Mixed bundle/unit orders
Stock reflected at component level
Warehouse & location mapping
Where you operate multiple warehouses or locations in ShipHero, Supply Lens applies routing rules at the point of order creation and maps each location's stock back to the correct ERP warehouse record or channel availability figure.
Order type → warehouse
Channel → location rules
Multi-location stock sync
ERP warehouse mapping
Error monitoring
Every flow across the ShipHero integration is monitored in real time. Unmatched SKUs, failed order transmissions, rejected ASNs, and GRN discrepancies surface as alerts before they become warehouse floor problems or affect customer deliveries.
Unmatched SKU alerts
Failed transmission notifications
GRN discrepancy flags
Dashboard + email alerts
Where ShipHero integrations break

The specifics that catch
every generic connector out.

ShipHero has a well-structured API and strong pick and pack workflows. The complexity is in the configuration — how your channels, SKUs, bundles, and warehouse locations map across systems.

We sell bundles on Shopify but ShipHero just sees one SKU and doesn't know what to pick.

Bundle explosion happens at the integration layer before the order reaches ShipHero. When a bundle SKU is detected, Supply Lens expands it into its component items with the correct quantities. ShipHero receives individual pick lines for each component. The Shopify fulfilment is created against the original bundle SKU. Stock updates return at component level, keeping your ERP position accurate regardless of how the bundle was sold.

ShipHero marks an order as shipped but the tracking number never makes it back to Shopify or our ERP.

Supply Lens listens for ShipHero shipment events and distributes them immediately to every downstream system. The carrier and tracking number are mapped to the format each system expects — ShipHero's carrier codes become the correct carrier name in Shopify's fulfilment API and the correct carrier field in your ERP. The event fires once in ShipHero and lands correctly everywhere without any manual step.

When stock arrives at the warehouse and is received into ShipHero, our ERP doesn't update for hours.

The receipt flow closes this gap. When goods are confirmed as received in ShipHero, Supply Lens creates the corresponding GRN in your ERP and updates stock immediately. Purchase orders are marked fulfilled to the received quantity. If the delivery is short or contains unexpected quantities, the discrepancy records against the original PO so nothing is absorbed silently into your stock position.

Our Shopify SKUs and ShipHero SKUs are different. Every sync fails the moment there's a mismatch.

Supply Lens maintains a persistent cross-reference table between Shopify variant IDs, ERP product codes, and ShipHero SKUs. The mapping is built once from your product data and maintained as part of the ongoing service. When a new product is added to your catalogue, the mapping entry is added before the first order for that product arrives. Mismatches are caught, flagged, and resolved before they cause a fulfilment failure on the warehouse floor.

Getting started

A complete ShipHero integration
in days, not weeks.

Most ShipHero integration projects follow a structured path. You give us what we need, we configure the five flows and the configuration layer, test end-to-end, and go live.

What we need from you
ShipHero API credentials
API token from your ShipHero account settings
ERP and storefront credentials
Unleashed, Shopify, Enterpryze, or whichever systems ShipHero needs to connect to
Warehouse and location list
Which ShipHero warehouses or locations you operate and how orders should route between them
Carrier and service list
Which carriers are active in ShipHero and what codes each downstream system expects
Bundle definitions
Any SKUs sold as bundles that need to reach ShipHero as individual component pick lines
Sample orders and products
To validate SKU mapping, bundle explosion, channel routing, and carrier handling before go-live
How we get you live
1
Scope
Credentials, flows required, warehouse rules, carrier list, and bundle definitions collected.
2
Configure
All five flows built in staging with carrier map, channel routing, SKU mapping, and bundle config applied.
3
Test
End-to-end run across each flow — order in, ASN, GRN, stock update, and shipment validated with real data.
4
Go live
Production activated. All flows monitored from day one.

Ongoing support includes carrier mapping updates, SKU mapping maintenance, and warehouse routing changes as your operation evolves.

Ready to connect ShipHero
to your full operation?

Five flows, fully configured. Orders, ASNs, receipts, stock, and shipments — all automated. 30-day trial available.