ShipHero connected to your fulfillment operation
Ecom supports sending fulfillment work to ShipHero and receiving events back through its inbound connection. We review how your orders and warehouse updates should move between the two systems, then test those flows before launch.
The connector, and its version
- API
- ShipHero
- Version
both directions
Supports sending fulfillment work and receiving platform events. The team confirms which order and warehouse updates your setup will use.
And what goes the other way
-
Work to the warehouse
Orders and their fulfilment intent go out through the fulfilment connector.
-
Events back
Inbound platform events are normalised by the adapter into the same shape every other source produces, so downstream nothing knows or cares that they came from ShipHero.
Historical fulfillment data can be reviewed for import during migration. Agree the records and date range needed before the cutover.
What people ask before connecting
We already run ShipHero. Do we have to move off it?
No: that is the reason this integration exists in both directions. Your system stays the system of record for the warehouse, and ours stays the system of record for the order.
What does "both directions" actually mean?
The supported setup can send fulfillment work to ShipHero and receive events back. Confirm which events and updates your operation needs during onboarding; a two-way connection does not mean every field moves in both directions.
The rest of the stack
Ready to move your orders faster?
Tell us what you ship and how much of it, and a specialist comes back within one business day.