Is the website an asset, or the work you want to replace?

Ecwid is the better fit when your existing website is the asset. If its articles, portfolio, and editing workflow still bring in buyers and help them choose, you only need to sell from those pages, and Ecwid adds a catalog, a category, a product card, or a Buy Now button to them. Our Ecwid review covers that embedded route and the hosted one.

Setka fits when the website is the work you want to replace. If you’re rebuilding the homepage, product presentation, and navigation anyway, keeping the old site keeps the job you meant to get rid of. Setka is our product. You bring the catalog and brand direction, Setka generates the whole store around them, and from then on you change it by describing the result, editing exact wording, previewing, and publishing. There is no theme code for you to maintain. Your guides can move into Setka’s built-in blog and link to the products they recommend; placing product cards inside a post is coming soon.

Ecwid gives you two ways to present the store

Ecwid documents adding commerce to an existing website, including a full catalog, a category, a product card, or a Buy Now button. The integration method depends on the website platform. You keep its content and editing workflow alongside Ecwid’s commerce settings.

Its Instant Site is a hosted, code-free website builder included in every plan. It has its own themes, sections, and editor. Custom domains, additional pages, and other capabilities depend on the plan.

DecisionEcwidSetka
Preserve an existing websiteAdd Ecwid commerce through the supported integrationSetka replaces the website; articles move into its built-in blog
Start without a websiteConfigure a hosted Instant SiteGenerate storefront pages from a brief and catalog
Change the presentationUse site/store design controls; deeper customization can use codeDescribe changes, edit copy directly, preview, and publish
Own the implementationDepends on the hosted or embedded approach and customizationSetka owns the storefront implementation; you direct and approve it

Ecwid’s customization guide covers built-in controls and code-level options. Code is not required for every change. The useful question is whether the presentation you want fits the editor or becomes a separate customization project.

Test a change that matters to your brand

Use a small homeware collection with real photos, dimensions, and a short account of how the pieces are made. Pick a task you will repeat: introduce a new collection, feature three pieces, and make the dimensions prominent on each product page.

If keeping your website is the goal, add the products to an actual article or collection page. Keep the connection specific: a guide to choosing a vase for a small dining table should lead to suitable pieces with their dimensions, rather than leave the reader to search the entire collection again. Check the route from that page to a product, cart, and checkout on a phone and desktop. Note which changes happen in the website editor and which happen in Ecwid; both need an owner.

If you are choosing a new store, compare Instant Site’s sections with the result you can direct in Setka. Give Setka the collection story and product facts, then ask for a revision such as “shorten the introduction and bring the dimensions closer to the product description.” Preview the page and mobile layout, then publish, place a real order through cart and checkout, and refund it before launch.

Then rehearse the next collection update. Replace a featured piece, revise its explanation, and check that the recommendation still fits the products available. You own those facts in either setup. In an embedded setup, you also own the article around the store and the website editor it lives in. In Setka, you direct the change and the platform implements it, and every change saves a storefront version you can return to if the update misses. The second collection update tells you more about a platform than the first design does.

Compare the plan your catalog actually needs

Ecwid’s pricing page and plan documentation, checked on 28 September 2026, list these USD prices and product limits:

PlanMonthly billingMonthly equivalent with annual billingProduct limit
Starter$5$510
Venture$35$29100
Business$65$492,500
Unlimited$149$119Unlimited

Taxes are excluded; billing country and app-store billing can change the price. Ecwid charges no platform transaction fee, while payment-provider charges remain separate. Its 2026 pricing update explains the changed Venture, Business, and Unlimited rates.

Product count is only one gate. For example, the current Instant Site documentation places custom domains on Venture and above. A store that needs a branded domain should not budget from the Starter price alone.

If you keep a website, add its subscription and upkeep to the Ecwid budget. If Instant Site’s sections already present the collection the way you want, Ecwid’s lower plan wins. If every new collection means paying for design or code work, that work becomes the larger cost, and it’s the cost Setka removes, because the store is built and changed inside the platform. Setka’s price doesn’t rise with your sales; Stripe’s processing fees apply as they would anywhere. See Setka’s current pricing.

Choose the workflow, then plan the move

Ecwid is the stronger choice when keeping an existing site is central to the decision, or when its hosted editor already gives you the control you want. Choose Setka when you want the store built for you and want to direct its changes without maintaining a theme.

Ecwid documents catalog export and separate order and customer exports on Venture and above. If you move to Setka, we run the migration for you. Before you move, list which pages stay, which get replaced, and which URLs customers already use, and give each important page a destination. Setka doesn’t set up redirects from old URLs yet. If customers or search traffic depend on those URLs, or a catalog, payment, or integration requirement is launch-critical, write to contact@getsetka.com with what you have before you move. Requests go straight to the people building Setka.

If you want to keep the website, plan that route with the embedded-commerce guide. If the storefront itself needs rebuilding, start with Setka and bring the collection brief above.