Getting Started with Capacity

Connecting Capacity to Pipe17

Navigate to the Integrations tab in your Pipe17 portal and click on "Add Integration" in the upper right corner.

Find the Capacity Connector and Click on Add without credentials.

Once you have added the integration, it will appear under your main Integration page. You can click the connector (Capacity) and it will lead you to it's settings and configuration page. 

Go to the Connection page, here you will need to define the API URL, whether you will connect to a Sandbox or Production account. 

As a second step, you will need to populate the Client Id and Secret, the API Key and the Client code. These values must be provided by a Capacity admin, you should be able to ask your account representative for these values.

Initial Configuration

Note that the initial configuration will vary depending on your business needs. In this example, we will walk through some common configurations and explain the functions of the settings involved.

Shipping Requests Settings

We are able to push Shipping Requests to Capacity; settings will be differentiated accordingly.

Inventory Settings

We are able to pull inventory from Capacity; settings will be differentiated accordingly.

	Similar to shipping request feature. You can use this setting for testing purposes. Only inventory entities with the specified SKUs will be pulled from Capacity.
	Please use this feature with caution as the updates will be collected for the whole set of inventory items available in Capacity. Depending on the available data, a full resync may take significant time to complete.

Arrivals Settings

We are able to push Arrivals to Capacity; settings will be differentiated accordingly.

Similar to shipping request feature. You can use this setting for testing purposes. Only Arrivals with the specified IDs will be pushed to Capacity.

Location Mapping

Pipe17 and Capacity use the concept of Locations, a correct configuration of locations will not help in order routing and inventory mapping.

This mapping will determine from which location we are going to pull the inventory from Capacity and to which one we are going to deposit it in Pipe17 to send it to other connectors such as sales channels or ERPs.

Once you have setup your initial settings, we would highly suggest checking out our guide on Getting Started with Locations. 

The end result when pulling inventory from Capacity should look something like this:

In this simple example, "CapacityMain" location is going to be the source of truth of the inventory quantities the "Capacity" location will show. If "CapacityMain" has 100 units of a product, "Capacity" will reflect the same.

Custom Mapping

Custom Mapping is supported with the Capacity Integration on Pipe17. Mapping is supported on Shipping requests, fulfillments, locations and inventory. 

Mapping is an advanced configuration that should not be attempted without technical knowledge. We recommend that you contact the Pipe17 team before attempting to map an area.

Testing

Test Data Synchronization

1. Locations
   • You must define which Capacity locations this integration will use. This can be confirmed by your Capacity team. 
   • Map locations accordingly. 
2. Inventory
   • Once the initial products have been configured correctly in Capacity and the selling channel or ERP and the locations mapped, activate the pull inventory. If no filter is applied, all inventory will be pulled.
   • Confirm the correct inventory quantities are reflected in Pipe17.
   • After you have confirmed inventory is ok, you should be able to push inventory. Remember, location mapping will dictate what inventory we push.
3. Shipping request
   *Pipe17 must have orders to test this step.
   • Once Pipe17 has orders, whether from a selling channel or an ERP.
   • You will need to set up the Order routing engine (ORE), in order to understand how to set up this part, please look at this guide. Order Routing.
   • The order routing engine will create a shipping request.
   • Confirm when a shipping request has been created by ORE. You can create a shipping request manually as well.
   • Verify that the shipping request is send correctly based on your configurations.
4. Fulfillments
   • Fulfill the test orders in Capacity.
   • Confirm the fulfillment information is updated in Pipe17.
   • Ensure that shipping confirmations and tracking numbers are pushed back to other integrations.

Use Cases to Consider

• Standard Order Processing: Verify the complete flow from order import to fulfillment update.
• Inventory sync: Ensure inventory quantities match in Pipe17 and Capacity.
• Partial Fulfillment: Test orders that are split into multiple shipments.
• Purchase flow: This is an advanced Pipe17 flow, our connector can support integrating purchase orders usually coming from an ERP. Using Arrivals or ASNs, Pipe17 informs the 3PL that they will receive a certain quantity of items. Once Capacity receives the items, Pipe17 will receive an update.
• Transfer flow: This is an advanced Pipe17 flow, our connector can support integrating transfer orders usually coming from an ERP. With the use of Arrivals or Shipping requests, depending on the desired flow Pipe17 informs the 3PL that they are going to receive or must ship a certain quantity of items. Once Capacity receives/ships the items, Pipe17 will receive an update.