Getting started with Brandboom

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 Brandboom 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 (Brandboom) and it will lead you to it's settings and configuration page. 

Go to the Connection page.

Here you will pick Brandboom environment (production or sandbox), 

Before you are able to connect Pipe17 to Brandboom, you will need to perform these steps in your Brandboom account:

• Get the API Secret Key: Request API Keys and authorization from Brandboom Support
• Get the Showroom name or id: Login to your Brandboom account to find this. You can find this by clicking Account > Profile

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.

Pull orders from Brandboom:

This will pull your Brandboom orders into Pipe17 to be routed if required. 

	This feature will filter for ingest orders with a creation date prior to the date you specify. By default, if this feature is empty, it will use the date the integration was created. This can be useful if you are testing in Pipe17 or only want to ingest orders from a specific date, such as a go-live. Please note that you can set a date in the past, please contact the Pipe17 team before doing so.
	Pull orders that match selected criteria, this will help you avoid pulling orders with unwanted brandboom status. Usually you will only want to pull orders marked as completed and export ready, but you can also choose to pull all orders except the open ones.
	Orders coming from Brandboom have a '_' at the SKU level. This is usually not a problem, but with this feature we can remove the '_' if necessary.
	This feature will mark orders in Brandboom as exported when they are imported into Pipe17.
	Sometimes you may want to send updates to orders that have already been sent to fulfilment. For example, to cancel an order or add new line items. This feature allows you to do this. Note that orders that have already been fulfilled cannot be updated.
	By default Pipe17 will perform order state transitions according to the configuration applied to the Automation Engine, Order Routing and other components. However, if you want Pipe17 orders to follow order statuses defined in Brandboom and control transitions from Brandboom, enable this setting and refer to Order Mapping to configure order status mapping.
	This feature allows you to select which order Pipe17 will record based on the order ID. This is very useful when testing to avoid pulling multiple orders.

Fulfillment settings

We are able to push Fulfillments to Brandboom; settings will be differentiated accordingly.

Product Settings

We are able to push or pull from Brandboom; settings will be differentiated accordingly.

	Brandboom product catalog is organized by price tiers. While pulling products into Pipe17, it is required to specify price tier name defined in Brandboom. Without a correct configuration product syncs won't work properly.
	When there are more than one price tier it will be needed to map the price tiers from Brandboom to the price names in Pipe17. Add price tiers in the format 'tierName:priceName' i.e. Brandboom price tier name and Pipe17 price name separated by colon.
	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 Product Resync after making changes to this setting.
	This feature will let you update the whole Product Catalog. Depending on the available data, a full resync may take significant time to complete. This may not be the best option if you wish to resync a specific Product or a few, you use the 'Sync' button at the product page or the "Sync" option in the Products list page.

Inventory Settings

We are able to push to Shopify or pull from Shopify; settings will be differentiated accordingly.

	By default, Inventory totals from all active Locations are pushed. Specify a Location to push inventory from. If a specific location is set, only the inventory from that location is pushed.
	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 an Inventory Resync after making changes to this setting.
	Opposite of previous feature, this avoid syncing inventory for specific SKUs. This is mostly used while testing.
	By default Pipe17 will not update future available quantities in Brandboom inventory. Enable this switch to pass future available quantities along with available quantities to Brandboom.
	Same concept to the Force product resync, it will trigger a complete sync of all inventory records.

Location Mapping

Brandboom, and Pipe17 use Locations to track inventory. How these settings are implemented can vary across connectors. Once you have setup your initial settings, we would highly suggest checking out our guide on Getting Started with Locations. 

The end result when pushing fulfillments to Brandboom should look something like this:

Custom Mapping

Custom Mapping is supported with the Brandboom Integration on Pipe17. Mapping is supported for orders, 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.