Setka is our product, and it’s the alternative to look at if your BigCommerce operations are fine but every new collection page or product-page change means briefing an agency or reopening a theme project. You bring the catalog and brand direction. Setka builds the store inside its own commerce platform, and you direct later changes by describing them, with no theme code for anyone to maintain.

Stay with BigCommerce if what decides your platform is negotiated wholesale pricing, buyer approvals, several regional or brand storefronts, or an ERP connection your operation already depends on. Those requirements settle the choice before design enters the conversation.

Who does the storefront work on each platform

DecisionBigCommerceSetka
Getting startedChoose an integrated storefront or a composable implementationProvide a brief and catalog for generated storefront pages
Visual editingStencil includes Page Builder and theme settings; Catalyst offers a different implementation pathDescribe changes, directly edit copy, and preview the result
Custom implementationDeeper Stencil changes use theme code; composable builds have their own implementation requirementsThe merchant does not receive a theme codebase to maintain
Publishing changesFollow the chosen storefront’s editing and deployment workflowPublish an approved storefront version inside the platform
Choosing on operational fitEvaluate documented B2B, multi-storefront, channel, and integration requirementsCheckout, variants, promotions, shipping rules, and orders are built in; customer accounts aren’t available yet

BigCommerce’s Stencil documentation covers both visual controls and developer customization, and Page Builder may handle the changes you need without touching code. Its product page also describes Catalyst and Makeswift: Catalyst is a separate composable route for teams with developer resources, with a visual editor for routine changes. The path you choose sets the cost and the maintenance, so choose it first.

A quick way to find out where you stand: write down your next three storefront changes and mark which are editor tasks, which need theme or frontend work, and who keeps that work running afterward.

Where Setka changes the job

Suppose your next homeware collection needs to help shoppers choose a useful housewarming gift. The collection introduction should explain what suits whom; the product pages still need dependable dimensions, materials, and care details. A knowledgeable buyer choosing a gift may need both. That is a reason to change the presentation, not just to make the page look new.

In Setka, you explain that direction and work with the generated pages: ask for a presentation change, edit exact wording, and preview the result before publishing. The homepage, collections, product pages, navigation, and cart stay inside the commerce platform, so the change doesn’t leave your team a theme patch to maintain. Every storefront version is saved, and you can return to an earlier one.

You still own the business decisions: product accuracy, brand direction, shipping policies, and whether the result is ready for customers. Review it the way a shopper meets it, from the homepage message to the collection, through the product facts, to the cart, on desktop and mobile. That review is yours on any platform. What Setka removes is the implementation in between: you describe the change instead of arranging it in an editor or commissioning code.

What BigCommerce charges as you grow

The BigCommerce pricing page, checked on 28 September 2026, uses Core, Growth, Scale, and Performance plan names.

PlanMonthly billingMonthly equivalent with annual billing
Core$39$29
Growth$105$79
Scale$399$299
PerformanceCustomFrom $1,499, subject to contracted terms

Prices are USD before tax, and they cover the subscription, not the whole cost of a store.

The same page lists $30,000 and $100,000 trailing-12-month GMV thresholds for Core and Growth. Scale has a $33,333 monthly GMV cap with a 0.9% overage charge above it. Model your own orders with BigCommerce’s GMV definition and upgrade rules, not a plan’s marketing description; our BigCommerce pricing guide works through those thresholds with example numbers.

The payment provider matters too. The page separates Embedded Payment Providers from Open Payment Providers. It lists no BigCommerce order fee for embedded providers, while open-provider fees are 2% on Core, 1% on Growth, and 0.6% on Scale on the eligible GMV described there. Processor fees come on top. Check your provider’s classification before relying on a “no transaction fees” summary.

For a store whose next changes would go to an agency or a theme developer, Setka usually costs much less: BigCommerce’s subscription is the smaller part of that bill, and in Setka the storefront work is built into the platform. Setka’s price also doesn’t rise with your sales. No GMV threshold moves you up a plan and no platform percentage is added to your orders; Stripe’s processing fees still apply. See Setka’s current pricing. If B2B Edition or extra storefronts are what you need, those are what you are paying BigCommerce for.

When BigCommerce belongs on the shortlist

If you need company purchasing accounts, buyer permissions, quoting, or account-specific purchasing processes, evaluate BigCommerce B2B Edition on those requirements. Don’t assume its specialist capabilities come with every self-service plan.

Likewise, a multi-brand or multi-region operation should map storefronts, currencies, inventory, and integrations before changing platforms. Each Setka store uses one currency, and customer accounts aren’t available yet. If your launch needs either, tell us at contact@getsetka.com: requests go straight to the people building Setka.

A good-looking demo doesn’t replace a B2B buying portal or an integration your operation already depends on.

Settle what has to survive before you move

List what the move must carry: catalog structure, payment methods, shipping and tax rules, customer records, order history, integrations, and existing URLs. Give each an owner who signs off on its replacement, because a clean catalog transfer settles none of the others. If you move to Setka, we run the migration for you: tell us at contact@getsetka.com what you have, including customer records and order history, and we’ll work out the move with you. Redirects from old URLs aren’t available yet, so flag any URLs that carry traffic you can’t lose.

If your buying workflows fit and storefront work is what you want off your team’s plate, start a Setka store. Bring one collection and the next three changes you would otherwise send to a designer or developer. Use the storefront brief to turn those requests into a direction you can review.