BigCommerce's Channel Manager lets one BigCommerce account serve more than one channel: the primary storefront, any additional storefronts, and marketplace channels such as Amazon or eBay, each identified by its own numeric channel_id. When InfiPlex pushes marketplace orders into BigCommerce as a shared order and inventory hub, every order needs the right channel_id attached so it lands, and reports, under the correct BigCommerce channel rather than always defaulting to the primary storefront. A small rule set on the BigCommerce connection controls that tag. This guide documents its syntax. For how the BigCommerce connection itself is set up, start with the InfiPlex BigCommerce integration page.
The Channel Mapping Rule
Where it lives: a JSON array on the BigCommerce connection, the same connection-level rule pattern InfiPlex uses elsewhere. Each rule names an order_source, either a specific source such as Amazon.com or the catch-all ALL_ORDER_SOURCES, together with an action_type and the value that action needs.
| Key | Value | Purpose |
|---|---|---|
order_source |
A specific source (e.g. Amazon.com) or ALL_ORDER_SOURCES |
Which orders this rule applies to |
action_type |
set_bc_channel_id |
Sets the BigCommerce channel_id on the order |
field_value |
A BigCommerce channel_id (integer) | The channel the order is tagged with |
A rule naming a specific order_source overrides the ALL_ORDER_SOURCES default for that source only; every other source still falls back to the default. A working example, mapping every order to channel 1 by default and Amazon orders to channel 2:
[
{
"order_source": "ALL_ORDER_SOURCES",
"action_type": "set_bc_channel_id",
"field_value": 1
},
{
"order_source": "Amazon.com",
"action_type": "set_bc_channel_id",
"field_value": 2
}
]
Read as a sentence: send every order to channel_id 1, the account's primary storefront channel, except orders from Amazon.com, which go to channel_id 2 instead. Adding a third rule for another marketplace, say eBay, would route eBay orders to their own channel_id the same way, without touching the default or the Amazon rule.
The Same Rule Shape InfiPlex Uses Across Connections
Pairing an order_source with an action_type and a value is not specific to BigCommerce. It's the same connection-level rule pattern behind InfiPlex's push rules on other connections, just naming a different action for a different target system. On a NetSuite connection, for example, the equivalent array carries action types like set_netsuite_item_custom_field and item_sku_map instead of set_bc_channel_id, resolved the same way, source by source, against the same ALL_ORDER_SOURCES default. The full set of NetSuite action types is documented in NetSuite Custom Field Mapping and Order Rules.
Why the Channel ID Matters in BigCommerce
BigCommerce's Channel Manager splits catalog visibility, pricing rules, and order reporting by channel. An order that lands under the wrong channel_id shows up in the wrong channel's order list and skews that channel's own reporting, even though the order itself was processed correctly. Getting the channel_id right at the point InfiPlex pushes the order is what keeps a multichannel seller's BigCommerce account, and its per-channel reporting, matching what actually happened on each marketplace.
BigCommerce Channel Mapping: Questions
What does the BigCommerce channel mapping rule control?
Which BigCommerce channel_id InfiPlex writes onto an order when it pushes that order into BigCommerce. BigCommerce's own Channel Manager separates the primary storefront, any additional storefronts, and marketplace channels by channel_id, and this rule set decides which channel_id a given order lands under.
What is ALL_ORDER_SOURCES?
The catch-all rule. A rule with order_source set to ALL_ORDER_SOURCES supplies the channel_id used for every order unless a rule naming that specific order_source exists to override it. Every BigCommerce connection should carry one, since it's what every source without its own rule falls back to.
How does a specific order_source rule interact with the ALL_ORDER_SOURCES rule?
The specific rule wins for orders from that source; the ALL_ORDER_SOURCES rule still applies to everything else. In the example below, every order defaults to channel_id 1 except Amazon.com orders, which are pushed to channel_id 2 instead.
Do I need a channel rule for every marketplace I sell on?
No. Add a rule only for a marketplace whose orders need a channel_id different from the ALL_ORDER_SOURCES default. Anything without its own rule falls back to the default automatically.
Does the channel_id used here affect BigCommerce's own reporting?
Yes. BigCommerce's Channel Manager reports order volume, catalog visibility, and channel-level settings by channel_id, so an order tagged with the wrong channel shows up under the wrong channel's numbers inside BigCommerce.
Can I combine this with BigCommerce's existing storefronts and marketplace channels?
Yes. This rule only decides which channel_id an incoming order is tagged with; it doesn't change how storefronts or marketplace channels are set up inside BigCommerce itself. It works alongside a multi-storefront BigCommerce account and any channel already configured there.
Is this the same rule pattern InfiPlex uses for NetSuite and other ERPs?
Yes. Order-source-scoped rules pairing an action_type with a value are the same shape InfiPlex uses across its connections. Here the action is set_bc_channel_id and the target is BigCommerce; the ERP-side version, with its full set of action types, is documented in NetSuite Custom Field Mapping and Order Rules.
Every BigCommerce channel, tagged automatically
Channel mapping by order source is included with the InfiPlex BigCommerce integration, alongside order import, inventory sync across every storefront and marketplace, and shipping through 100+ carriers or your 3PL.
