Separate the store you want from the systems you need
If changing a collection page means briefing an agency or reopening a theme project, Setka is worth evaluating. If your main challenge is negotiated wholesale prices, buyer approvals, or several regional storefronts, start with those workflows: they can decide the platform before design enters the conversation.
Ordinary selling should already hang together: accurate products, prices and availability, a usable cart and checkout, payment setup, shipping rules, and order handling. A wholesale approval chain or an ERP connection adds a different kind of requirement. Ask what the platform supplies, what needs another service, and who keeps the complete workflow working. A longer feature list earns its place when it solves your store’s actual needs.
Setka is our product. Its case here is specific: you bring the catalog and brand direction, and the platform generates the storefront, connects it to its commerce capabilities, and lets you guide later changes without maintaining a theme codebase.
Choose the BigCommerce storefront path before comparing the work
| Decision | BigCommerce | Setka |
|---|---|---|
| Getting started | Choose an integrated storefront or a composable implementation | Provide a brief and catalog for generated storefront pages |
| Visual editing | Stencil includes Page Builder and theme settings; Catalyst offers a different implementation path | Describe changes, directly edit copy, and preview the result |
| Custom implementation | Deeper Stencil changes use theme code; composable builds have their own implementation requirements | The merchant does not receive a theme codebase to maintain |
| Publishing changes | Follow the chosen storefront’s editing and deployment workflow | Publish an approved storefront version inside the platform |
| Choosing on operational fit | Evaluate documented B2B, multi-storefront, channel, and integration requirements | Checkout, variants, promotions, shipping rules, and orders are built in; customer accounts aren’t available yet |
BigCommerce’s Stencil documentation describes both visual controls and developer customization. Page Builder may cover the changes you need without editing code. List your next three storefront changes and ask which are editor tasks, which require theme work, and who will maintain the result.
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. Choose the implementation path before estimating its cost or maintenance work.
Where Setka changes the job
Suppose your next homeware collection needs to help shoppers choose a useful housewarming gift. The collection introduction should explain suitability; product pages still need dependable dimensions, materials, and care details. A knowledgeable buyer choosing a gift may need both. This is a reason to change the presentation, beyond making 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 storefront change does not hand your team a theme patch to maintain.
You still own the business decisions: product accuracy, brand direction, shipping policies, and whether the result is ready for customers. Setka owns the storefront implementation. Every storefront version is saved, and you can return to an earlier one.
For the second collection change, check more than the requested section. Follow the homepage message to the featured collection, inspect the product facts, and continue through the purchase path on desktop and mobile. The platform owns implementation; the merchant still decides whether the experience serves the buyer. Compare the repeat work of directing and reviewing that change with the work of arranging it in an editor or commissioning custom code.
Read the pricing mechanics
The BigCommerce pricing page, checked on 28 September 2026, uses Core, Growth, Scale, and Performance plan names.
| Plan | Monthly billing | Monthly equivalent with annual billing |
|---|---|---|
| Core | $39 | $29 |
| Growth | $105 | $79 |
| Scale | $399 | $299 |
| Performance | Custom | From $1,499, subject to contracted terms |
Prices are USD before tax. These are subscription amounts, not the complete 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. Use BigCommerce’s GMV definition and upgrade rules when modeling your own orders; a plan’s marketing description is not its billing calculation.
Payment-provider choice also matters. The page distinguishes 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 remain separate. Confirm 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. 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. Do not assume its specialist capabilities are included in 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 [email protected]: requests go straight to the people building Setka.
A good-looking demo does not replace a B2B buying portal or an integration your operation already depends on.
Evaluate a replacement before planning a migration
Write down the workflows that must survive: catalog structure, payment methods, shipping and tax rules, customer records, order history, integrations, and existing URLs. For each essential workflow, name an owner and ask them to approve its replacement before the move. A successful catalog transfer alone does not settle order history, integrations, or URL handling. If you move to Setka, we run the migration for you: tell us at [email protected] 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 required 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.