Connect Ware2Go to Pipe17

Ware2Go combines a Warehouse Management System (WMS), Order Management System (OMS), and Transportation Management System (TMS) into one platform for fulfillment management. Pipe17 supports the following order flows for the Ware2Go integration: 

• Push product catalog information to Ware2Go
• Push shipping requests to Ware2Go
• Pull inventory changes from Ware2Go
• Pull fulfillments from Ware2Go
• Push arrivals (inbounds) to Ware2Go
• Pull receipts from Ware2Go
• Pull locations from Ware2Go

In this Article

• Requirements
• Connecting Ware2Go
• Order Flows
• Integration Specific Settings

Requirements

You will need administrator credentials from your Ware2Go account in order to access the API Users menu. To begin, ensure that you are signed into your Ware2Go AccountVu portal, and open this link in a new tab. This will direct you to the API Users menu in your AccountVu portal. 

1. Click the New API User button underneath the All Filters button
2. Assign a name to the new API user (required) and assign the Account Owner role
3. After clicking Submit, return back to the main API Users wizard. 
4. Your new API User should be listed in the table. Click the new user Name. This will open a new screen with additional details.
5. From here, check the box for Show Token and copy the API Secret. Keep this in a safe yet accessible place, as it will be needed in Pipe17 

Connecting Ware2Go

1. Click on Integrations > Add Integration > Search for Ware2Go > Add
2. Click again on the Integrations tab on the left, Ware2Go should now be listed as an option. Click on the Ware2Go icon
3. In the Connection tab, select your Ware2Go environment (Sandbox, or Production)
4. Enter the API name used when configuring the new user in your AccountVu portal
5. Enter the API Secret you saved earlier
6. Enter your Merchant ID. This can be provided by your Ware2Go account manager
7. Click Save

Congrats! Your Ware2Go account is now connected to Pipe17. Before we begin pulling orders, you must configure your order flows accordingly. We'll dive into that next!

Order Flows

Pipe17 supports the following orders flows for Ware2Go

• Push product catalog information to Ware2Go
  • Turning on this order flow will enable Pipe17 to push your product catalog (from your sales channel) into Ware2Go
• Push shipping request to Ware2Go
  • Turning on this order flow will enable Pipe17 to push shipping requests to Ware2Go (per order)
• Pull inventory from Ware2Go
  • Turning on this order flow will enable Pipe17 to pull inventory quantities from Ware2Go for each SKU
• Pull fulfillments from Ware2Go
  • Turning on this order flow will enable Pipe17 to pull fulfillments from Ware2Go, which can then be passed along to your sales channel or other connections (if enabled)
• Push arrivals to Ware2Go
  • Turning on this flow will enable Pipe17 to push arrivals (inbounds) created in Pipe17 to Ware2Go
• Pull receipts from Ware2Go
  • Turning on this flow will enable Pipe17 to pull receipts from Ware2Go, which can then be pushed to other connections (if enabled)
• Pull locations from Ware2Go
  • Turning on this flow will enable Pipe17 to pull locations from Ware2Go which will then be viewable in your Inventory > Locations tab. 

Integration Specific Settings

Underneath your order flow toggles, you will see additional fields for Shipping Requests, Products, Inventory, and Arrivals. 

Here is the full settings page:

Shipping Requests

• • Process only shipping requests with specific order IDs: This will tell Pipe17 to only import orders with specific order IDs, which can be used for testing. 
  • Force Ware2Go managed routing: When enabled, this delegates the order routing to Ware2go, i.e. all orders are routed to a single fixed location called "Ware2go managed routing". Ware2go internally find the optimal location to route from. Typically, this switch is enabled for all merchants.
  • Cancel shipping request in Ware2Go when cancelled in Pipe17: When enabled, if a shipping request is cancelled in Pipe17 by an user or an automated activity, Pipe17 will do its best to send a shipment cancellation request to Ware2Go.

Fulfillments

• • When shipping request in Ware2Go is marked fulfilled, report fulfilled lines as recorded in Pipe17: When enabled, Pipe17 will skip matching fulfilled line items reported by Ware2Go in the package document if the order suggests that it is fully shipped. The logic is only applied when the order has one and only one package. If the order has multiple packages, Pipe17 reverts back to matching line item requested to line items fulfilled. Here is how it work?
    • Normally when Pipe17 pulls a package for an order from Ware2Go, it tries to match the lines item SKUs in the package to the line item SKUs requested to be shipped. It tries to resolve any SKU Mapping defined in Pipe17, or any aliasing or Kit-To-Order reported by Ware2Go.
    • When this flag is enabled, Pipe17 will first check the status of the order and if the status indicates its fully shipped, Pipe17 will count the number of packages. If the order has only one package, Pipe17 will assume all requested line item SKUs are shipped. It will skip the logic of matching the line items, instead report all line items fulfilled along with tracking information to the order source channel. As a result the shipping request as well as the order is marked fulfilled in Pipe17 and once Pipe17 reports the fulfillment information back to the source channel, the order will be marked fulfilled in the order source channel as well. 
    • When the flag is enabled, and more than one package pulled for the order, OR when the flag is disabled (default), Pipe17 will try to match the line item SKUs as explained above.

Products 

• • Process only products with specific SKUs: This will tell Pipe17 to only pull in certain products where the SKU is added to this field
  • Force product catalog sync: Toggling this ON will force Pipe17 to pull in new/updated products

Inventory

• • Process inventory information only for products with specific SKUs: This will tell Pipe17 to pull inventory quantities for only the SKUs added to this field
  • Force Inventory Sync: Toggling this ON will force Pipe17 to pull in updated inventory from Ware2Go. This happens automatically, but this toggle will trigger this on demand

Arrivals

• • Process only arrivals with specific order IDs: This will tell Pipe17 to only process Arrivals (inbounds) with the order IDs added to this field