Keep Foxy if your website or CMS already gives you the product pages you want and what you need is a configurable cart and checkout. Choose Setka when building and changing those pages is the problem. Swapping the checkout won’t finish the store for you; moving to a platform that builds the store will.

Setka is our product. We recommend it when you’d rather hand over your catalog and brand direction and then steer the generated store than keep a website, a theme, and a Foxy integration running. It is not a drop-in FoxyCart replacement for an existing website: it replaces the website too.

Foxy leaves product presentation with your website

Foxy’s introduction describes a hosted cart and checkout used with an existing website or platform. Its product-management guide explains that standard products live on your website or in your preferred CMS, with product information passed through add-to-cart links or forms. Digital products have a separate workflow in Foxy.

That separation is useful when your content system or custom product presentation is worth preserving. Foxy also documents using its checkout without its cart, so an existing cart can hand off to Foxy’s checkout, and its features include deep template and integration customization.

DecisionFoxy CommerceSetka
Product pagesBuilt in your website or preferred CMSGenerated from the brief and catalog inside Setka
Cart and checkoutHosted commerce services integrated with your siteConnected to the generated storefront inside the platform
CustomizationPlan-dependent templates, HTML/CSS/JavaScript, and integrationsDescribe storefront changes, edit copy, preview, and publish
Ongoing ownershipYour team owns the surrounding website and integrationSetka owns storefront implementation; you direct the result

What moves into the platform with Setka

With Foxy, the catalog, the product pages, and the code that passes products to the cart all live on your side. Setka holds the catalog itself and generates the homepage, collections, product pages, navigation, and cart from it and from your brief. Checkout runs through your own Stripe account; a paid order updates inventory, sends the customer a confirmation, and notifies you.

Later changes stay in the same place. Open a page, describe what should change, edit exact wording where it matters, preview, and publish. Every change saves a storefront-wide version you can return to. You still supply accurate product facts and decide how the store presents the business.

A quick test: write down your next store change. A new collection on the homepage, a clearer product layout, or different wording beside the price are changes you direct inside Setka without touching code. A custom form, a subscription renewal, or a customer login is different: trace how it connects to Foxy today, because that dependency needs its own replacement plan.

Imagine a coffee business that publishes brewing guides in its CMS, sells through Foxy, and lets customers manage recurring orders in Foxy’s portal. Rewriting a guide is a content task. Changing what a subscription contains or how it renews touches billing and customer communication too. Moving only the product pages would leave that second job unowned, and Setka doesn’t run subscriptions yet, so that business should keep Foxy for now or talk to us first.

Read Foxy’s billing terms together

Foxy’s pricing page, checked on 28 September 2026, shows these USD monthly equivalents with annual billing. They are not month-to-month quotes.

PlanAnnual-billing monthly equivalentIncluded transactionsCharge per additional transaction
Starter$30100$0.35
Growth$65500$0.25
Advanced$3001,000$0.075
EnterpriseFrom $2,25010,000$0.05

The page also lists a Foxy transaction fee on Starter, Growth, and Advanced: 1%, with a $0.05 minimum and respective maximums of $0.35, $0.25, and $0.075. That fee is separate from the charge for exceeding the included transactions. User and automation allowances can add further charges, and gateway and processor fees come on top.

So a Foxy bill has five lines: subscription, transactions above the allowance, the capped transaction fee, extra users or automation runs, and processing. On the Starter plan, 150 transactions exceed the included 100 by 50; at $0.35 each, the overage alone is $17.50, before the 1% fee and processing. Monthly billing is shown in a separate view on the same page.

All of that sits on top of a website you build, host, and keep integrated. If you’d be building that website for the store, Setka usually costs less in total: the storefront is part of the platform, so the site build, its hosting, and the integration work never appear as separate costs. Setka’s price doesn’t rise with your sales; Stripe’s processing fees still apply. See current pricing.

Check what your customers do in Foxy before you move

Foxy documents recurring billing, a customer portal, digital products, and, from its Growth plan, multi-currency selling. List what your customers actually do: download a file, view receipts, change a payment method, manage a subscription, pay in their own currency.

Setka doesn’t have customer accounts, subscriptions, or digital products yet, and each store uses one currency for now. If your customers depend on any of these, tell us what they do at contact@getsetka.com: requests go straight to the people building Setka.

Foxy’s pricing page lists customer and subscription migration on Advanced and Enterprise. That names a service; it doesn’t promise that every source system, catalog, URL, or design transfers. If you move to Setka, we run the migration for you: tell us what you have, and we’ll work out the move with you.

If your current website and Foxy integration already do the job, keep that work. The embedded-commerce guide helps separate a checkout change from a store rebuild.

If you want a branded store without commissioning and maintaining its pages, start your store in Setka. Bring your catalog and a brief for the presentation.