By E-commerce 4 Internet Marketers Editorial
Review / comparison. This article compares documented catalog controls, payment ecosystems, multi-storefront options, and API surfaces on BigCommerce and Shopify for website owners and developers who sell regulated or higher-risk SKUs. Facts below come from official product and developer documentation. Interpretation is labeled separately. This is not legal advice, underwriting advice, or a guarantee that either platform will host or process every vertical.
Why catalog control matters for regulated SKUs
Merchants who sell hemp-derived products, supplements, alcohol, firearms accessories, nicotine goods, or other restricted categories often need more than a single public catalog. They may need to hide SKUs by region, keep wholesale packs off a DTC site, publish different assortments to marketplaces, or route checkout through a specialty processor when the platform’s native payments product declines the category.
Platform choice shapes how hard those splits are without custom engineering. The four surfaces that show up most often in build plans are catalog publication rules, payment app and gateway ecosystems, multi-storefront or multi-market arch
BigCommerce Multi-Storefront models each storefront or marketplace as a channel. Official developer docs state a cardinal rule: products must be explicitly assigned to a channel to be sold on that channel. On native Stencil storefronts, products that are not assigned to the storefront’s channel are hidden from that channel. Category membership is separate from channel assignment. Removing a product from a category does not remove it from the channel. Merchants manage assignments through the Catalog API channel-assignments endpoints and control-panel workflows.
Category trees are also channel-scoped. Docs say a store can create multiple category trees, and that a tree may currently be assigned to a maximum of one channel. Price lists can be assigned to channels, customer groups, or a channel plus customer group combination, with documented precedence when more than one assignment could apply.
Shopify (documented facts)
Shopify Markets docs state that products excluded from a market’s catalog are hidden from storefronts, omitted from search, and blocked from cart in that market context. If a buyer changes shipping address into a restricted market, restricted items are removed at checkout. Market catalogs inherit from parent markets and are added alongside inherited catalogs rather than replaced.
Shopify also documents variant-level publishing so individual variants can be published or unpublished independently of the parent product on a given publication, which the docs explicitly call out for region-based restrictions among other use cases.
Interpretation
Both platforms can hide regulated SKUs from specific selling contexts without deleting them. BigCommerce’s channel-assignment model is explicit and storefront-centric inside one store. Shopify’s publications model spans Online Store, markets, B2B locations, and apps inside one shop, with Markets as the main single-store regional assortment tool. Neither catalog API replaces licensing, age gates, or carrier rules. Those remain merchant and partner responsibilities.
Payment app ecosystems side by side
Shopify Payments versus third-party providers (facts)
Shopify Payments eligibility help states that only eligible merchants can use Shopify Payments, and that business type and products must not be prohibited. High-level prohibited examples in that help article include regulated or illegal products and services such as cannabis and related products, prescription drugs, medical devices, tobacco and related products, firearms, holsters, ammunition, or weapons, plus financial services, adult products, pseudo pharmaceuticals with unverified health claims, gambling, and counterfeit goods. Shopify says the list is not exhaustive and varies by region, and points merchants to country-specific lists, the Shopify Payments Terms of Service, and the Acceptable Use Policy.
If a merchant is not eligible for Shopify Payments, Shopify’s third-party payment provider docs say the store can choose from more than 100 credit card payment providers. Shopify distinguishes direct providers (payment completes on the online store) from external providers (redirect to a hosted page). Third-party transaction fees apply on third-party gateways per Shopify billing docs. Shopify also documents payments extensions that only approved Partners can build, with custom credit card payment extensions limited to eligible Shopify Plus merchants who confirm eligibility with Plus Support.
BigCommerce payment gateways and Payments API (facts)
BigCommerce’s Payments API overview lists many compatible gateways for API-driven payment processing, including Authorize.net (stored instruments and raw card data) and NMI (raw card data), along with Stripe variants, PayPal Commerce Platform, Braintree, Adyen variants, and others. The same docs state that the Payments API does not support gateways that are not on the compatible list. BigCommerce’s Transactions API docs describe importing externally processed transactions for a smaller set of providers (including Authorize.net, Braintree, PayPal Commerce Platform, and Stripe) so post-order capture, void, and refund can stay in BigCommerce when payment happened outside the platform.
Commerce’s Acceptable Use Policy (which covers BigCommerce under the Commerce terms) requires merchants to represent that products and services comply with applicable law, and disclaims responsibility for evaluating product legality. It also notes third-party service provider policies can affect regulated products.
Interpretation
For many high-risk catalogs, the binding constraint is often the payment stack rather than the storefront CMS. Shopify’s public Shopify Payments eligibility language is explicit about several regulated categories. BigCommerce’s public Payments API surface documents Authorize.net and NMI among compatible gateways, which matters when specialty acquiring already sits on those processors. App-store or Partner approval still gates custom payment UX on both sides. Merchants should confirm acquiring bank rules and platform AUP separately from “gateway appears in the admin” screenshots.
Multi-storefront and multi-market architecture
BigCommerce Multi-Storefront (facts)
BigCommerce’s Multi-Storefront overview describes selling from multiple website storefronts and other channel types (marketplace, POS, marketing, custom) from a single catalog in one BigCommerce store. Each storefront can have its own site URL, theme configuration, scripts, pages, redirects, and channel-level settings. Channel 1 is the default storefront channel and cannot be deleted. Docs emphasize that partners and apps must pass channel_id on carts, checkouts, and orders so shoppers are not accidentally tied to default-channel configuration.
Shopify Markets and expansion stores (facts)
Shopify Markets configure buyer experiences (including catalogs, pricing, and web presence such as domains, subdomains, or subfolders) for groups of buyers matched by conditions. That is a localization and assortment layer on one shop.
Separately, Shopify Plus expansion stores are additional .myshopify.com stores under one organization and contract. Shopify Help states each expansion store operates independently with its own data, settings, and configurations. Products, collections, and inventory are not synced between stores by default. Organizations can have one main store plus up to nine expansion stores (ten total) at no additional license cost on standard Plus contracts, with staging stores outside that limit. Expansion stores must meet branding and product-type eligibility rules documented by Shopify.
Interpretation
If the goal is multiple branded public sites with shared admin catalog controls, BigCommerce MSF is the documented single-store multi-website path. If the goal is regional assortment and pricing inside one Shopify shop, Markets catalogs are the documented path. If the goal is hard operational isolation (separate apps, themes, and catalogs), Shopify Plus expansion stores are separate shops that must be synchronized by apps or ERP if shared inventory is required. High-risk teams often pick isolation when underwriting or policy risk differs by brand or region. That preference is an operating judgment, not a documented platform ranking.
API flexibility for custom catalog and checkout work
BigCommerce (facts)
BigCommerce documents REST Store Management APIs (including Catalog), a REST Storefront API for carts and checkouts, a GraphQL Storefront API for headless and Stencil frontends, Customer Login and Current Customer APIs, and the Payments API. GraphQL Storefront docs describe querying products, carts, and checkout initiation, including channel-context URLs for non-default channels. Multi-storefront API guidance covers channel assignments, category trees, price-list assignments, and site-scoped scripts and pages.
Shopify (facts)
Shopify’s primary Admin surface for modern apps is the GraphQL Admin API, including publications, catalogs, markets, and product mutations. Buyer-facing custom storefronts use the GraphQL Storefront API (Shopify documents Storefront as GraphQL-only). Markets and publishing guides show Admin mutations for publication state and Storefront @inContext queries so headless clients only see products available in a country or buyer context.
Interpretation
Both platforms are capable of headless and automation-heavy catalogs. BigCommerce’s channel assignment and tree model maps cleanly to “this SKU exists on wholesale site A and not on retail site B.” Shopify’s publication and Markets model maps cleanly to “this SKU is unpublished for market X and sales channel Y” inside one shop, with expansion stores used when true multi-shop isolation is required. Engineering cost usually tracks how many contexts must stay in sync, not which logo is on the admin login.
Comparison snapshot for operators
| Surface | BigCommerce (docs) | Shopify (docs) |
|---|---|---|
| Hide SKU from a selling context | Explicit channel assignment required | Publish/unpublish to publications (channels, markets, B2B) |
| Regional assortment | Separate storefront channels, price lists, settings | Markets catalogs; optional expansion stores on Plus |
| Native payments vs specialty gateways | Payments API lists Authorize.net, NMI, and many others | Shopify Payments has prohibited categories; 100+ third-party providers; Partner payments apps |
| Multi-website in one admin | Multi-Storefront channels and sites | Markets web presence on one shop; expansion stores are separate shops |
| Headless / automation | REST Management + GraphQL Storefront + Payments API | GraphQL Admin + GraphQL Storefront |
What this review does not decide
Official docs do not publish a single scorecard that crowns either platform for every regulated vertical. Commerce AUP language puts legality on the merchant. Shopify AUP language likewise puts legal and payment-partner compliance on the merchant, and notes that payment terms can be stricter than storefront hosting alone. App marketplaces change. Gateway eligibility changes by MCC and acquiring bank. Any “we sell X on Y successfully” claim outside current official docs is omitted here.
Practical shortlist before choosing
- Map every regulated SKU to the contexts where it must be invisible (region, DTC vs wholesale, marketplace).
- Confirm whether Shopify Payments or a specialty processor will actually underwrite the MCC, then confirm the matching BigCommerce or Shopify gateway/app path.
- Decide if shared-catalog multi-site (BigCommerce MSF or Shopify Markets) is enough, or if separate Shopify expansion stores (or separate BigCommerce stores) are required for risk isolation.
- Prototype publication or channel assignment via API on a staging catalog before migrating live inventory.
- Keep age verification, claims review, and shipping carrier rules outside the platform comparison. Those controls are merchant-owned on both stacks.
Sources
- BigCommerce Multi-Storefront overview
- BigCommerce Multi-Storefront API guide
- BigCommerce Payments API overview
- BigCommerce Transactions API
- BigCommerce About Our APIs
- BigCommerce GraphQL Storefront API overview
- Commerce Acceptable Use Policy
- Shopify Markets
- Shopify product and variant publishing
- Shopify Payments eligibility
- Shopify third-party payment providers
- Shopify payments extensions
- Shopify Plus expansion stores
- Shopify Acceptable Use Policy
Shopify’s publishing framework is built on catalogs and publications. Developer docs describe AppCatalog (sales channels such as Online Store or POS), MarketCatalog (international markets), and CompanyLocationCatalog (B2B company locations). Each catalog can have a publication, which is the set of products and collections visible in that context. Merchants and apps publish or unpublish products (and, where supported, variants and collections) with GraphQL Admin mutations such as publishablePublish and publishableUnpublish.