Embed commerce in your existing website when the site already explains your products well, you can maintain it comfortably, and all it lacks is a way to buy. Build a complete store when there is no site worth keeping, or when browsing, product pages, and checkout need to be designed together. The cost follows the same line: an embed is cheap when the surrounding site is finished and expensive when you still have to build that site.
A coffee roaster with useful brewing guides and a well-designed website may only need to put six coffees up for sale. Those guides already help people choose a coffee and learn how to brew it, so they are part of the buying journey and worth keeping. A new homeware brand with a spreadsheet of products is in a different position. Both need checkout. Only the homeware brand also needs collections, product pages, navigation, and a cart, and embedding checkout into a blank page doesn’t build any of them.
A complete store can start from a template you configure or be generated for you. Setka is our product, and it takes the second approach: you provide a brief and your catalog, Setka builds the store, and you direct changes to it from there.
The work each approach leaves you with
| Decision | Embed commerce in an existing site | Build a complete store in Setka |
|---|---|---|
| Starting point | Pages and a website you want to retain | Products, brand direction, and a brief for the store |
| Presentation | Your existing website plus the commerce service’s embedded elements | Generated homepage, collections, product pages, navigation, and cart |
| Changes | Coordinate changes to the host website and the embedded selling experience | Describe changes, edit wording, preview, and publish inside Setka |
| Ongoing responsibility | Maintain the website and configure the commerce service | Direct the store while Setka owns its storefront implementation |
| Best reason to choose it | Preserve a website that already works for your business | Build and change the store without maintaining a theme-code layer |
Before choosing an embed, find out where three things live: the pages, the product facts, and the cart. They may have different owners. Some services supply catalog displays as well as checkout; Snipcart, for example, reads product definitions from your website. Ask where a price or description is maintained and how it reaches every place a buyer sees it. Keeping your website shouldn’t leave you guessing which copy of a product is correct.
Shoprocket is one example of an embedded commerce service. It also offers hosted storefronts, so the same vendor can support both approaches. These official pages were checked on 28 September 2026. Our Shoprocket comparison covers that choice in more detail.
Run one real product through both
Take a real product with its real photos, description, price, and shipping needs, and walk through four tasks:
- Find it from the homepage on a phone.
- Learn enough about it to buy it.
- Add it to the cart and pay: in the provider’s test mode where one exists, or with a real order you refund before launch, which is how you test checkout in Setka.
- Change how it’s presented, and note what else needs updating.
Make the last task two changes. Suppose a homeware shop moves a seasonal collection into the main navigation and adds care information beside its lead product. A week later that product sells out, so the shop features a different one and rewrites the collection’s introduction to match what’s still available. For each change, write down which website pages, catalog fields, and cart settings needed attention, and who handled each. Then check the result on a phone and a larger screen, and confirm the facts match from the collection introduction through the product page to the cart.
If you can make both changes in tools you already know, keeping the website has a practical advantage. If routine changes need help you no longer want to depend on, that is the case for a complete store.
In Setka, both changes happen in one place. Open the page, describe what should change, edit exact wording where you know it, and preview the new version of the store before you publish it. The product, its stock, and the cart are in the same platform as the pages, so there is no second system to update. Every version is saved, and you can restore an earlier version of the whole store.
The full cost of each route
Embedding can preserve a website you have already paid to build. The bill is its ongoing subscription or hosting, the commerce subscription, payment processing, and any help needed to keep the two connected.
For a new store, add the work of building the surrounding website before you compare subscription prices. That is where Setka usually costs much less than commissioning a website and adding commerce to it. The store is built into the platform, so design and build never arrive as a separate bill, and Setka’s price doesn’t rise with your sales. See current pricing. You still prepare accurate product information, approve the design and copy, and configure shipping and taxes.
A cheap commerce add-on is a good deal when the site around it is finished. When you still need someone to design and build that site, its price answers only a small part of the cost question.
Which to choose
Keep your current website if its design and content are already right, the commerce service supports the buying journey you need, and you’re happy maintaining both.
Choose Setka if the store itself needs to be built or substantially reworked and you want to direct how it looks without maintaining a theme. If a catalog, payment, or integration requirement decides your launch, tell us at contact@getsetka.com before committing. Requests go straight to the people building Setka.
Moving a whole store is a bigger job than embedding a checkout. If you decide to move, list the product data, URLs, customer records, order history, and integrations first, and get a specific answer about each. If you’re moving to Setka, send that list to contact@getsetka.com: we’ll go through it item by item and run the migration for you. Redirects from old URLs are not in Setka yet.
If building the store around your products is the work you want handled, start a store in Setka. Give it a brief with a buyer, a collection, and a buying priority, for example: “A homeware store for people furnishing a small kitchen. Lead with everyday bowls, group products by use, and make dimensions and care instructions easy to find.” Then review the result with your own products. Our store brief guide helps you prepare the details.