Connect Warehance 3PL to Pipe17

The Warehance 3PL connector links the app to Warehance, a warehouse management system, so your Warehance warehouse can fulfill orders from the app. The app sends shipping requests, products, arrivals, and returns to Warehance and brings back fulfillments, inventory, receipts, and returns. The connector has limited availability.

With this connector, you can:

  • Pull Warehance warehouses into the app as locations.
  • Push shipping requests to Warehance, and sync cancellations in both directions.
  • Pull fulfillments with tracking numbers and carriers from Warehance.
  • Pull on-hand and available inventory for each Warehance warehouse.
  • Push products, arrivals, and returns to Warehance.
  • Pull receipts and returns from Warehance.

Setup

Before you begin, you need:

  • A Warehance account with access to Settings › API Keys.
  • Your Warehance client ID, if you use an organization-level API key.
  1. Sign in to Warehance and go to Settings › API Keys.
  2. Generate an API key and copy it right away. Warehance shows the key only once.
  3. In the app, go to Integrations and click Add integration.
  4. Select Warehance 3PL.
Connect Warehance 3PL pop-up
  1. Paste the key into API Key.
  2. Leave API URL blank to use the standard Warehance API. Set it only to connect to a non-production Warehance environment.
  3. If your API key is organization-level, enter your client in Warehance Client Id. The app attaches products and new stores to this client. Leave it blank for a client-scoped key.
  4. Click Connect.
  5. Go to the Settings tab, turn on the flows you need, and click Save.

Settings

Setting Description Options/Default
Pull locations from Warehance Pulls Warehance warehouses into the app as locations every 5 minutes. Order Routing and Inventory need locations. On/Off. Default: On
Push shipping requests to Warehance Sends orders to Warehance for fulfillment every 5 minutes. Each request needs a Warehance store from the Warehance stores to create setting; a request without one fails. On/Off. Default: Off
Process only shipping requests for specific external order IDs Limits the push to shipping requests with these external order IDs. Use it for testing and leave it empty in production. Optional
Push shipping request cancellations to Warehance Cancels the Warehance order when the order is canceled in the app. If Warehance already fulfilled it, the shipping request is marked rejected and an exception is raised. On/Off. Default: On
Pull order cancellations from Warehance Cancels the shipping request in the app when the order, or all of its lines, is canceled in Warehance. On/Off. Default: Off
Shipment canceled action Status a shipping request gets when its Warehance order is canceled. Canceled + Restock releases committed stock; Canceled keeps it committed. Canceled, Canceled + Restock. Default: Canceled + Restock
Pull fulfillments from Warehance Pulls shipments, with tracking numbers, carriers, and shipped status, as fulfillments every 5 minutes. On/Off. Default: Off
Pull fulfillments updated since Where the first fulfillments pull starts. Empty starts from when the integration was created. Optional
Pull inventory from Warehance Pulls on-hand and available quantities for each Warehance warehouse every 5 minutes. On/Off. Default: Off
Process only inventory for specific SKUs Limits the inventory sync to these SKUs. Use it for testing and leave it empty in production. Optional
Force inventory resync Pulls every item on the next sync, then turns itself off. A full resync can hit Warehance rate limits on a large catalog. On/Off. Default: Off
Include bundle products in inventory sync Turn on only if bundles are defined in Warehance. Leave off when bundles are defined in the app; the app calculates bundle stock from its components. On/Off. Default: Off
Push products to Warehance Creates and updates Warehance products from your catalog so SKUs exist before shipping requests arrive. Parent and bundle products are skipped. On/Off. Default: Off
Process only Products with specific SKUs Limits the product push to these SKUs. Use it for testing and leave it empty in production. Optional
Warehance stores to create One row per store, in the format externalId:name, for example shopify:My Shopify Store. The app creates each store in Warehance, or reuses one with the same name, and adds its ID to the row. Optional
Push arrivals to Warehance Sends arrivals (advance ship notices) to Warehance as inbound shipments. The SKUs must already exist in Warehance, or Push products to Warehance must be on. On/Off. Default: Off
Pull receipts from Warehance Pulls received quantities from Warehance inbound shipments as receipts, once an hour. On/Off. Default: Off
Pull returns from Warehance Pulls returns, with tracking, received and rejected quantities, and return reasons, every 5 minutes. On/Off. Default: Off
Pull returns updated since Where the first returns pull starts. Empty starts from when the integration was created. Optional
Push returns to Warehance Creates Warehance returns from returns in the app. Warehance requires a return reason on every line. On/Off. Default: Off
Return label paid by Who pays for the return label on returns sent to Warehance. Choose Customer; Merchant isn’t supported yet and makes every return push fail. Merchant, Customer. Default: Customer

Flows

Flow Direction Notes
Locations Warehance → the app Every 5 minutes.
Shipping requests The app → Warehance Every 5 minutes. Needs a Warehance store.
Cancellations Bidirectional Controlled by the two cancellation settings.
Fulfillments Warehance → the app Every 5 minutes. You can re-pull a 1–48 hour window with an integration action.
Inventory Warehance → the app Every 5 minutes. You can pull stock for specific SKUs with an integration action.
Products The app → Warehance Every 5 minutes.
Arrivals The app → Warehance Every 5 minutes.
Receipts Warehance → the app Once an hour.
Returns Bidirectional Every 5 minutes. You can re-pull a 1–48 hour window with an integration action.

Troubleshooting

  • Shipping requests fail to reach Warehance
    Each request needs a Warehance store. Add your store in Warehance stores to create, check that the store mapping uses it, and then retry the shipping requests.
  • Products or stores show up under the wrong brand in Warehance
    Your API key is organization-level. Enter the correct client in Warehance Client Id on the Connection Details tab.
  • Every return push to Warehance fails
    Check Return label paid by. Merchant isn’t supported yet, so set it to Customer.
  • An arrival is rejected by Warehance
    The SKUs on the arrival don’t exist in Warehance yet. Turn on Push products to Warehance, or create the products in Warehance, and then retry.
  • Fulfillments or returns from a past period are missing
    Run the fulfillments or returns integration action for that time window. Pull fulfillments from Warehance or the returns flow must be on.

Need Help?

If you need additional assistance:

  • Use Ask Pippen, our AI agent, located at the top of the platform page.
  • Submit a support request with as much relevant detail as possible. Learn how to submit a request.

We’re here to help you succeed with your operations.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.

Have more questions?
Submit a request
Share it, if you like it.