GoFlow holds your channel orders. A 3PL that is not connected to your GoFlow account gets them through a script or file drop someone maintains.
Once an outside 3PL ships, tracking reaches GoFlow with the next upload, and Amazon or Shopify shows the order unshipped until then.
Counts change at the warehouse all day. Until GoFlow gets them, every listing it manages sells against an old number.
| iPaaS & Custom Builds | Legacy OMS | Pipe17 | |
|---|---|---|---|
| Native API-First Connectivity | ✅ | ❌ | ✅ |
| Pre-Built Commerce Connectors | ❌ | ❌ | ✅ |
| Custom Integration Mappings | ✅ | ❌ | ✅ |
| Advanced Order Orchestration | ❌ | ✅ | ✅ |
| Exception Management & Alerts | ❌ | ❌ | ✅ |
| Unified Inventory Management | ❌ | ✅ | ✅ |
| Rapid to Implement & Go-Live | ❌ | ❌ | ✅ |
| Easy to Add / Swap Channels & Flows | ❌ | ❌ | ✅ |
| Low Total Cost of Ownership (TCO) | ❌ | ❌ | ✅ |
Orders GoFlow collects from Shopify, Amazon, Walmart, and other channels come into Pipe17, where your rules assign each to a warehouse or 3PL.
Once a location ships, Pipe17 writes the tracking onto the GoFlow order, and GoFlow tells the channel it came from.
Pipe17 sends on-hand quantities from your warehouses and 3PLs to GoFlow. The listings GoFlow manages then sell against current counts.
is better with
Yes, Pipe17 connects to GoFlow when GoFlow is your order management system (OMS). Pipe17 pulls the orders GoFlow collects from channels such as Shopify and Amazon, sends each one to the warehouse or 3PL your rules choose, then posts tracking and on-hand inventory back to GoFlow. If GoFlow runs your warehouse instead, the GoFlow 3PL integration covers that direction.
The GoFlow OMS connector brings orders from GoFlow into Pipe17 and returns fulfillments and inventory to it, while the GoFlow 3PL connector pushes orders the other way, to a warehouse GoFlow runs. You can run both. Connect the 3PL connector first so its GoFlow warehouses exist in Pipe17, and the OMS connector can then report inventory totals to one of them.
Pipe17 pulls GoFlow orders in, and its order routing uses your rules to send each one to your own warehouse or to a 3PL connected to Pipe17, such as ShipHero. The pull covers the GoFlow statuses you choose, narrowed if you like to orders GoFlow has assigned to specific warehouses.
Pipe17 posts each shipment to the GoFlow order, and GoFlow passes the tracking on to that order's channel, whether Amazon, Walmart, or Shopify. GoFlow marks the order shipped once its boxes cover every line, which for a split order means after the last box posts. When each channel shows the order shipped depends on GoFlow's own connection to that channel.
Fulfillment by Amazon (FBA) orders, and Walmart orders shipped by Walmart Fulfillment Services (WFS), are fulfilled by the channel itself, and Pipe17 can bring them in for visibility only. It records them and never routes them to a warehouse or 3PL. Or leave channel-fulfilled orders out of the pull and bring in just the ones you ship.
Pipe17 sends absolute on-hand quantities to each GoFlow warehouse, so GoFlow and its listings match the stock your locations report in Inventory Visibility. Zero quantities are held back by default, which stops one bad count from emptying listings; switch zeros on when you want true stock-outs to reach GoFlow as well. Or send one combined total to a single GoFlow warehouse.
Pipe17 raises an exception in Exception Resolution, and the tracking GoFlow did not accept stays visible to your team instead of vanishing. Common causes are a carrier GoFlow does not list or an order canceled in GoFlow before the shipment posted. After you fix the cause, for example by setting a fallback carrier, re-accept the fulfillment in Pipe17 and it sends the shipment again.
In Pipe17, enter the API URL for your GoFlow subdomain and an API token from GoFlow Settings > API Tokens. Switch on locations before orders, fulfillments, and inventory, because a pulled order needs its GoFlow warehouse to exist in Pipe17. The first order pull begins at connection unless you set an earlier start date. The connector is built and maintained by Pipe17 as part of the Pipe17 Network.