Getting Started with Shipbob

Connecting Brandboom to Pipe17

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

Find the Shipbob Connector and Click on Add.

The Connection Flow Settings page will be displayed, leave these toggles turned off for now. We will revisit these later in the guide. Just click in the "x".

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

Go to the Connection page, here you will pick Channel Name, we recommend "Pipe17". Once connected, channel name shown here will become the integration name from the ShipBob UI.

Finally, once you have all the information, you can click on Save.

Once the connection has been established, you can start configuring the connector.

Initial Configuration

Please note that the initial configuration may vary between stores. In this example, we will walk through some common setups and explain the functions of the settings involved.

Products Settings

In order to be able to pull inventory from Shipbob, we must turn on product push to Shipbob. Make sure SKUs match in Pipe17 and Shipbob or apply the corresponding mapping. 

This setting is especially useful during the testing stage or if you want to keep only a subset of your Product catalog in Pipe17. You must trigger a specific Product resync or full resync after making changes to this setting.

Please use this feature with caution as the updates will be processed for the whole product catalog available in Pipe17. Depending on the available data, a full resync may take significant time to complete. If you wish to resync a specific Product, navigate to the Product details page in Pipe17 and click on the 'Sync' button at the bottom of the page. For syncing a few Products, go to the Products list page, select the Products by clicking on the checkbox, and click on the 'Touch' button at the top of the Products list page.

Shipping Requests Settings

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

Inventory Settings

We are able to pull inventory from Shipbob; 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 ShipBob.
	ShipBob has the concept of a bundle. If bundle setup will be done directly in ShipBob, then enable this setting to support bundled inventory. If using bundles across multiple 3PLs, our recommendation is to do the bundle setup directly in Pipe17. If setting up bundles directly in Pipe17, then leave this setting OFF to allow Pipe17 logic to determine correct inventory at the bundle level based
	This feature will define to which locations inventory will get allocated.There are 3 options: - Shipbob warehouse locations: inventory will get allocated in the corresponding matching location. - Shipbob managed location only: all inventory in Shipbob will be pulled to that location. - Shipbob manages location & warehouse locations: a combination of both will occur, this option requires an extra configuration, Shipbob location needs to be excluded from totals. Request help from Pipe17 team.
	Please use this feature with caution as the updates will be collected for the whole set of inventory items available in ShipBob. Depending on the available data, a full resync may take significant time to complete.

Arrivals Settings

We are able to push Arrivals to Shipbob; 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 ShipBob.

Location Mapping

Shipbob and Pipe17 use Locations to track inventory. How these settings are implemented can vary depending your needs. As mentioned above, Shipbob can work with 2 types of locations, warehouse locations (individual locations) and Shipbob managed location (generalized location). The first thing to do is to define which one you want to work with, it is possible in some specific use case to work with both, if so it is better to contact the Pipe17 team.

What you will need to do to enable the Shipbob connector is to do a location mapping. This mapping will determine from which location we are going to pull the inventory from Shipbob 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 Shipbob should look something like this:

In this example, Shipbob managed location is being used and the locations of various sales channels and that of the ERP Cin7 have been mapped. This will cause all locations under the Shipbob managed location to maintain the same amount of inventory. 

Custom Mapping

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

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. Products
   • Push products to Shipbob, initially we should only push SKUs that already exist in Shipbob to enable inventory pull.
   • Confirm in “events” if the push was successful. 
2. Locations
   • You must define how you want to set up Shipbob integration, either with managed location or individual warehouses (or both).
   • Map locations accordingly. 
3. Inventory
   • Once the initial products have been pushed and the locations mapped, activate the pull inventory. If no filter is applied, all inventory will be pulled.
   • Confirm the inventory updates are reflected in Pipe17.
4. Shipping request
   • Pipe17 must have orders to route.
   • 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.
5. Fulfillments
   • Fulfill the test order in Shipbob.
   • Confirm the fulfillment information is updated in Pipe17.
   • Ensure that shipping confirmations and tracking numbers are pushed back to other connectors.

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 Shipbob.
• Partial Fulfillment: Test orders that are split into multiple shipments.
• Order Cancellations: Cancel an order in a selling channel and confirm it updates in Shipbob.