If you have a content site that works and want to start selling from it, start with Ecwid: it can place a full catalog, a category, or a single product inside pages you already own. If your products already live in Shopify, its Buy Button does the same job. If you are launching a new product brand, both platforms can host the whole store. Ecwid’s Instant Site fits when its page allowances and plan gates cover your content; Shopify fits when you need its retail tools, channels, or integrations.
Either way, a new store on Ecwid or Shopify starts from a theme you then adapt. Setka is our product, and it takes the other route: it builds the store from your brief and catalog. We cover where that fits at the end. Our Ecwid review goes deeper on both Ecwid routes, and Ecwid alternatives covers the options if neither fits.
Scenario one: a useful content site that should stay
Imagine a cooking teacher with an established website. It contains recipes, class information, and a newsletter archive. The teacher wants to sell eight kitchen products without moving those pages or replacing the site’s editor.
The job is to add shopping to something that already works. Rebuilding the website would create work that has nothing to do with selling eight products.
Ecwid documents embedding a full catalog, category, product card, or Buy Now button on an existing site. It supports common site platforms and custom sites, as long as the host accepts the relevant plugin or embed method. Products, orders, and inventory are managed in Ecwid while the existing site stays the place for recipes and editorial content.
That makes Ecwid the first candidate for this teacher. A catalog gives customers one place to browse the eight products, and a product card or button can sit beside the recipe that uses it. A lesson on folding a delicate batter can explain why a particular spatula suits the job and put that spatula within reach, so the reader never has to leave the lesson to hunt for it.
Shopify’s Buy Button sales channel also supplies embed code for non-Shopify websites and blogs. Its documentation says the channel is included in all Shopify subscription plans. You don’t have to rebuild an existing site as a Shopify Online Store to sell Shopify products from it.
Buy Button makes most sense if you already manage products in Shopify and want to sell them from the recipe site too. Choosing Ecwid just to keep those pages would ignore a channel you already pay for. An embedded purchase path is still not the full Shopify theme experience. Shopify also warns against adding Buy Buttons to its own Online Store or blog because they can cause checkout problems; those surfaces have their own selling tools.
Who owns what on an existing site
| Responsibility | Ecwid embedded | Shopify Buy Button |
|---|---|---|
| Recipes, navigation, and general pages | Existing website and its editor | Existing website and its editor |
| Product records and order administration | Ecwid | Shopify |
| Shopping presentation on the host page | Ecwid integration plus host-page layout | Buy Button embed plus host-page layout |
| Checkout configuration | Ecwid commerce settings and chosen payment provider | Shopify commerce and payment settings |
| Site maintenance | Website owner or existing provider | Website owner or existing provider |
| End-to-end purchase review | Merchant checks the combined experience | Merchant checks the combined experience |
An embed keeps your website, and its responsibilities with it. You still check how the product sits beside the article, whether the mobile navigation still works, and what happens as the customer moves from content into checkout.
If the teacher changes a spoon’s price, the commerce record updates everywhere the embed appears. A price typed into recipe copy does not. Someone has to find and fix every sentence written outside the catalog.
Scenario two: a new brand with no website to keep
Now imagine a homeware brand launching 24 products. It wants collections, product pages, brand stories, clear delivery information, and room for future launches. There is no existing site worth keeping.
Here, building a site in a separate website builder and embedding a store in it adds a system you don’t need. It can still make sense if the brand strongly prefers that builder, but Ecwid doesn’t require a separate site to put the store on.
Ecwid Instant Site is a hosted, code-free website builder included in every plan, with hosting, maintenance, and a free subdomain. Merchants assemble pages and sections in its editor. Additional pages, a custom domain, and other capabilities depend on the plan. Custom domains require Venture or above.
The brand’s 24 products exceed Starter’s documented ten-product allowance. Venture covers up to 100 products and allows a custom domain, so it is the first realistic plan here. Content can change that: the Instant Site table allows three additional pages on Venture, and the blog is available only on Business and Unlimited. A brand that plans to publish stories regularly needs Business. See Ecwid’s plan table.
Shopify’s Online Store provides the full hosted-store path on Basic or higher. The brand chooses a theme, configures its presentation, and adds extensions only where required. Shopify’s main plans document unlimited products, which a 24-product brand won’t use; fit matters more than capacity.
| Responsibility | Ecwid Instant Site | Shopify Online Store |
|---|---|---|
| Hosted storefront | Ecwid | Shopify |
| Routine visual work | Instant Site editor, sections, and themes | Shopify theme editor and selected theme |
| Catalog and orders | Ecwid admin | Shopify admin |
| Deeper customization | Available code and developer extension paths | Theme code, apps, and developer extension paths |
| Product and policy accuracy | Merchant | Merchant |
| Approval after a change | Merchant reviews the customer journey | Merchant reviews the customer journey |
For the 24-product brand, Instant Site is a credible full-store choice when its page structure covers the brand story and buying information. Shopify earns the preference when the brand also wants its particular commerce tools or theme choices. Starting from zero doesn’t by itself make Shopify the better answer, and neither platform’s catalog capacity decides how well the products will be presented.
The second change tells you more than the first page
Both platforms can produce an attractive first page. What separates them is the routine change after launch.
For the cooking teacher, that change is adding a ninth product and featuring it in an existing recipe. Some of the work happens in the commerce admin and some in the website editor. When the featured utensil later changes, the recipe has to describe the new one, and any price or delivery promise typed into the page has to be corrected by hand.
For the homeware brand, it is the next collection launch: add the products, change the homepage emphasis, and make sure the newsletter’s link lands on a page that explains the sizes and uses that matter for, say, small spaces. On either platform, that is theme work. If the launch fits what the theme’s editor allows, the work stays in the editor. If it doesn’t, it becomes an app or a handoff to whoever owns the custom code. A larger theme and app catalog gives you more options; it doesn’t decide who keeps the result working.
In embedded mode, the existing website’s subscription stays on the bill. In hosted mode, the bill is the plan, domain, and any extensions or implementation help. Ecwid advertises zero platform transaction fees, while payment-provider fees remain separate; Shopify’s payment and third-party transaction charges depend on the plan and payment arrangement. Our Shopify pricing guide adds up the plan, theme, apps, and payment fees for a first year.
When you want the platform to build the store
For the homeware brand, we recommend Setka when the problem is the theme work above: presenting 24 products and their stories well without assembling the store from themes and sections, then reworking them for every launch.
You don’t need a finished layout in mind. Give Setka the brand direction, the customers you’re selling to, and the catalog. Setka builds the store inside its e-commerce platform: homepage, collections, product pages, navigation, and cart. Brand stories go in the built-in blog, in the same store as the collections. For the next launch, open a page, describe what should change and where, edit exact wording directly, preview the new version, and publish it. Every version is saved, so you can return to an earlier one. There is no theme code to maintain and no app to keep compatible. Setka’s price doesn’t rise with your sales; Stripe’s processing fees still apply. See current pricing.
You still supply accurate product information, set prices and policies, configure shipping and payments, and approve what gets published.
Setka doesn’t embed in an existing website. For the cooking teacher, keeping the site is the whole point, so Ecwid or Shopify Buy Button is the right answer.
For a new brand, start a store in Setka with one representative collection and the story behind it. Review the homepage, collection, and product pages together in the preview, and judge whether they sell the products the way you would.