Background
BC customers (along with their addresses) can be transferred bidirectionally between iPaaS.com and BC. We also have extensive handling for Customer Companies moving bidirectionally for BC B2B Edition. Customer Companies can have relationships with other Customer Companies (i.e. departments or subsidiaries) as well as Customers (i.e. buyers).
Note: relationships between B2B users and their employees is done via a relationship between a Customer Company and a Customer in iPaaS.com and not with the Employee data type.
Matching
Customer records are matched on email addresses (bidirectionally) and assumed to be the same record if that matches.
Duplicate address prevention
To prevent duplicate addresses from being added to BigCommerce from iPaaS.com, add a static mapping to a Destination field “PreventDuplicate” in the Customer Address From mapping collection. If a static value of Y, y, or true are found, new addresses will search BigCommerce addresses for an exact match for every field included in the request (excluding custom fields). If there is an exact match, the address is not added to BigCommerce, but will also not have an external ID added.
To prevent duplicate addresses from being added to iPaaS.com from BigCommerce, add a static mapping to a Destination field “PreventDuplicate” in the Customer Address To mapping collection. If a static value of Y, y, or true are found, new addresses will search iPaaS.com addresses on the customer record for an exact match for every field included in the request (excluding custom fields). If there is an exact match, the address is not added to iPaaS.com, but will also not have an external ID added.
These only apply to full customer requests with addresses as a mapping subcollection; address-only transfers do not currently honor the PreventDuplicate values.
BigCommerce Custom Fields
Not supported for this data type.
iPaaS.com Custom Fields
None created by default for this data type.
Customers & Customer Companies TO iPaaS.com
Notes:
The names of the following sections are the mapping collection names in iPaaS.com.
Some mapping collections have mappings that need to be updated. Those are denoted by a *
Some mapping collections have translations that should be reviewed. Those are denoted by a ⁺
Some mapping collections have mapping or error filters that need to be updated. Those are denoted by a º
Webhooks (External)
In order to enable Customer data to flow TO iPaaS.com, the following external webhooks need to be enabled:
B2B does not support webhook notifications to iPaaS.com and relies on standard BigCommerce webhooks for changes to customers (company users) and placed orders. The original BigCommerce integration store/customer/{action} and store/order/{action} webhooks must be used for instant notification of these record types shared between B2C and B2B, however scheduled polling options are available for all B2B supported features.
B2B Company Polling
B2B Companies can be polled and sent to iPaaS.com Companies if updated since the last poll time using the store/company/poll webhook. To configure polling, add a polling event at Dashboard / Integration Monitoring / Events. This webhook / poll event must use the filter “B2B_Company”.
Add New Event Fields
Field | Value |
Name | BigCommerce B2B Company Poll |
Event Type | Webhook (Poll Request) |
Dexription | BigCommerce B2B Company Poll |
Event Rules Values
Name | Description | Expression |
Interval | Every 1 hour | 0 0 0/1 1/1 * ? * |
SystemId | Name of the subscription | ID of the subscription |
Scope |
| store/company/poll |
Filter |
| B2B_Company |
B2B User Polling
In most situations, store/customer/created and store/customer/updated webhook subscriptions will be sufficient to initiate a transfer of a B2B Company User to iPaaS Customer as this record type is shared between B2C and B2B, however if desired B2B Company Users may also be polled using the store/customer/poll webhook. To configure polling, add a polling event at Dashboard / Integration Monitoring / Events. This webhook / poll event must use the filter “B2B_User”.
Add New Event Fields
Field | Value |
Name | BigCommerce B2B Company User Poll |
Event Type | Webhook (Poll Request) |
Dexription | BigCommerce B2B Company User Poll |
Event Rules Values
Name | Description | Expression |
Interval | Every 1 hour | 0 0 0/1 1/1 * ? * |
SystemId | Name of the subscription | ID of the subscription |
Scope |
| store/customer/poll |
Filter |
| B2B_User |
Data Mapping
BC Customer Add To IPaaS
Brings new customers in BC over to iPaaS.com
Notes:
This data supports associating a customer with one or more channels in BC.
This mapping collection has the following sub-mapping collections:
BC B2B Customer Relationship Update To IPaaS
BC Customer Update To IPaaS
Updates customers that have changed in BC in iPaaS.com
Notes:
This data supports associating a customer with one or more channels in BC.
This mapping collection has the following sub-mapping collections:
BC Customer Address Update To IPaaS
BC B2B Company Add To IPaaS⁺
Brings new Companies in BC over to iPaaS.com
Notes:
If you are not using BC B2B Edition you can delete this mapping.
This mapping collection has the following sub-mapping collections:
BC B2B Company Address Add To IPaaS
BC B2B Company Relationship Add To IPaaS
BC B2B Company Update To IPaaS⁺
Updates Companies in BC over to iPaaS.com
Notes:
If you are not using BC B2B Edition you can delete this mapping.
This mapping collection has the following sub-mapping collections:
BC B2B Company Address Update To IPaaS
BC B2B Company Relationship Update To IPaaS
BC B2B Customer Add To IPaaS
Transfers B2B customers created in BC over to iPaaS.com.
Notes:
If you are not using BC B2B Edition you can delete this mapping.
B2B customers are mapped to company users in the account
This mapping collection has the following sub-mapping collections:
BC B2B Customer Relationship Add To IPaaS
BC B2B Customer Update To IPaaS
Updates B2B customers updated in BC over to iPaaS.com.
Notes:
If you are not using BC B2B Edition you can delete this mapping.
B2B customers are mapped to company users in the account
This mapping collection has the following sub-mapping collections:
BC B2B Customer Relationship Update To IPaaS
Customers and Customer Companies FROM iPaaS.com
Webhooks (Internal)
In order to enable Customer and Customer Company data to flow FROM iPaaS.com, the following internal webhooks need to be enabled:
customer/created
customer/updated
customer/company/created
customer/company/updated
Data Mapping
BC Customer From IPaaS
Used for creating customers in BC from customers created in iPaaS.com
Notes:
If you are not using BC B2B Edition you can delete this mapping.
This mapping collection has the following sub-mapping collections:
BC Customer Address From IPaaS
BC B2B Company Add From IPaaS
Used for creating companies in BC from Customer Companies created in iPaaS.com
Notes:
If you are not using BC B2B Edition you can delete this mapping.
This mapping collection has the following sub-mapping collections:
B2B Company Address Add From IPaaS
BC B2B Company Update From IPaaS
Used for updating companies in BC from Customer Companies updated in iPaaS.com
Notes:
If you are not using BC B2B Edition you can delete this mapping.
This mapping collection has the following sub-mapping collections:
B2B Company Address Update From IPaaS
BC B2B Customer From IPaaS
Used for creating and updating customers in BC from Customers created anr/or updated in iPaaS.com
Notes:
If you are not using BC B2B Edition you can delete this mapping.
Only one of B2C or B2B mappings should apply to a customer transfer.
BigCommerce B2C will allow duplicate customers to be created