Start with the website you already have
A good existing website is an asset. If its pages explain your work, its navigation makes sense, and you can maintain it comfortably, replacing it just to accept orders may create unnecessary work. An embedded commerce service can add the selling layer.
If you are starting with a blank page, embedding checkout does not answer the rest of the store-building question. Someone still needs to create the pages, organize the products, and make the buying journey work on mobile.
For example, a coffee roaster with useful brewing guides and a well-designed website may only need to add six bags of coffee for sale. A new homeware brand with a spreadsheet of products still needs collections, product pages, navigation, and a cart. Both need checkout; only the second needs the whole storefront built. The roaster’s brewing guides may also be part of the buying journey: they help someone choose a coffee and understand how to use it. Keep that useful work in the decision, alongside the design.
A complete store can start from a template you configure or from a generated storefront. Setka is our product, and takes the second approach: you provide the brief and catalog, then direct changes to the store it builds. The table below compares that workflow with keeping your existing site.
Compare 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, locate three things: the pages, the product facts, and the cart. They may have different owners. A service can 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 should not 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. Evaluate the channel you would actually use; our Shoprocket comparison explains the choice in more detail.
Try one product before choosing a platform
Use a real product with its real photos, description, price, and shipping needs. Walk through four tasks:
- Find it from the homepage on a phone.
- Understand the product well enough 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 its presentation and check what needs updating elsewhere.
Make the last task a two-change exercise. Suppose a homeware shop first moves a seasonal collection into the main navigation and adds care information beside the lead product. Then, a week later, that product sells out: change the lead product and update the collection’s introduction so it still describes what is available. Record which website pages, catalog fields, and cart settings need attention, and who handles each one.
For both changes, check the path a buyer would follow on a phone and a larger screen. Someone choosing a gift may need dimensions, suitability, and delivery information; a knowledgeable buyer may want material and care details. Those needs can overlap. Keep the facts consistent from the explanation through the product page and cart. A coherent appearance helps the journey, but does not substitute for truthful descriptions, photos, and policies.
If you can repeat both changes in tools you already know, keeping the website has a practical advantage. If routine changes require help you no longer want to depend on, the store-building workflow deserves more weight.
For Setka, review the generated pages, request a specific change, and preview the resulting storefront version. Storefront versions can be restored as a whole.
Compare the full cost of the decision
Embedding may preserve a website you have already paid to build. Include its ongoing subscription or hosting, the commerce subscription, payment processing, and any help needed to maintain the connection.
For a new store, include the work needed to build the surrounding website before comparing subscription prices. That is where Setka usually costs much less than commissioning a website and adding commerce to it: in Setka the store is built into the platform, so the design and build work never appears as a separate bill. See current pricing. You still prepare accurate product information, approve the design and copy, and configure shipping and taxes.
A cheap commerce add-on can be a good deal when the surrounding site is finished. It answers much less of the cost question when you still need someone to design and build that site.
Choose the approach that preserves useful work
Keep your current website if its design and content are already right, the commerce service supports your required buying journey, and maintaining both is acceptable.
Choose Setka if the store itself needs to be built or substantially reworked, and you want to direct its appearance without maintaining a theme. If a catalog, payment, or integration requirement decides your launch, tell us at [email protected] before committing: requests go straight to the people building Setka.
An embedded checkout is not the same as moving an entire store. If you decide to move, inventory the product data, URLs, customer records, order history, and integrations first. Get a specific answer about each transfer. If you move to Setka, send that inventory to [email protected]: 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 surrounding store is the work you want help with, 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.