Sign In
Book a Demo

Warehance Integration for Fulfillment and Returns

Warehance is a warehouse management system. The Warehance integration sends orders, products, inbound shipments, and returns from Pipe17 to its warehouses, and brings tracking, stock, receipts, and return receipts back to Pipe17 and your channels.
Book a demo
Warehance logo tile for the Pipe17 Warehance integration

The Solution for Warehance Integration & Warehouse Operations

Warehance Runs the Warehouse. Pipe17 Decides Which Orders Go There.

Bolting a Warehance warehouse onto an existing stack takes an iPaaS to move orders, stock, and returns, plus a legacy OMS to decide what the warehouse gets. Pipe17’s Order Operations Platform handles both jobs. Its Warehance connector makes each warehouse a Pipe17 location routed alongside your other warehouses and 3PLs, on one stock count.
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) ❌ ❌ ✅

Future-Ready Brands and Fulfillment Providers Run on Pipe17

Pipe17 Sends Warehance the Orders. Warehance Sends Back Tracking, Stock, and Receipts.

Box with checkmark overlaid, representing a verified, completed or fulfilled order

Orders Arrive Under a Method the Warehouse Recognizes

Pipe17 lists your Warehance shipping methods. Pair the methods your channels send with them once, and every order arrives under a name Warehance already knows.

Two-tone icon of a computer dashboard with charts controls and gears symbolizing visibility and system control.

Sell Only What Warehance Has Free

Pipe17 reads on hand, available, and allocated per warehouse and counts only the available figure as sellable. Units promised to open orders stay off sale.

Two-tone icon of a multi-step process symbolizing completed purchase order fulfillment

Carry Returns to the Warehouse and Back

Pipe17 creates each approved return in Warehance for the warehouse to receive against, and the units received or rejected post back to the same return.

Automated Warehance Data Flows

Pipe17 pushes orders, cancellations, products, inbound shipments, and returns into Warehance, then pulls the warehouse’s answers back, continuously. Warehance stays the record for what is on the shelf.
  • Push Orders to Warehance. Each order routed to a Warehance warehouse is created there under the store that matches its sales channel, with the ship-to address, order date, required ship date, shipping method name, and lines carrying SKU and quantity. Pipe17 checks Warehance for a duplicate before creating one.
  • Push Cancellations to Warehance. Canceling an order in Pipe17 cancels the Warehance order behind each of its shipments. If Warehance has already shipped one, Pipe17 marks that cancellation rejected and opens a late cancel exception instead.
  • Push Products to Warehance. Pipe17 creates and updates Warehance products from your catalog, with name, description, barcode, price, weight, and dimensions, so SKUs exist before orders reference them. Only physical SKUs go across. A bundle reaches the warehouse as its components.
  • Push Inbound Shipments to Warehance. Pipe17 announces each inbound shipment headed for a Warehance warehouse, with its reference number, expected date, tracking number, and the SKUs and quantities on the way.
  • Push Returns to Warehance. A return approved in Pipe17, whether it began in your storefront or in a returns app, is created in Warehance with the customer email, items, quantities, and reasons, ready for the warehouse to receive.
  • Pull Warehouses from Warehance as Locations. Every Warehance warehouse becomes a Pipe17 location carrying its ship-from address. Routing, inventory, inbound shipments, and returns all point at that location.
  • Pull Fulfillments from Warehance. Each parcel Warehance ships becomes its own Pipe17 fulfillment carrying its tracking number, carrier and service level, ship date, weight, dimensions, and the SKUs and quantities packed inside. Pipe17 posts that tracking back to the order’s sales channel.
  • Pull Inventory from Warehance. Per SKU and warehouse, Pipe17 records on hand, available, and allocated quantities as Warehance reports them, and your channels sell from the available figure. You can narrow the pull to a SKU list, and, by default, bundles take their stock from their components.
  • Pull Receipts from Warehance. Each time the warehouse books units in against an announced inbound shipment, Pipe17 records a receipt on that shipment with quantities per SKU. A delivery received in several rounds shows one receipt per round.
  • Pull Returns and Cancellations from Warehance. Returns created in Warehance come into Pipe17 with tracking, carrier, received and rejected quantities per item, reasons, and label cost, and a return Pipe17 sent is updated rather than duplicated. When someone cancels an order in Warehance, Pipe17 cancels the matching shipping request (the Pipe17 record that asked the warehouse to ship) and, by default, releases its stock.

Live on Warehance With an API Key, Not a Code Project

Pipe17 owns and maintains the Warehance connector, listed as Warehance 3PL, against the Warehance API. Generate an API key in Warehance, paste it into Pipe17, and turn on the flows you run. Nothing to code.

Send Warehance Your Orders and Returns. Keep One Record of Both.

Book a demo to watch an order route to a Warehance warehouse and its parcel tracking land back on the order, without anyone re-keying either.
Book a demo
Warehance horizontal logo

is better with

Pipe17 horizontal svg logo black

Warehance Integration FAQs

The Warehance integration, built and managed by Pipe17, turns each Warehance warehouse into a location on the Order Operations Platform. Pipe17 sends it orders, products, inbound shipments, and returns, and brings back per-parcel tracking, stock, receipts, return receipts, and cancellations. An order from a storefront such as Shopify or a marketplace such as Amazon routes to one of those locations, and its tracking goes back to that channel.

Yes, the Warehance integration works for a 3PL that runs Warehance for its clients and for a brand on its own Warehance account. A 3PL sets up one integration per client, with a key scoped to that client, and each client's channels route into its own stores at the 3PL's warehouses. A brand connects once and routes orders to its Warehance warehouses alongside any other warehouse or 3PL on the Pipe17 Network.

An order from Shopify, Amazon, or TikTok Shop reaches Warehance when order routing in Pipe17 assigns it to a Warehance warehouse. Pipe17 creates the order in Warehance under the store set up for that channel, with the shipping method name from the order or the Warehance method you paired it with. Once the warehouse ships, each parcel's tracking posts to the channel that took the order.

Your channels sell from Warehance's available figure. Pipe17 pulls on hand, available, and allocated quantities for each SKU at each Warehance warehouse and treats available as the sellable count, next to stock at your other warehouses and 3PLs. Warehance is the system of record for stock. Bundle stock comes from the components unless you choose otherwise, and the pull can be limited to a SKU list.

Yes, as long as the warehouse has not shipped it, canceling the order in Pipe17 cancels the Warehance order behind each shipment. An order Warehance has already fulfilled cannot be canceled, and Pipe17 marks that cancellation rejected and raises a late cancel exception. When someone cancels an order in Warehance, Pipe17 cancels the matching shipping request and, by default, releases its committed stock.

Returns move both ways between Pipe17 and Warehance. A return approved in Pipe17, whether from your storefront, Loop, or Happy Returns, is created in Warehance ahead of the warehouse receiving it, and Pipe17 records the received and rejected units on that return. A return that starts in Warehance comes into Pipe17 with tracking, quantities, reasons, and label cost, and appears in returns management like any other.

Warehance setup needs an API key and a few Pipe17 settings. Generate the key in Warehance under Settings > API Keys and paste it into Pipe17, with your Warehance client ID if the key covers your whole organization. Pipe17 pulls your warehouses as locations. Name a Warehance store per sales channel, pair the shipping methods your channels send with Warehance ones, map SKUs where needed, and enable the flows you use.

Test the Warehance integration on a narrow slice first by restricting the order push to a few order IDs and the product and inventory syncs to chosen SKUs. Turn the flows on in sequence: warehouses first, then products, inventory, orders, and fulfillments, then cancellations, inbound shipments, and returns. Once a trial order ships and its tracking comes back, remove the filters and open every flow.