For a working content site that needs shopping, we recommend Ecwid as the starting choice: it can place a full catalog, category, or individual product inside pages you already own. For a new product business choosing Shopify for its retail tools, channels, or integrations, the Shopify Online Store puts the storefront in that same system.
Those are starting recommendations, not exclusive capabilities. Ecwid can host your website through Instant Site. Shopify can sell on an existing website through Buy Button. The decision is which part of your web presence you want the commerce platform to own—and who will maintain everything outside it.
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 an existing experience. Rebuilding the website would create work that is unrelated to the immediate selling goal.
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, subject to the host accepting the relevant plugin or embed method. Products, orders, and inventory are managed in Ecwid while the existing site remains the place for recipes and editorial content.
That makes Ecwid a sensible first candidate for this teacher. A catalog can give customers one place to browse the eight products, while a product card or button can appear beside a relevant recipe. A lesson on folding a delicate batter could explain why a particular spatula suits the task, then put that product within reach. The reader should not have to leave the explanation and hunt through an unrelated catalog to find it.
The teaching is part of the shopping experience. Someone buying a utensil as a gift may need help choosing its size or use; an experienced cook buying the same gift may want precise material and care details. Buying intent does not tell you how much a person knows. Keep enough guidance beside the product for both to make a considered choice.
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 do not have to rebuild an existing site as a Shopify Online Store to sell Shopify products from it.
Buy Button makes particular sense if you already manage products in Shopify and want to sell them from the recipe site too. Choosing Ecwid just to preserve those pages would overlook a channel already available in Shopify. An embedded purchase path still differs from 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.
The ownership map for 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 preserves your website, including its responsibilities. You still need to check how the product fits beside the article, whether the mobile navigation remains usable, and what happens as the customer moves from content into checkout.
If the teacher changes a spoon’s price, the commerce record is the source of truth. Any price typed separately into recipe copy is still editorial content that someone must update. Central catalog management cannot correct every sentence you wrote elsewhere on the site.
Scenario two: a new brand with no website to preserve
Now imagine a homeware brand launching 24 products. It wants collections, product pages, brand stories, clear delivery information, and space for future launches. There is no existing site worth retaining.
Here, adding an embed to a new third-party website introduces another system by choice. It may still make sense if the brand strongly prefers that website builder, but “we need a site to put the store on” is not a requirement of Ecwid.
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 permits a custom domain, making it the first plausible plan for this example. Content can change that decision: the Instant Site table allows three additional pages on Venture, while its blog is available on Business and Unlimited. A brand planning regular editorial stories should budget for that distinction. See Ecwid’s plan table.
Shopify’s Online Store provides the full hosted-store path on Basic or higher. The brand chooses a theme and configures its presentation, then adds extensions only where required. Shopify’s main plans document unlimited products, but a 24-product brand should care more about fit than unused 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 does not, by itself, make Shopify the better answer. Neither platform’s catalog capacity decides how well the products will be presented.
Test a change, not just an attractive starting page
For the cooking teacher, rehearse adding a ninth product and featuring it in an existing recipe. Check which work happens in the commerce admin and which happens in the website editor. Then change the featured utensil: does the recipe still explain the one now offered, and are any separately written price or delivery promises still accurate? Walk through the purchase path on mobile and desktop, from the lesson to the product, cart, and checkout.
For the homeware brand, rehearse a collection launch: add the products, change the homepage emphasis, check stock and delivery information, and review checkout. If a newsletter introduces a collection for small spaces, its destination should explain the relevant sizes and uses. Repeat the exercise for the next collection. Notice whether an ordinary launch stays in the editor or becomes a handoff to someone who owns custom code. A theme or app earns its place when it serves that job; having more available does not settle who will keep the result working.
In embedded mode, the existing website’s subscription stays on the bill. In hosted mode, the plan, domain, and any extensions or implementation help are the bill. 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.
When you want the platform to build the storefront
Setka is our product. We recommend it for the second scenario when the homeware brand wants to explain its products well without assembling the storefront from themes and sections. You do not need a finished layout in mind. Give Setka the brand direction, customer context, and catalog, then direct the resulting store. The useful comparison is how you will introduce the next collection and refine its presentation, as well as how the first homepage looks.
Setka generates the store’s presentation, lets you describe page changes and edit exact copy, and provides preview and publishing. You direct the outcome without maintaining a generated theme codebase. Setka includes a built-in blog, so the brand stories live in the same store as the collections. The merchant still supplies accurate products, decides commercial policies, configures the supported selling setup, and approves the store.
That is a different choice from keeping the cooking teacher’s existing site and embedding shopping. Setka is not a drop-in commerce widget. If preserving a working content site is the priority, Ecwid or Shopify Buy Button directly addresses that requirement.
For a new brand taking that route, start a store in Setka with one representative collection and the story behind it. Use the preview to review the homepage, collection, and product pages together. The question is whether they explain the products the way you want to sell them.