| iPaaS & Custom Builds | Legacy OMS | Pipe17 | |
|---|---|---|---|
| Native API-First Connectivity | ✅ | ❌ | ✅ |
| Pre-Configured 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) | ❌ | ❌ | ✅ |
Routing rules you set send each order to the Broad Reach warehouse in its destination country when that warehouse has the stock.
Each Broad Reach warehouse's available count arrives in Pipe17 per SKU, and every channel sells against that count.
Pipe17 tells Broad Reach which inbound stock and returns to expect, then records what each warehouse actually received.
is better with
Yes, Pipe17 integrates with Broad Reach Logistics, an Asendia company, through a pre-built connector that Pipe17 maintains. A brand already shipping with Broad Reach connects its existing client account, and a brand still choosing a 3PL can add Broad Reach next to the warehouses it runs today. Access stays limited to that client account, which keeps other Broad Reach clients' products and stock out of your Pipe17 data.
Pipe17 is an order management system (OMS) that works with Broad Reach Logistics and with the stores, marketplaces, and ERP you already run. It takes the place of the separate iPaaS and legacy OMS that cross-border fulfillment built from parts requires. Order rules, inventory, and the connection to each Broad Reach warehouse sit in one platform your team configures without writing code.
Yes, Pipe17's order management treats each Broad Reach warehouse as its own location, and routing rules choose among them alongside your warehouses, stores, and any other 3PL in your Pipe17 Network. A rule can ship orders bound for Canada from a Canadian warehouse and U.S. orders from a U.S. one, or weigh available stock and the sales channel. Broad Reach handles the border crossing for parcels that cross.
Pipe17 creates each purchase order (PO) or transfer in Broad Reach's system before the goods arrive, which gives the warehouse the same heads-up an advance ship notice (ASN) does. Received quantities then come back per line and lot and count toward the stock every channel can sell, including stock that showed up with no PO.
Broad Reach receives and inspects returned units, and Pipe17 keeps the record your team acts on. Each approved return authorization (RMA) is announced to the warehouse ahead of time. When Broad Reach checks units in, Pipe17 shows which returns arrived and which units were marked damaged, the facts behind each refund or restock decision.
Setup starts with API credentials and your client account name, arranged through Broad Reach. In Pipe17 you enter them, pull Broad Reach's warehouses in as locations, map SKUs, and turn on each flow you need, testing first on chosen order numbers and SKUs. Shopify, NetSuite, or whichever store and ERP you run connect to Pipe17 separately.
Yes, Pipe17's managed EDI receives each retailer's EDI purchase orders and routes them to a Broad Reach warehouse like any other order. Ship notices, invoices, and the retailer's other documents go back to that retailer through the same managed EDI. Broad Reach picks, packs, and ships, while Pipe17 runs the order and the paperwork around it.