BrightPearl Mapping 

When using BrightPearl on BigCommerce, BrightPearl will map to the method name within an order. This works well in most scenarios, as BrightPearl can dynamically see each method name setup in ShipperHQ when we pass that info over into an order on BigCommerce. 

Here’s how the flow works from ShipperHQ to BigCommerce:

1. BigCommerce sends a request with the cart information to ShipperHQ via the ShipperHQ API.

2. ShipperHQ replies to BigCommerce with the method name

3. BigCommerce receives the response from ShipperHQ.

4. When the order is placed, the method name, delivery date and time (if present), duties and taxes (if present), is all placed into one line "Method"  

Here's how the flow works from BigCommerce to BrightPearl:

1. BrightPearl sends an API request to the BigCommerce Order API. In this case, order 105.
2. BigCommerce responds to BrightPearl with the "shipping_method" value.
3. BrightPearl then uses the value within the "shipping_method" name as the mapping value in their system
   
   
   

Potential Issues with Mapping

Using Duties and Taxes, or Delivery Date and Time, can potentially break the method mapping in BrightPearls system. 

The reason that happens is because BrightPearl depends on the the "shipping_method" name to only contain the carrier service, ie FedEx (Ground) instead of FedEx (Ground Delivers: Tue, Sep 23).

Resolution

If this issue occurs, the best course of action is to reach out directly to BrightPearl for further assistance. They can advise on looking into partial method name mapping solutions or looking into grabbing the Method Code instead of the Method Name from the BigCommerce Order API. 

Relevant Articles: 

Use ShipperHQ with Order Management or Fulfillment Software

What Data Does BigCommerce Store from ShipperHQ?