Commerce engineering / BigCommerce
BigCommerce development.
Connected to your business.
BigCommerce development for storefronts, custom apps, B2B buying and the integrations behind the store. Start with your catalogue, buyer journeys and operating systems, then agree the build and acceptance tests in writing.
Discuss BigCommerce requirements โContents ยท BigCommerce
Choose the parts your store actually needs.
A store project can involve a Stencil theme, a separate headless storefront, catalogue migration, custom apps, business buying workflows or integrations with the systems your team already uses. These are different responsibilities. A theme change does not include a warehouse connector simply because both appear on the same store.
- Storefront: navigation, search, product pages, cart and accessible layouts.
- Operations: product and price ownership, stock, orders, fulfilment and returns.
- Integration: ERP, PIM, tax, shipping and payment-provider dependencies.
- Delivery: environments, release access, testing, training and handover.
Put the contract subjects beside the technical scope.
White-label branding, confidentiality, source delivery, IP assignment and post-launch support need written terms for the actual engagement. Define the repositories and materials to be handed over, any third-party licences, the support boundary and the people who can approve changes. BigCommerce platform rights and subscription terms are separate from rights in custom work.
Build around the hosted platform, not around duplicate records.
Begin by identifying what belongs in the commerce platform and what belongs in a connected service. The storefront displays a customer-facing journey; an app or integration can manage a separate business workflow. Decide which system owns each product, price, customer and order field before deciding how to move it.
A second sales channel should not become an unexplained second source of stock or customer records. Define the channel-specific presentation and the shared records, then test how updates and failures travel between them. Measure the storefront using the agreed catalogue and installed integrations, rather than assuming a sparse demonstration predicts the live store.
Compare responsibilities before comparing platform names.
Use the same real catalogue and buyer journeys when comparing BigCommerce, Shopify, WooCommerce or another platform. Avoid a blanket fastest, cheapest or best label. Plan, region, extensions and implementation choices change what is available and what it costs.
- Hosting and operation: who runs the platform, storefront, custom apps and integration services?
- Storefront model: an existing theme, a customised theme or a separately hosted front end?
- Business buying: company accounts, buyer roles, quotes, credit terms and negotiated pricing?
- Multi-channel operation: which records are shared and what is specific to each storefront?
- Commercial terms: current platform plan, transaction and payment fees, paid apps, hosting and maintenance. Verify the vendor quote rather than relying on an old comparison table.
- Exit and ownership: available exports, account access, custom source repositories and third-party licence limits.
Seven decisions before a BigCommerce build.
What belongs in the development scope?
Separate storefront work, catalogue and order migration, apps, system integrations and business buying. A move from another platform may need redirects and data reconciliation as well as a new theme. A wholesaler may need buyer permissions and ERP price mapping before a visual redesign. Write down the workflows, actors, data and acceptance evidence for each workstream.
Stencil theme or a separate storefront?
A theme keeps the storefront close to the platform theme workflow. A headless approach introduces a separately operated front end. Evaluate content needs, accessibility, publishing ownership, app compatibility and hosting responsibility rather than treating headless as an automatic upgrade. BigCommerce documents the GraphQL Storefront API for both Stencil and composable storefront use; it is the API strategy used in Catalyst.
How do apps and APIs fit?
Identify whether an app is private to your store or intended for other merchants. Define its install and uninstall lifecycle, requested permissions, merchant configuration and error reporting. Distinguish the customer-facing Storefront API from management operations. The documented storefront API covers catalogue, customer and cart/checkout operations, but its workflow does not itself perform payment processing.
Which B2B workflows are required?
Ask for a demonstration of the exact company-account, buyer-role, quote, price-list, purchase-order, credit-term and invoice journeys you need. Confirm which current products, plans or extensions supply them. Test a buyer who changes company, loses a permission, receives a revised quote or sees different pricing from a colleague. Product labels alone are not acceptance tests.
How will ERP integration recover?
Assign field ownership, map customer and tax identifiers, define order-state transitions and decide how to reconcile rejected updates. A successful API call does not prove a correct sync. Test duplicate notifications, out-of-order changes, partial records and either system being unavailable. Make replay and reconciliation visible to operators rather than silently discarding failures.
When should another platform be considered?
Compare the required workflows against current vendor capabilities and the work needed to operate them. Existing WordPress content, a specialised checkout requirement, extensive platform-code changes or an established internal stack can alter the choice. Use a written trade-off record with the same acceptance scenarios for each candidate, not an agency ranking.
What will your team own and receive?
List the commerce account, domain, catalogue, customer and order records, content, custom theme, apps, integration services and any separately hosted storefront. Record who controls each item and the permitted export or transfer route. Specify custom-code handover and IP terms without implying that a contract transfers the vendor platform itself.
Keep storefront operations in the comparison
The theme route needs a local-development, bundle-review and publishing workflow. The separate-front-end route needs its own hosting, configuration, monitoring and deployment workflow. Ask whether the content editor, visual page tools and installed apps still work in the chosen architecture. A theme app that injects browser scripts cannot be assumed to appear automatically on another front end.
Include search, category filtering, product options, account access, cart persistence and checkout handoff in the comparison. A successful product-page render does not establish that the whole storefront works. Use the same promotion, tax and shipping examples to check the complete purchase journey.
Write the integration mapping before the connector
Record ERP customer codes, commerce customer groups, tax identifiers, product and variant identifiers, warehouses, currency and fulfilment status. Decide how cancellations, refunds and partial shipments move between systems. Identify whether each connector is an installed app, an integration service or custom code, and who operates it.
For an unavailable ERP, decide whether the store can accept an order, how that pending transfer is shown and when an operator intervenes. For unavailable commerce APIs, define what data remains available, which updates are held and how reconciliation resumes. Neither direction should silently overwrite a newer record from the other system.
Stencil framework detail
Stencil is BigCommerce's own theme framework: Handlebars templates, SCSS and JavaScript, developed locally with the Stencil CLI and pushed to the store as a bundle. BigCommerce documents Page Builder support for Stencil themes and publishes Cornerstone as an open-source starting point. Choose a theme and extensions whose current compatibility has been checked, rather than assuming all marketplace apps work together.
Use the local preview to review real catalogue content across devices before publishing a bundle. Separate theme configuration from sensitive credentials. Theme customisation still needs accessibility, script and checkout testing: selecting a responsive base theme is not the same as verifying your finished storefront.
B2B Edition detail
The current B2B Edition documentation describes company accounts, sales quotes, invoice management, user roles and sales-agent assistance. Its Buyer Portal can use a default or customised build for Stencil or headless storefronts. Map those capabilities to your actual purchasing workflow before deciding what custom work is needed.
A buying company may have several users with different approval and purchasing rights. Specify whether a quote can be changed, who approves a purchase, which addresses are permitted and when an outstanding invoice prevents another order. Confirm the selected plan and configuration rather than treating every B2B function as an included feature of any store.
Installed app lifecycle
For the documented single-click app model, the merchant approves requested permissions and the app exchanges the authorisation code for a store-specific access token. The app's interface is then rendered in an iframe in the control panel. Keep tokens confidential, request only the needed scopes and validate the authorisation flow.
BigCommerce documents callbacks for loading an app, uninstalling it and removing a user's access. The load and auth callbacks are required; uninstall and remove-user handling are recommended. If an app does not implement uninstall handling, the platform still uninstalls it, but the app may not know. Define cleanup, cached-access invalidation and retained-record policy, and verify signed callback payloads before acting on them.
Keep the boundaries visible in the architecture.
Theme, application and integration boundaries
Agree which code renders the interface and which code controls business rules or integration jobs. Keep deployable components, configuration and permissions understandable. The goal is a change that can be tested and released without unexplained edits in a live control panel, not a promise that every feature can be changed without risk.
Token types are not interchangeable
Current BigCommerce guidance distinguishes browser storefront tokens from private tokens for server-to-server and headless interactions. Private tokens must not appear in browser code. Customer-specific access needs its documented customer context. Select the documented token for each request path, keep secrets out of theme assets and repositories, and test that one customer cannot obtain another customer's data.
Webhook intake, queue and reconciliation
Design intake to authenticate an event, validate its structure, record it durably and acknowledge it promptly. BigCommerce recommends validating signatures and timestamps, and describes custom-header authentication. Apply its current verification mechanism, including replay handling, before processing an event. A shared-secret comparison by itself is not a complete production webhook design.
A worker can retrieve the current order and update the ERP using a stable external identifier. Define idempotency, retry policy, retained failure evidence and manual replay. Test a duplicated notification, a failed downstream update and a worker restart. A queue deduplication setting does not by itself prove that every downstream side effect is safe to repeat.
Performance uses the actual workload
Define the catalogue size, images, variants, filters, promotions and third-party scripts used for testing. Check mobile product, category, search and checkout paths. Record query complexity, caching behaviour, invalidation and failure states. Keep business results such as conversion separate from technical measurements.
A replayable order-transfer sequence
- Receive the event over the agreed endpoint and verify it using the vendor's current authentication and signature guidance.
- Validate the expected event type, identifiers and timestamp before recording work. Keep request material needed for verification intact for that verification.
- Persist the work durably and return the required acknowledgement promptly. Record a failed intake rather than acknowledging work that has been lost.
- Read the authoritative order and map it to the ERP's required customer, tax, product and fulfilment identifiers.
- Apply an idempotent create-or-update operation with a stable external reference. Test how the ERP responds when the same request is repeated after a timeout.
- Retain success, retry and terminal-failure evidence. Provide a supported replay route and reconcile orders that have no matching downstream record.
This is a design sequence, not runnable endpoint code. Choose retry limits, backoff, queue retention, timeouts and operational alerts for the actual integration. A replay must not create a duplicate shipment, invoice, charge or sales order.
Shared API capacity and back-pressure
BigCommerce documents a shared store quota for applications using the REST APIs, with availability depending on the plan and requested resources. Read response headers and handle a rate-limit response rather than assuming an integration has a private unlimited allocation. Avoid publishing fixed quota numbers in a long-lived implementation plan without checking the merchant's current plan.
For HTTP 429 responses, the current guide describes waiting according to the rate-reset header before retrying. Spread work, cache suitable results and make the queue visible when it grows. Define what happens if an initial catalogue import competes with live order transfer for the same capacity. A retry policy should also respect downstream ERP limits and the operational priority of each job.
Three engagement shapes, agreed to the actual work.
- Related platform: evaluate an existing marketplace or shopping product on its own stack. Do not describe it as a BigCommerce store without evidence.
- Custom BigCommerce work: agree the storefront, apps, data migration and integrations, with responsibilities and acceptance evidence for each.
- Ongoing development: agree capacity, release approval, operational ownership, support boundaries and cancellation terms. No monthly price or notice period is assumed here.
Six acceptance areas to put in the scope.
- Review: changes are traceable, reviewed and tested before the agreed release.
- Testing: pricing, mappings, permission rules and API failure cases have defined automated or repeatable checks.
- Storefront performance: measurements use representative catalogue data and installed app behaviour.
- Handover: source, build instructions, configuration inventory, documented permissions, deployment steps and runbooks are deliverable items. Transfer secrets through an agreed secure route, not ordinary documentation.
- Launch: redirects, domain and certificate responsibilities, tax, shipping, payment tests, rollback and approval are explicit. These require separate owner authority at execution time.
- After launch: monitoring ownership, incident response, bug boundaries and any support period are written terms, not an implied universal guarantee.
Make the evidence reviewable
Agree which checks run on every change and which require a release review. Search, cart and checkout need end-to-end checks as well as tests for pricing and data mapping. Test every enabled payment method on the agreed phone and desktop browsers using the provider's supported test process.
The handover inventory can include the theme source and bundle, app and integration repositories, environment setup, API scopes, webhook registrations, store-access roles and a post-launch runbook. Keep access transfer separate from code delivery, with explicit owner approval and a secure route for credentials.
Launch checks should cover redirects from the actual URL inventory, domain and certificate readiness, tax and shipping rules, installed apps and webhook registration. Record the approval and rollback plan rather than treating a green build as permission to change the live store.
Technology options by responsibility.
The implementation should name the tools it actually uses and why. This is an option map, not a claim that every project includes every product.
- Storefront: a Stencil theme or a composable front end such as Catalyst; the design determines the choice.
- Commerce interfaces: GraphQL Storefront API, management APIs and supported webhook events.
- Custom app and integration runtime: selected language, hosting environment and storage for the required workflow.
- Background processing: durable work records, retry handling and operator-visible reconciliation.
- Delivery and operation: version control, CI, environment configuration, logs, performance tests and error monitoring.
- Business integrations: the chosen ERP, PIM, payment, tax and shipping systems, each with its own current access and service terms.
Named options from the original scope, not a mandatory bundle
- Stencil: evaluate the Handlebars theme and local CLI/bundle workflow for the selected theme approach.
- Catalyst / Next.js / React: evaluate a composable storefront and the responsibility for its independent hosting.
- BigCommerce Apps: define install authorisation and control-panel screens for the chosen app type.
- B2B Edition / Multi-Storefront: check the current plan and required company-account, quote, pricing and storefront workflows.
- Stripe / PayPal / Adyen: compare availability, supported checkout integration, currencies, testing and current provider charges for the merchant's region.
- NetSuite / SAP / Dynamics / Acumatica: identify the actual edition and connector interfaces, not only the ERP brand.
- Node.js / PostgreSQL: possible app runtime and operational-data storage, subject to the app's requirements.
- Redis / BullMQ: possible queue and retry components, with persistence and downstream idempotency still needing design.
- GitHub Actions / Sentry: possible build automation and error tracking, with access, retention and data handling agreed.
- Docker / AWS: possible packaging and hosting choices for custom components. Hosting responsibility, region and costs remain scope decisions.
From brief to handover, with explicit dependencies.
- Brief: catalogue, buyer journeys, existing systems, constraints and authorised stakeholders.
- Scope: field ownership, required integrations, access model, environments and acceptance scenarios.
- Build and review: working increments on an agreed test environment, with open decisions recorded.
- QA and reconciliation: representative data, permissions, failures, mobile layouts, payments and migration checks.
- Launch and handover: owner-approved cutover, supported rollback, configuration/runbook delivery and operational ownership.
What changes the estimate?
A useful quote separates one-time implementation from recurring vendor and operating costs. Prices and delivery dates require a current written quote.
- Theme customisation versus a separately hosted storefront.
- Catalogue size, variants, media, historical orders and data cleanup.
- Number of storefronts, currencies, languages and regional requirements.
- Business buying, buyer permissions, quotes and negotiated pricing.
- ERP, PIM, tax, shipping and payment integrations, including exception handling.
- Private versus distributed apps, installation lifecycle and vendor review obligations.
- Migration rehearsal, redirects, launch support, training and handover.
- Current platform plans, paid extensions, payment-provider fees and hosting for custom components.
An illustrative distributor workflow.
Consider a distributor whose customer-specific prices and stock are held in an ERP. The required outcome is consistent permitted pricing, an auditable order transfer and reconciliation when a system is unavailable. This is a planning scenario, not a claimed client project or measured result.
- Identify the buyer's company and permissions before returning its eligible catalogue and prices.
- Agree whether prices are read live, synchronised or cached, and how stale data is shown.
- Record order intake durably, authenticate notifications and use replay-safe downstream identifiers.
- Show rejected records and reconciliation work to the operations team.
- Rehearse historical-data import and old-URL redirects using agreed samples before cutover.
A separate cross-border retail scenario
A fashion retailer selling to several currency regions may need regional storefront presentation, shipping rules, duties and tax information, and inventory updates from several fulfilment providers. This is an illustrative requirements set, not a client result, launch-time claim or revenue forecast.
- Decide whether regional storefronts share products and stock and which price, language and currency differences are intentional.
- Check the chosen tax or duties provider, including any Zonos or other integration, against its current supported markets and the checkout model.
- Define delivered-duty-paid calculations, unavailable estimates, refunds and changes to a destination address.
- Map each warehouse or 3PL identifier to fulfilment events and inventory updates, including partial fulfilment.
- Test what the customer sees before purchase, including shipping charges and duties. Do not infer a reduction in abandonment from the presence of an integration.
- Agree measurable acceptance evidence. No particular delivery duration, revenue lift, support window or first-month user count is assumed.
BigCommerce delivery review and handover.
Agree the implementation boundary, deliverables and acceptance checks in the project scope. Include the source and configuration to be handed over, third-party dependencies, account ownership and the receiving owner's installation and operating walkthrough. Review the selected work at the agreed milestones, with unresolved items recorded before release.
Proposed acceptance evidence includes a reproducible build, a preview using representative data, tested permission boundaries, migration reconciliation and a written handover inventory. Confirm business identity, commercial terms and contact details directly before signing an engagement.
Translate the sector into operating requirements.
- Retail: variants, stock, promotions, fulfilment, returns and customer support.
- B2B distribution: company accounts, buyer roles, negotiated prices, quotes and ERP reconciliation.
- Healthcare-related commerce: permitted product categories, sensitive-data boundaries and jurisdiction-specific obligations.
- Media or creator commerce: content access, subscriptions, cancellation and entitlement changes.
- Cross-border operation: language, currency, tax, shipping, payment eligibility and customer communications.
- Telemedicine: consultation packages, recurring access and sensitive-data boundaries must be assessed separately from ordinary product checkout.
- Fintech-related checkout: supported payment instruments, fraud review, refunds and provider restrictions need explicit checks.
- Transportation and mobility: parts catalogues, fleet supplies and booking-deposit workflows need their own identifiers and cancellation rules.
- Food and beverage: menus, ordering cutoffs, delivery zones, stock availability and loyalty need defined operating rules.
Questions to settle before work begins.
Does a store build include mobile apps?
Not automatically. Agree responsive storefront testing separately from a native or cross-platform shopping app. An app has its own supported-device, authentication, release and store-review requirements. BigCommerce web or app integrations and Apple or Google app-store publication are different processes.
What does the admin experience include?
Identify the platform control-panel workflow and any custom app screens your staff will use. Agree who can change products, prices, orders, promotions and integration settings. Test a staff account with limited permissions rather than checking only the store owner.
Can an existing store be migrated?
Inventory source exports, identifiers, media, product variants, customer and order records, redirects and unsupported fields. Rehearse import and reconciliation before cutover. Do not assume passwords can be transferred or redirects preserve rankings. The source platform, authentication design and search-engine behaviour determine those limits.
How are schedule and price agreed?
Use the selected workflows, vendor dependencies, data readiness and acceptance evidence to prepare a written scope. Record who supplies accounts and content, who approves changes and what happens when a dependency is delayed. A recurring service needs its own capacity and termination terms.
What happens when something fails after handover?
Agree which organisation watches errors, who can deploy a fix, what is a defect versus a new requirement and how incidents are escalated. Confirm any support period and exclusions in the contract. Record coverage, response expectations and escalation in the actual support agreement.
Can a different team continue the work?
Make that testable: have the receiving team follow the build and deployment instructions using approved access, locate configuration and dependencies, inspect integration mappings and run the acceptance tests. A repository alone is not a complete handover.
How should confidentiality and IP be handled?
Agree confidentiality before sharing sensitive technical or commercial information. The contract should name the parties, permitted use, exclusions and handling of materials. Source delivery and IP assignment are separate subjects: define what is custom work, what is licensed and what remains a third-party platform.
Can work be done remotely?
Confirm the actual contracting entity and delivery contacts. Set the working timezone, review and escalation channels, required overlap and any on-site work in writing. Do not infer an office in a city from a service page or assume a response window that has not been agreed.
Freelancer or company?
Match the scope to demonstrated capability and continuity. A small isolated theme change and a combined storefront, ERP migration and app build have different coordination needs. Ask who is accountable for architecture, QA, deployment and handover; how absence is covered; and who owns any subcontractor output. A company label alone does not answer those questions.
What is the app-review boundary?
A store-specific integration, a merchant-facing marketplace app and a shopping app for phones are different deliverables. Confirm whether vendor review, listing material, certificates, review responses and later updates are included. Vendor approval and review timing are not controlled by a development provider.
Platform references used for the technical checks.
Current vendor documentation was checked on 16 November 2026. Vendor capabilities and terms can change; confirm the selected API, plan and integration behaviour during implementation.
Bring the catalogue and the difficult workflow.
Start with the part that is hard to operate today: buyer permissions, ERP mapping, catalogue migration, storefront performance or a custom app. Define the desired outcome and the evidence that would show it works.
Discuss your BigCommerce scope โ