iPaaS.com companies, company addresses, company hierarchy, and company users write out to BigCommerce B2B Edition. An iPaaS.com Company is written as a B2B company carrying its identity and B2B attributes; its addresses and its parent/subsidiary hierarchy are written alongside it. The individual buyers who belong to a company — Customer records flagged for B2B — are written as company users, and the company each user belongs to and its B2B role are resolved from the customer's primary company relationship. Transfers run automatically from subscribed iPaaS.com triggers or on demand from the iPaaS.com Manual Sync page.

This article is the field-level companion to BigCommerce B2B Edition Support, which covers the higher-level picture — what B2B Edition is, how to turn it on, and how automatic transfer is set up. B2B handling is off by default and only applies when B2B support is enabled on the subscription. Capturing BigCommerce companies and company users into iPaaS.com is covered by the companion BigCommerce to iPaaS.com B2B Company and Customer Mapping Documentation. Standard (non-B2B) customers are handled by a separate set of collections — see the Related Documents footer. Only one of the standard (B2C) or B2B mappings should apply to any given customer.

This article documents the following mapping collections and the iPaaS.com data type each one operates on. Every collection here transfers iPaaS.com to BigCommerce.

In BigCommerce B2B Edition, a company relates to other companies as departments or subsidiaries, and to its users. In iPaaS.com those ties are modeled as relationships: company-to-company links form the hierarchy (written outbound through the Parent Company Relationship child collections), and company-to-user links connect a company to its buyers. The company-to-user tie is a relationship between a Company and a Customer — not the Employee data type.

Manual Sync IDs differ by collection because each collection acts on a different record. Addresses and relationships transferred as part of a company or a customer have no independent Manual Sync entry point; sync the parent and its children transfer together.

After a successful transfer, iPaaS.com records the BigCommerce identifier as the external ID on the iPaaS.com record:

The external-ID record is the primary match that routes later transfers of the same record to an update rather than creating a duplicate.

Outbound record delete is not supported for these collections. Deleting a company, address, or company user in iPaaS.com does not propagate a record deletion to BigCommerce; remove records manually in each system as needed.

Company hierarchy deletes are handled separately and are gated by the Allow iPaaS.com to delete company hierarchy subscription setting. When the setting is off, the integration adds and updates hierarchy links but never removes existing ones. Turn the setting on only when you intend to let iPaaS.com delete company hierarchy relationships.

BigCommerce does not expose custom fields for the company, company address, or customer data types. The integration reads several iPaaS.com custom fields outbound to carry B2B-specific values and to route records; none require manual creation for the default templates, and the ones that route records add no mapped data.

Values read from the iPaaS.com Company and its relationships:

Values read from the iPaaS.com Customer to identify and route a B2B user:

All collections in this article ship Enabled. Trigger events:

Whether a given trigger drives an Add or an Update depends on whether the record is already linked to BigCommerce by an external ID. Automatic transfers do not run until the corresponding triggers are configured — see Setup Requirements.

Several collections operate on the same underlying records. Review their filters and Add/Update settings before enabling them, and decide which collection is the source of truth for each record.

The integration decides whether an outgoing B2B record is new or one BigCommerce 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. The selectable methods are:

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. A company without a name, or a company user without an email, cannot be matched reliably.

The Company and Customer collections drive their related records through child collections that transfer as part of the parent:

The company-to-company hierarchy (parent/subsidiary) is written through the Parent Company Relationship child collections. The company each user belongs to and its B2B role are resolved from the customer's primary company relationship during the customer write.

Automatic transfers do not run until the corresponding triggers are configured. Enable the iPaaS.com company and customer triggers (created and updated) under Outbound Data Flows in the subscription configuration. See the BigCommerce Installation Instructions for the step-by-step screens.

Company and its children:

Company user and its address:

Each collection below lists its Mapping Filter (when the collection has one), the iPaaS.com data type it operates on, and its field mapping table. Source and destination field names are shown as they appear in each system.

iPaaS.com data type: Company

Writes an iPaaS.com Company to BigCommerce B2B Edition, creating the company when it does not yet exist. The company write resolves the primary billing address, the administrator contact (from the company's B2B Admin relationship), and the customer group as part of a single write.

Mapping Filter

Filter Description. The filter processes a company only when its B2B Company Status custom field is present and set to one of PENDING, APPROVED, or REJECTED. Companies without a recognized status are skipped. These are the recognized BigCommerce B2B company statuses rather than environment-specific values, so no placeholder substitution is required.

CompanyStatus formula:

State formula:

Country formula:

Administrator formula (the same shape is used for first name, last name, email, and phone — only the custom-field name differs):

CustomerGroupId formula:

Placeholder value — replace during implementation: the "US" country default assumes a US-centric customer base — adjust it if your companies are primarily elsewhere. The customer-group mapping depends on Independent Company Behavior being enabled in BigCommerce; confirm it is enabled before relying on the group assignment.

iPaaS.com data type: Company

Writes changes to an existing iPaaS.com Company to BigCommerce B2B Edition. It shares the same filter as the Add collection and maps a subset of the same fields; it does not remap the administrator contact.

Mapping Filter

Filter Description. Same as the Add collection — a company is processed only when its B2B Company Status custom field is PENDING, APPROVED, or REJECTED; other companies are skipped. No placeholder substitution is required.

Placeholder value — replace during implementation: the B2BPaymentMethods static value cheque,true|bigcommerce_store_credit,false is an example pairing. Replace it with your store's actual BigCommerce payment-method codes and enabled states (format code,enabled|code,enabled) before enabling this collection. Payment-method codes that do not exist in your BigCommerce store are not applied.

iPaaS.com data type: Company Address

These are child collections of the company transfer. Each address is written to BigCommerce and linked to its parent company; there is no independent sync. Neither collection has a mapping filter. The Add and Update field tables are identical.

Placeholder value — replace during implementation: the "US" country default assumes a US-centric customer base — adjust the country formulas if your companies are primarily elsewhere.

iPaaS.com data type: Company Relationship

These are child collections of the company transfer. They write the company's parent-company hierarchy link — nesting a company under its parent (department/subsidiary) in BigCommerce. Each collection maps a single field. The Add and Update collections are identical.

Mapping Filter

Filter Description. The filter processes a relationship only when its Type is parent and the related parent company both exists in iPaaS.com and is linked to its BigCommerce company by an external ID. Non-parent relationships are skipped (return false). When a parent relationship is present but the parent company is missing or unlinked, the transfer stops and raises the error "The parent company either does not exist in iPaaS or is not correctly linked to the corresponding BigCommerce company, as its external ID could not be found in iPaaS." — transfer the parent company first so it exists in iPaaS.com and is linked to BigCommerce. This filter references data relationships rather than an environment-specific value, so no placeholder substitution is required.

iPaaS.com data type: Customer

Writes an iPaaS.com Customer (a B2B user) to BigCommerce B2B Edition as a company user, creating the user when it does not yet exist and updating it when it does. The company the user belongs to and the user's B2B role are resolved from the customer's primary company relationship.

Mapping Filter

Filter Description. The filter reads two iPaaS.com custom fields. A customer is processed only when its B2B_SendToB2B field is y or true and its B2B_Deleted field is null or false. A customer not flagged for the B2B path is skipped (return false) and handled by the standard Customer collection; a customer flagged for B2B but marked deleted is also skipped. The filter references custom-field names rather than an environment-specific value, so no placeholder substitution is required.

B2B_CompanyId formula:

B2B_Role formula:

B2B_SendToB2B and B2B_UserIdFromB2B formulas (each passes through its custom field, returning null when empty):

iPaaS.com data type: Customer Address

Writes an iPaaS.com Customer Address to BigCommerce for the B2B user. This is a child collection of BC B2B Customer FROM iPaaS.com and transfers as part of the customer; it is not synced on its own.

Mapping Filter

Filter Description. An address is written only when both the Address1 street line and the Region are present. Addresses missing either value are skipped. This filter contains no environment-specific value, so no placeholder substitution is required.

Id formula:

Placeholder value — replace during implementation: the "000" phone fallback is a filler value used when the customer has no phone number. Replace it, or remove the fallback, if your business needs a real phone value on BigCommerce addresses. The "US" country default likewise assumes a US-centric customer base — adjust it if your customers are primarily elsewhere.