When the template becomes the work
You want to introduce a collection with its making process, show the differences between pieces, and give buyers the details they need. If you can do that in your Big Cartel template, keep it. If each collection sends you back into layout work or custom code, changing how the store gets built is a better reason to move than finding another template.
Setka is our product. We recommend it when the storefront you want would otherwise become a customization project: you supply the products and brand direction, and Setka generates the store inside its commerce platform. You can describe later changes, edit exact wording, preview, and publish without maintaining a theme codebase.
Two ways to make the store yours
| Decision | Big Cartel | Setka |
|---|---|---|
| Starting the design | Choose a template and adjust its settings | Supply a brief and catalog for storefront generation |
| Refining the result | Use the template’s available settings; deeper changes can involve HTML/CSS | Describe changes and edit copy inside the storefront workflow |
| Before publishing | Preview template changes | Preview the generated storefront version |
| Reversing direction | Check what template switching preserves and how custom settings behave | Return to an earlier storefront-wide version |
| Best fit | You like configuring a creator-focused template store | You want to direct the design without owning its theme implementation |
Big Cartel documents visual customization and code editing, while its template guide explains that layout and presentation options vary by template. Code is an option for deeper changes, not a requirement for every merchant.
In Setka, the generated homepage, collections, product pages, navigation, and cart use your product and brand context. When the presentation needs changing, you work on the result inside the platform. You still decide what the store should say and whether the design is right.
A useful test: change how one collection is presented
Take a ceramics collection whose making process matters as much as its product photos. Prepare a short studio story, three representative products, dimensions, and care instructions. Use this hypothetical brief to check three things:
- Can the collection introduce the process before asking someone to choose a piece?
- Can a buyer find dimensions and care information without hunting through a long description?
- Does the mobile layout leave the product and purchase action clear?
With Big Cartel, inspect the relevant template’s layout options before assuming you need custom development. If the template already supports the presentation, that is a practical win.
With Setka, use the story and catalog in the brief, then request refinements to the generated pages. Preview the result before publishing. Every version is saved, so you can return to an earlier storefront version.
After the first version, change the brief: feature a different piece and shorten the story. Keep its dimensions, care advice, availability, and dispatch information accurate. Follow the changed collection through a product page to the cart on desktop and mobile. The studio story should help someone choose; it should not displace the facts they need to buy.
That second pass tells you how you will run the store after launch. Record who makes the change, who checks the purchase path, and who fixes any mismatch. We would judge a platform by whether you can keep adapting the store this way as the brand grows. An attractive first version is only the start of that job.
Compare costs without treating free as a problem
Big Cartel’s pricing page, checked on 28 September 2026, lists a free Gold plan, Platinum at $15 per month, and Diamond at $30 per month in its monthly view. Billed annually, the two paid plans cost $144 and $288 a year.
Big Cartel advertises 0% platform transaction fees. Stripe or PayPal processing fees remain separate. A small store that fits the free plan should count that as a real advantage.
If your template already presents each collection well, Big Cartel’s free or $15 plan is the cheaper store, and no development budget should be invented to justify moving. If every collection change means paying for layout or code work, that work is the larger cost. In Setka the store is built into the platform, so that line mostly disappears; see our current pricing.
Check the catalog before moving
Big Cartel documents product variants and inventory behavior, including variant-group dropdowns. If your store depends on combinations such as size and color, that is a buying requirement, not a minor detail.
Setka supports product variants. If your catalog depends on particular options, such as glaze and size together, tell us at [email protected] before you move: requests go straight to the people building Setka.
For products sold as separate, defined items, focus the evaluation on presentation, shipping, payments, and the day-to-day changes you expect to make.
Moving is a separate project from choosing the design
Big Cartel documents order CSV exports. If you are moving an existing store, Setka runs the migration for you: tell us at [email protected] what you have, whether orders, customers, blog posts, or anything else, and we’ll work out the move with you. Self-service import and redirects from old URLs are not available yet, so mention any URLs that carry search traffic you can’t lose.
Keep the current store operating while you check the replacement. For products, images, order history, customer records, URLs, and integrations, record what transfers, what needs rebuilding, and what you will retain as an archive before changing the domain.
If the collection exercise describes the work you want to stop maintaining, start your store in Setka. Bring the three products and the presentation you want to achieve; use the brief guide to prepare the direction. Make the decision on a store built around your work, with your catalog requirements checked before you move.