Question 1

Do you work with Stencil themes or headless setups?

Accepted Answer

Both. Most of our work is with Stencil themes since that's what most BigCommerce stores use. We also build headless storefronts using Next.js, Nuxt, or other frameworks when the project calls for it—typically when you need experiences that go beyond what Stencil can deliver.

Question 2

Can you customize the BigCommerce checkout?

Accepted Answer

Within the platform's constraints, yes. BigCommerce's checkout is managed, which limits certain customizations for security reasons. We can add custom fields, modify layouts, integrate with additional services, and implement custom validation. For more extensive checkout changes, we'd discuss Checkout SDK or headless options.

Question 3

How do you handle code handoffs?

Accepted Answer

All code lives in your repository from day one. We document everything—not just what the code does, but why decisions were made. When the project ends, you have complete ownership and any competent developer should be able to maintain and extend our work.

Question 4

What if we already have custom code that's causing problems?

Accepted Answer

We can audit existing customizations to identify issues and recommend fixes. Sometimes it's worth refactoring; sometimes rebuilding is more practical. We'll give you an honest assessment of what makes sense for your situation and budget.

Question 5

Do you build BigCommerce apps?

Accepted Answer

Yes, both single-store apps and marketplace apps. Single-store apps are custom functionality built specifically for your store. Marketplace apps are more complex, requiring OAuth, billing integration, and multi-tenant architecture. We've built both.

Question 6

How do you ensure custom code doesn't break with BigCommerce updates?

Accepted Answer

We follow BigCommerce's documented APIs and avoid undocumented features that could change without notice. We use their official SDKs where available. We also build with testing in mind, so you can verify functionality after platform updates before pushing to production.

Build what the platform allows, not what it fights.

Custom Storefront Features

Backend Tooling

Performance Optimization

Headless Commerce

Code that ages well

Frequently asked questions