Move to Setka when the products should lead the store and you want the platform to build and rework their presentation from your direction, instead of arranging it yourself in an editor. Stay on Squarespace when the portfolio, articles, or other site content carry the business and you’re happy shaping them in its editor. A missing link from an article to a product is something Squarespace can fix; it isn’t a reason to move.
Setka is our product, and this page makes the case for it where handing over the storefront is what you actually want.
Follow the story through to the product
Consider a fictional workshop selling nine carved wooden trays and desk objects as separate, fixed-specification products. Its Squarespace site has a portfolio and articles about materials and making. Visitors often arrive to read a story before considering a purchase.
The workshop’s decision is whether the current site turns that interest into a clear buying journey:
- An article explains how the wood is selected and finished.
- A link takes the reader to the relevant collection or product.
- The product page explains dimensions, intended use, care, price, and availability.
- The shopper can add the object to the cart and understand delivery before paying.
Follow that route on a phone with real product information. A beautiful article and a beautiful product page can still leave a poor connection between them. Conversely, if the route already works and you enjoy maintaining it, a new store needs a stronger reason than a different starting design.
Squarespace already gives the workshop a concrete way to make that connection. Its product-block guide, checked on 5 October 2026, documents displaying one store product in a page or blog post. The store page must be enabled, and the product must be published and visible. Its product-display guide, checked on the same date, says product-editor changes update the blocks containing that product. A missing route from an article may therefore be a fix inside Squarespace, rather than a reason to move the store.
Squarespace already generates more than copy
Squarespace’s AI guide, checked on 5 October 2026, describes Blueprint AI Builder, AI templates, generated text and images, and style settings. Its September product update describes a personalized multi-page site generated from business and brand information, with whole-site preview and refinement in the editor. The AI guide also covers rewriting supported text, including product descriptions and blog posts.
Keep Squarespace if that combination suits you: you want to arrange the site, manage the stories, and refine the presentation yourself with AI help. Our Squarespace e-commerce review covers where that combination works best. For the workshop, the useful test is how comfortably you can maintain the article-to-product route and alter the collection as new objects arrive.
Give the product page a specific job
Before changing platforms, write the missing presentation requirement. For one tray, the workshop could ask:
Put the dimensions and a photograph showing scale close to the purchase decision. Explain the finish and care using our supplied facts. Make the matching desk objects easy to find without implying that they are sold as a bundle.
This instruction separates three jobs: supplying accurate product facts, choosing how to present them, and implementing that presentation. The workshop remains responsible for the first two in either platform.
Now give the brief a buyer. A visitor arriving from an article about choosing a useful housewarming gift needs help deciding whether the tray suits the recipient: what fits on it, how much space it takes, and how to care for it. A woodwork enthusiast may also want the finish and construction details. Those are overlapping needs; buying for someone else does not make the visitor a novice.
Keep the arrival promise recognizable. If the article recommends a compact desk tray, lead the visitor to that tray or a clearly explained choice of desk objects, with a photograph that shows scale. A mixed portfolio page may be useful elsewhere, but it should not force this shopper to search for the object just recommended. Product-story fit means the story earns its place by helping someone choose, rather than surrounding the product with attractive prose.
In Squarespace, you carry out that instruction yourself: product settings, page sections, and blocks in the editor, with AI help for the text. In Setka, the store is already generated from your brief and catalog, so you open the tray’s page and give it the instruction above. Setka reworks the page, you check it in preview, edit any wording directly, and publish. There is no theme code behind it for you to maintain.
Either way, judge the result on a phone: can a shopper tell the tray from the matching objects, see its scale, and find the care information? Do the photographs, description, price, delivery promise, and returns terms still describe the same purchase in the cart?
Then make the second change, the one that shows the ongoing work: promote a new finish while keeping the dimensions exact. In Setka that’s another description on the same page, and every change saves a version of the whole store, so you can go back if the new emphasis doesn’t sell.
Separate product fees from content fees
Squarespace’s transaction-fee guide, checked on 5 October 2026, distinguishes platform transaction fees from payment processing. In the current Basic, Core, Plus, and Advanced schedule, ordinary store products have a 2% platform fee on Basic and 0% on Core, Plus, and Advanced. Payment processing remains separate. Our Squarespace e-commerce pricing guide shows at what sales volume each plan costs less.
Digital content, courses, video, and member sites use a separate schedule, so don’t apply their fee to the wooden objects. The guide also says the new plans are rolling out in waves and Plus may not appear in every market, so the plan offered to your site is the one to price.
A 0% platform fee isn’t a zero-cost store: the subscription, payment processing, and any design or development work you buy still add up. Setka’s price doesn’t rise with your sales volume, and Stripe’s processing fees apply. For a product-led store you would otherwise build or redesign with outside help, Setka usually costs less, because the store is built into the platform and the implementation work never appears as a separate bill. See current pricing.
Map the website you would preserve
For the workshop, the editorial archive may be worth more than the inconvenience of a collection layout. Use this map before agreeing to a full replacement:
| Existing asset or job | Decision to make before switching |
|---|---|
| Articles and portfolio pages | Which pages stay where they are, and which content needs a new destination? |
| Important URLs | Which addresses must remain reachable, and what redirect behavior does the destination support? |
| Product facts and media | What export is available, and what does the destination actually accept? |
| Orders and customer records | Which history must be retained, and where will it remain accessible? |
| Forms, scheduling, memberships, or other services | Which jobs continue in their existing tools, and which require a verified replacement? |
| Domain and launch | Who changes the domain connection, and what must pass before the new storefront is promoted? |
Use the migration checklist to turn the decisions into acceptance checks. If you move to Setka, we migrate your store data for you. Redirects from old URLs are not in Setka yet; they’re coming soon.
Setka is a full-store choice, not a product embed in the Squarespace editor. If preserving the existing site is the priority, an embedded-commerce route may be a better architecture to evaluate than replacing the presentation platform.
Choose the work you want to own
For this workshop, keep Squarespace when the articles, portfolio, and editor are serving the business and the product path can be improved with work you are comfortable doing.
Choose Setka when the product presentation, and every change to it, is the work you want the platform to do. You bring the product facts, images, audience, prices, shipping rules, and approval. Setka builds the storefront on its own commerce, checkout included, and keeps a version of the whole store for every change. It supports product variants too, if your catalog has them.
Setka has a built-in blog and CMS, so the stories can move with you. Embedding catalog products in a blog post, which Squarespace’s product blocks already do, is coming soon. If that, or moving a particular archive, layout, or publishing workflow from your preservation map, decides the choice, tell us at contact@getsetka.com before you move. We’ll answer yes, no, or not yet, and requests go straight to the people building Setka.
Start your store in Setka with the product whose presentation has been hardest to get right. Review the generated buying journey before deciding whether a full-store change is justified.