SynchUP BigCommerce Order Data Pusher Settings

Discover the settings and record matching logic for the SynchUP BigCommerce Order Data Pusher

Record Matching

There are three areas for record matching in the BigCommerce Order Data Pusher; the Order, Customer and Customer Address objects.

Order

There is a single setting pertaining to Order record matching; Multiple Match Behavior - Order. BigCommerce has a property on orders called External Order Id. In lieu of using a custom defined attribute as seen in other External Id mapping locations, SynchUP uses this property.

The following logic is how record matching occurs:

1. If ExternalId on the MCO is not null, SynchUP will use that id and update that record in BigCommerce
   1. If that Id does not exist, that record will result in a failure
2. If ExternalId is null, SynchUP will look to see if the value of the InternalId on the MCO matches the value of External Order Id on an order record in BigCommerce
   1. If a match is found, SynchUP will update that record
   2. If multiple records are found, SynchUP will refer to the Multiple Match Behavior - Order setting to determine how to proceed. Possible options:
      1. Fail Record - The entire record will fail and nothing will be updated
      2. Last Modified - With the subset of records that match, the record within BigCommerce that was updated most recently will be updated
      3. Create New - No records within BigCommerce will be updated. A new record will be created
3. If a match is not found, the next step would be for SynchUP to match on a unique identifier. In BigCommerce the order number is the same as the unique order id. Attempting to match on that would be a redundant step, therefore SynchUP does not have a data matching step for this Data Pusher.
4. If all of the logic above has been performed and no matches have been found, SynchUP will create a new Order record in BigCommerce

Customer

The two settings pertaining to Customer matching is External ID - Customer and Multiple Match Behavior - Customer.

The following logic is how record matching occurs:

1. If ExternalId on the MCO is not null, SynchUP will use that id and update that record in BigCommerce
   1. If that Id does not exist, that record will result in a failure
2. If ExternalId is null and External ID - Customer is filled out, SynchUP will look to see if the value of the InternalId on the MCO matches the value of the attribute name filled out in the setting on a BigCommerce record
   1. If a match is found, SynchUP will update that record
   2. If multiple records are found, SynchUP will refer to the Multiple Match Behavior - Customer setting to determine how to proceed. Possible options:
      1. Fail Record - The entire record will fail and nothing will be updated
      2. Last Modified - With the subset of records that match, the record within BigCommerce that was updated most recently will be updated
      3. Create New - No records within BigCommerce will be updated. A new record will be created
3. If a match is not found, SynchUP will then use the the Email address of the Customer record and do a search in BigCommerce for a record with the same email address
   1. If a match is found, SynchUP will update that record
      1. if the setting External ID - Customer is filled out, SynchUP will update that attribute on that customer with the InternalId of that record
      2. Note: Email in BigCommerce is a unique value. There is not a possibility for multiple matches in this scenario
   2. Note: This step can be skipped by enabling the setting Suppress looking up customer via Email
4. If all of the logic above has been performed and no matches have been found, SynchUP will create a new Customer record in BigCommerce

Customer Address

The two settings pertaining to Customer Address matching is External ID - Address and Multiple Match Behavior - Customer.

The following logic is how record matching occurs:

1. If ExternalId on the MCO for a Customer Address is not null, SynchUP will use that id and update that record in BigCommerce
   1. If that Id does not exist, that record will result in a failure
2. If ExternalId is null and External ID - Address is filled out, SynchUP will look to see if the value of the InternalId on the Customer Address MCO matches the value of the form field name filled out in the setting on a BigCommerce record
   1. If a match is found, SynchUP will update that record
   2. If multiple records are found, SynchUP will refer to the Multiple Match Behavior - Address setting to determine how to proceed. Possible options:
      1. Fail Record - The entire record will fail and nothing will be updated
      2. First Created - Within the subset of records that match, the record that was first created in BigCommerce will be updated
      3. Last Created - Within the subset of records that match, the record that was last created in BigCommerce will be updated
      4. Create New - No records within BigCommerce will be updated. A new record will be created
3. If a match is not found, SynchUP will perform a full-text comparison of all address fields
   1. If a match is found with all fields, SynchUP will not add a new address record
      
      1. if the setting External ID - Address is filled out, SynchUP will update that form field on that address with the InternalId of that record
   2. If multiple matches are found, SynchUP will refer to the Multiple Match Behavior - Address setting to determine how to proceed
4. If all of the logic above has been performed and no matches have been found, SynchUP will create a new Customer Address record in BigCommerce
   
   

Additional Settings

• Suppress refunding orders
  • Type: Boolean
  • Definition: If toggled to true, SynchUP will not attempt to create refunds for orders in BigCommerce even if refund data is present on the MCO
• Default Refund Payment Provider
  
  • Type: String
  • Definition: If a Refund Payment Provider is not mapped on the MCO, SynchUP will use this value as the fallback when creating a new refund.