BigCommerce Customization and B2B Storefront Engineering

Summary

We build custom BigCommerce storefronts and the trading logic around them, including business-to-business selling into manufacturers and regulated product categories. This kind of work covers Stencil theme engineering, catalogue and pricing modelling, storefront and management API integration, webhook-driven synchronisation with back-office systems, and the compliance decisions that surround checkout. The goal is a store that works with the platform rather than against it, so it stays fast and maintainable through platform updates.

The Challenge

BigCommerce is a hosted, multi-tenant platform, so a custom build is not a matter of editing arbitrary server code. The storefront is a Stencil theme rendered from Handlebars templates, styled with SCSS and progressively enhanced with JavaScript, while catalogue, order and account data are reached through platform APIs. Building well inside those boundaries produces a fast store; fighting them produces one that breaks at the next platform update.

Selling to manufacturers rather than consumers changes the shape of the work again: buyers expect account registration and approval, specification detail on every listing, repeat ordering, and volume-based pricing rather than a single retail price. Regulated categories tighten it further. Hemp, agricultural derivative and similar lines face payment processor restrictions, so a high-risk merchant account and a gateway that explicitly permits the category have to be confirmed before build, not after launch.

The recurring failures are predictable. Heavy browser-side scripting bolted onto a theme degrades performance and mobile conversion. Business logic written into Handlebars templates cannot be tested and becomes unmovable. Direct API calls from browser code leak credentials or exhaust rate limits. Inventory synchronised on a fixed schedule instead of by event drifts out of step and oversells.

The Solution

Components

• Stencil theme built from Handlebars templates and partials, developed locally against the Stencil CLI so template context and rendering can be tested before anything is pushed.
• Storefront GraphQL API for authenticated, on-page data such as account-specific pricing, stock and account details, avoiding stale cached values in a page served from the edge.
• Management API for catalogue, inventory, order and account synchronisation with back-office systems.
• Webhooks for order creation, shipment and inventory events, consumed by a small middleware service with retry and replay handling.

Catalogue and pricing model

The catalogue model deserves more design time than the theme. Variants, modifiers and option sets behave differently: variants carry their own stock keeping unit and inventory, modifiers change price or capture input without creating a separate stock record. Getting that wrong makes inventory reconciliation impossible later. For wholesale buyers, customer groups and price lists carry tiered and contract pricing, and minimum order quantities and case or pallet units of measure are represented explicitly rather than approximated with product notes.

Checkout and compliance

Checkout is the most constrained area of the platform, and that constraint is deliberate: it keeps card data out of the storefront and narrows the cardholder data environment. Customisation happens through the supported checkout SDK and approved payment providers rather than by intercepting the payment step. Regulated categories add age or business verification, jurisdiction-based shipping restrictions, and downloadable certificates of analysis attached to product or batch records. Tax treatment varies by jurisdiction and product classification, which usually means an automated tax service rather than manual rate tables.

Administration

Administration covers accounts and approval states, product listings and specification attributes, inventory levels, order status and fulfilment, and returns, so that routine trading decisions never require a developer.

How we build it

We model the catalogue and pricing rules first, then build the theme against real product data rather than placeholders, keeping integration logic in a middleware service so the storefront stays presentational. Staging environments mirror the production configuration, and the store is quality tested end to end, from account creation through order placement, shipping and returns, on current Chrome, Safari and Firefox and on real mobile devices.

What This Delivers

Trade buyers get a storefront that reflects how they actually purchase, with approved accounts, contract pricing and repeat ordering instead of a retail flow bent into shape. Stock and orders stay in step with the back office because synchronisation is event-driven. Compliance obligations for a regulated category are settled before launch rather than discovered by a declined payment, and the theme remains upgradeable because logic lives outside it.

Technologies and Tools

BigCommerce Stencil with Handlebars, SCSS and the Stencil CLI, the Storefront GraphQL API and Management API, platform webhooks, a middleware service for integration and retry handling, the supported checkout SDK with approved gateways, and an automated tax service.