Most stack posts about e-commerce stop at the checkout, as if the sale were the end of the story.

It is roughly the middle. Getting the first order is expensive; getting the second is where a store becomes a business. So this stack covers both halves.

Six tools, in order.

1. Mobbin — copy the conventions that make people comfortable

Nowhere punishes originality like a checkout.

Shoppers have been trained by thousands of stores on where the cart lives, what a shipping estimate looks like and when the price becomes final. Meeting that expectation exactly is worth more than any clever idea you have about it.

2. Figma — design the product page, then the rest

The product page is the store. Everything else is navigation.

Design it properly: gallery, variants, price, availability, delivery, returns, and what happens when an option is out of stock. Get that one page right and the rest of the site is comparatively easy.

3. Shopify — do not build a cart

Tax, shipping rules, inventory, discount codes, fraud, refunds, and the fifty rules you will discover the week after launch.

All of it is solved and none of it is your product. Build a store on it, not a store like it — the custom cart is the single most common way a small team loses a quarter.

4. Stripe — the part that must not be interesting

Payments are a place to be thoroughly boring.

Support the methods your customers already use, keep the form short, and never surprise anyone with the final number. Most checkout abandonment is not a payments problem; it is a cost-revealed-too-late problem.

5. Klaviyo — the second purchase

This is the step most stacks leave out, and it is where the margin lives.

Acquiring a customer is the expensive part. Keeping them is a sequence of unglamorous, well-timed messages: the abandoned cart, the post-purchase check-in, the restock note, the one that arrives when they usually reorder.

Set those up before you spend more on ads.

6. Cloudflare — speed is a conversion feature

On a store, latency is money. A slow product image is a lost sale, measurably.

Serve images and pages from the edge, cache aggressively, and check performance on a mid-range phone on mobile data rather than on your laptop. That is the device the revenue is actually on.

The order is deliberate

Conventions before design. Design the product page before the site. Buy the commerce engine rather than building it. Make payments boring. Set up retention before you scale acquisition. Make it fast, because fast is worth money here in a way it is not everywhere.

Do those in that order and the store is mostly a question of what you sell.

Do I need a headless build or is Shopify enough?
For most stores, Shopify with a good theme is enough and gets you selling in days. Headless is worth it when the storefront is genuinely unusual or the content side is heavy — and it costs materially more to build and maintain.
Why Klaviyo instead of a general email tool?
Because it is wired to store events. Abandoned cart, post-purchase, restock and reorder timing depend on knowing what someone bought and when, which a generic newsletter tool does not know.
Does Shopify handle payments without Stripe?
Shopify Payments covers many stores on its own. Stripe is in this stack for the cases it does not cover — separate subscription billing, marketplace payouts, or selling in regions and methods you need finer control over.
How much does speed really affect sales?
Enough to treat it as a feature rather than a chore. Slower pages measurably reduce conversion on mobile, which is where most store traffic now arrives, so test on a mid-range phone rather than a desktop.