BigCommerce B2B Edition adds business-to-business commerce on top of a standard BigCommerce store: buyers are grouped into companies, companies can be organized into a hierarchy of departments and subsidiaries, individual buyers belong to a company as company users, and buyers can request quotes. When you run B2B Edition, the iPaaS.com integration keeps this B2B data in step with your connected systems alongside the standard store data.

Use this article to understand what the integration synchronizes for B2B Edition, what you need in place first, and how automatic transfer is configured. B2B support is off by default and turns on with a single subscription setting, so a standard (non-B2B) store is unaffected until you enable it.

B2B handling is controlled by two settings on the subscription, both documented in BigCommerce Connections and Settings:

When B2B is enabled, the integration reads and writes B2B data through the B2B Api Url; when it is off, only standard store data is synchronized.

Before B2B support can do anything, you need:

Subscribers or their MiSP should confirm both are in place before expecting B2B records to transfer.

With B2B enabled, the integration synchronizes three kinds of B2B data.

A B2B company transfers as a Company record, carrying the company's core identity — name, email, and phone — together with its B2B attributes such as customer group, assigned catalog, status, and payment-terms configuration. Companies transfer in both directions.

Each company brings its related records with it:

The individual buyers who belong to a company — the company users — transfer as Customer records. The link between a company and its users is modeled in iPaaS.com as a relationship between a Company and a Customer, not through the Employee data type. Each relationship also records the user's B2B role (Super Admin, Admin, Senior Buyer, or Junior Buyer).

To identify a Customer as a B2B user and route it correctly, the integration relies on a B2B_UserId custom field on the iPaaS.com Customer. This custom field carries the BigCommerce B2B user identifier; it is populated on the inbound transfer and read on the outbound transfer so a B2B user round-trips to the same BigCommerce record rather than creating a duplicate. Standard (non-B2B) customers carry no B2B user identifier and are handled by the standard Customer collections instead.

A B2B quote transfers to iPaaS.com as a Transaction of type Quote. The quote header carries the buyer company, totals, tax, shipping, discount, item count, and dates, and drives the transfer of the quote's related records:

The buyer company on a quote is resolved automatically as a prerequisite, so the company is transferred before the quote when it does not yet exist in iPaaS.com.

BigCommerce B2B Edition does not send its own webhook notifications to iPaaS.com. Because of that, automatic B2B transfers are set up differently depending on the record type. All of the setup below is done on the Subscriber Dashboard; see the BigCommerce Installation Instructions for the step-by-step screens.

Companies do not ride any BigCommerce webhook, so they transfer through scheduled polling. Under the subscription's Inbound Data Flows, add a poll event that uses the store/company/poll scope with the filter B2B_Company. Choose a polling interval that suits how often your companies change. Until a company poll event is enabled, no companies transfer automatically — though Manual Sync is always available.

B2B company users are shared with the standard customer path, so in most cases the standard BigCommerce customer events (customer created and customer updated) are enough to transfer a company user — enable those under Inbound Data Flows. If you prefer polling, add a poll event that uses the store/customer/poll scope with the filter B2B_User. Either path works; you do not need both.

To send companies and B2B users from iPaaS.com to BigCommerce, subscribe to the iPaaS.com company and customer triggers under Outbound Data Flows in the subscription configuration.

Deletion of company hierarchy records is gated by the Allow iPaaS.com to delete company hierarchy subscription setting, documented in BigCommerce Connections and Settings. When the setting is off, hierarchy records are never deleted — the integration adds and updates hierarchy links but leaves existing ones in place. Turn the setting on only when you intend to let iPaaS.com remove hierarchy relationships.

The integration decides whether an incoming B2B record is new or an existing record it already knows about, so updates land on the right record instead of creating duplicates:

When a match is found, the record is treated as the same record and the configured collision method for that data type decides the outcome. Review the collision method for the Company and Customer data types so records merge with, or stay separate from, existing records as your workflow expects.

B2B quote writes are not active at this time. B2B quotes transfer to iPaaS.com as documented above, but creating and updating BigCommerce B2B quotes from iPaaS.com is not currently performed. The quote-write mapping collections exist for completeness, so subscribers or their MiSP should validate quote behavior in a staging environment before relying on it in production. See Known Limitations for the current list of behaviors to be aware of.