| 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) | ❌ | ❌ | ✅ |
Pipe17 buys the lowest Easyship rate for the named courier. When none is named, or none of its rates return, Pipe17 takes the lowest overall.
Easyship returns the label inside its purchase reply, one per carton, and Pipe17 stores it with the tracking number for the packer to print.
For an international parcel whose shipment lists its items, Pipe17 passes each item's description, quantity, weight, value, Harmonized System (HS) code, and origin to Easyship.
is better with
The Easyship integration buys courier labels through Easyship's shipping API for shipments packed in Pipe17. A store associate in the StoreOps app, or any system that calls the Pipe17 API, requests the label on a shipping request. Pipe17 then prices the carton with Easyship, buys the lowest matching courier rate, and keeps the label, tracking number, and courier service on the shipment. The connector is Pipe17's to maintain.
Yes, for a shipment that lists its items, Pipe17 sends each item's description, quantity, weight, declared value, Harmonized System (HS) code, and origin country to Easyship with the carton's details, and Easyship prices the parcel across the courier services it can offer. A domestic parcel needs none of those details, and Easyship prices it from the carton alone.
Pipe17 picks the lowest Easyship rate from the courier named on the request. When no courier is named, or that courier returns no rate, Pipe17 picks the lowest rate from any courier. Easyship first prices the carton across its courier services, Pipe17 applies that rule to the list, and a second call buys the chosen rate. The courier service bought comes back on the label record.
Pipe17 cancels the shipment in Easyship and marks the label pending. Easyship confirms in its reply or later through a shipment-cancelled webhook, and Pipe17 records the refund as accepted or rejected on the label. When the refund comes back rejected, Pipe17 raises an exception with the reason given. The voided label is kept on record, and the packer asks for a replacement.
Yes, enter your production Easyship API key in the connection in Pipe17 and the integration runs on your Easyship account, with your courier accounts and rates, and labels bill there. Pipe17 tests the key with Easyship as part of connecting. With the key field empty, the connector runs on the account Pipe17 manages and no Easyship signup is needed on your side.
The Easyship integration defaults to PDF labels, with PNG and Zebra Programming Language (ZPL) where the courier allows it. One format applies per Easyship integration, chosen for the printers at your locations, and the file arrives inside the purchase reply. Pipe17 stores it with the tracking number and courier service, and the packer prints it on the spot.
Yes, one organization can connect both, and each store picks its label provider from its StoreOps settings or falls back to the organization-wide choice. A store set to Easyship and a store set to the EasyPost integration pack the same way, because Pipe17 resolves the provider behind each request for a label.
Add the Easyship integration and choose a label format. Leave the API key empty for the managed account, or enter your own production key. Then point a store at Easyship in its StoreOps settings, or leave the organization-wide choice. Your own key adds one step: create a webhook in your Easyship dashboard for the shipment-cancelled event at the URL Pipe17 shows, and paste its secret into the connection.