Integrations
Your clients' orders land in ShipFlow without re-keying.
Every connection runs through one pipeline. Orders arrive, items are matched by SKU or barcode, anything that cannot be matched waits for a person instead of being guessed, and shipments and stock go back to wherever the order came from.
Shopify
Fulfillment requests become warehouse orders the moment the merchant asks; tracking and stock go back on their own.
- In
- Fulfillment requests, order edits and cancellations, products and variants.
- Out
- Fulfillments with tracking, available stock at your location, accept or reject of requests.
Walmart Marketplace
Released orders are pulled and acknowledged without anyone watching Seller Center.
- In
- Released orders and cancellations.
- Out
- Shipping updates with carrier, method and tracking; inventory per ship node.
Amazon
Seller-fulfilled orders arrive with the buyer's address and go back confirmed with tracking; nobody re-keys a Seller Central order.
- In
- Unshipped and partially shipped seller-fulfilled orders, cancellations.
- Out
- Shipment confirmations with carrier, method and tracking; offer quantities.
Mirakl
A seller's orders on any Mirakl-powered marketplace become warehouse orders and are accepted; shipments, partial shipments and offer quantities go back.
- In
- Orders awaiting acceptance and orders to ship, cancellations, refund requests.
- Out
- Order acceptance, tracking and ship confirmations, partial shipments, offer quantities.
Rithum
Every channel a seller runs through ChannelAdvisor lands as one order stream, and shipments go back per item.
- In
- Ready-to-ship orders with items, cancellations.
- Out
- Shipments with carrier, class and tracking; quantities per distribution centre.
ShipStation
Orders and stores already in ShipStation flow through; labels printed there attach to packages.
- In
- Orders, stores, label batches.
- Out
- Order status, package weights, tracking scans.
QuickBooks
Invoices raised in ShipFlow land in the ledger without re-keying.
- In
- Customers and items.
- Out
- Invoices and charges.
Yoke EDI
Trading partners that speak EDI send 940s and get 945s back.
- In
- Warehouse shipping orders and stock transfers (940 / 943).
- Out
- Shipment and receipt advice (945 / 944 / 856).
SFTP / CSV
Clients on nothing but spreadsheets drop files and the orders appear.
- In
- Orders, items and expected receipts as CSV on hosted or your own SFTP, with saved column mappings.
- Out
- Shipment files on ship and a stock file on a schedule; bad rows returned with a reason.
Public API & webhooks
Anything else your clients run talks to the warehouse directly.
- In
- Items, inventory, orders, shipments and receipts over a versioned REST API with per-client keys and scopes.
- Out
- Signed webhooks for order, shipment, receipt and inventory events, with retries and a delivery log.
How the pipeline behaves
Held, not guessed.
An order with a SKU the warehouse does not know is held with the reason shown. A variant with no SKU in the store is listed separately as work for the client. A shipping method with no mapping is held only if the client asked for that. Nothing ships on a guess.
Who connects what
Clients connect their own channels.
From the portal, a client connects its Shopify or Walmart store, maps items and shipping methods, sees every order that came in and every update that went back, and retries or rejects a held request itself. The office sees the same page across every client. Details for app reviewers are on ShipFlow for Shopify; developers start at the API documentation.
Something else in your stack?
Tell us what needs to talk to the warehouse and we will show you the pipeline on a walkthrough.