DEV Community

Cover image for Headless Shopify for a Small Ceramics Shop: Overkill or the Cheaper Option?
Artur Pokładek
Artur Pokładek

Posted on AI-assisted

Headless Shopify for a Small Ceramics Shop: Overkill or the Cheaper Option?

We just launched a headless Shopify store for Lady Blue, a small brand selling hand-painted Bolesławiec ceramics. It took us about four weeks. One of the things behind that choice was a parcel locker picker, which inside Shopify would have meant a bigger plan.

The frontend is our own Next.js app, and the products and the checkout stay in Shopify. If you want to click around before reading, the store is live at ladyblue.pl.

Shopify's own docs warn you off

Shopify's docs are pretty direct about it. The About headless commerce page says: "A headless storefront costs more to build and run than a theme."

The same page asks you to make sure the merchant "accepts the added cost and complexity" and "has developers to maintain the storefront after launch." Fair enough. With a theme, the cart and the apps are somebody else's job.

Why we went headless anyway

Lady Blue needed a look of its own, and we couldn't get that out of a theme.

Page speed mattered too, though I have no measurements to show for it yet.

And there were the fees. A lot of what this shop needed sat behind paid apps or a higher Shopify plan, and each of those is a recurring cost.

Where does the customer pick a locker?

Lady Blue ships with InPost parcel lockers. The customer has to choose one somewhere before paying.

The official InPost app has a Polish listing, and it asks for the Shopify Advanced plan or active "Carrier-Calculated Shipping". Its interactive locker map is listed as available only for Shopify Plus.

Shopify's plans page (prices in USD) puts Advanced at $399 a month with monthly billing. Plus starts at $2,300 a month. Adding your own picker to the checkout's shipping step needs Plus as well, because checkout UI extensions for the information, shipping and payment steps "are available only to stores on a Shopify Plus plan."

Third-party InPost apps exist too. This one costs $19 a month, and its listing says "Carrier Calculated Shipping is required for the app to work (unavailable on the Basic Shopify plan)."

So we built the picker ourselves. It works in the cart.

Jobs a theme would have done for us

The first version of our cart let you add more units than were in stock. Every piece in this shop is hand-painted. We fixed it, and add-to-cart now stops once you have added all the units available in stock.

Themes add to the cart through Shopify's Cart AJAX API, and when the requested quantity is too high, "the cart will instead add the maximum available quantity."

Headless carts go through the Storefront API. Cart mutations report stock problems in a warnings field, and ProductVariant.quantityAvailable gives you the number.

Apps are the bigger gap. Shopify's docs for Hydrogen, its own headless framework, say apps often add app blocks or embeds to the theme, and a Hydrogen storefront "doesn't render them, because they're Liquid, which only an online store theme renders."

Our "build a set" wizard shows a whole set of ceramics on one table. It is our own feature, and in a Shopify theme it would be hard to do without a paid app.

We wrote no checkout code

Checkout and payments stayed on Shopify's side. The cart gives you a checkoutUrl, and per the cart docs it "redirects customers through Shopify's web checkout."

The Hydrogen go-live guide says the same thing shorter: "Checkout still runs on Shopify."

Products stay in Shopify too. The owner edits all descriptions and products in Shopify admin, in Polish, German and English. The store sells to Poland and the Netherlands.

Those translations reach the frontend through the Storefront API, where the @inContext directive accepts a language argument since API version 2022-04.

Everything else on the site, we change as part of the maintenance fee. Shopify's Hydrogen markets page notes that "your app's own interface text, such as button labels, still needs your app's translation system," and on this project that system is ours. So for anything outside the products, the owner has to come to us.

So, overkill or the cheaper option?

For Lady Blue, the locker picker would have needed a bigger plan, and the set builder would have been hard to do without a paid app. We built both, and the frontend is ours to look after.

Whether that works for another store depends on the project. I don't have a rule for it.

When a theme and free apps cover what a store needs, I think the theme is the cheaper option, and the warning from Shopify's docs applies in full.

The store is days old. I have no conversion or speed numbers yet, so I'm making no claims about results.

I'm after specifics here, like a plan fee or one app you did not want to pay for every month. If you have built a store for a small shop, headless or on a theme, what tipped the decision for you?

Top comments (7)

Collapse
 
friga profile image
Artur Pokładek •

Fair point. Support is its own line here: the owner pays a maintenance fee, and everything outside products and descriptions goes through us under it. I left the amount out on purpose, that's the client's business.

Agreed that a 12-month view with build, fee and app costs side by side is the honest comparison. For speed I'd rather wait for a few weeks of real traffic than post a Lighthouse score from launch day.

Collapse
 
rushdeploy profile image
Rishabh Mishra •

The locker picker is the clearest win here, since it avoids the $399 plan for one feature.
One edge I would watch is stock changing after the cart is built, since each piece is one of a kind.
I would recheck quantityAvailable just before you hand over the checkoutUrl, so a sold piece shows as sold instead of failing at checkout.

Collapse
 
friga profile image
Artur Pokładek •

Good catch. With inventory tracking on, Shopify's checkout still refuses a piece that sold in the meantime, so it won't oversell, but the customer finds out one step too late. A recheck right before handing over the checkoutUrl turns that into a "sold" label in the cart instead. Worth adding.

Collapse
 
alexshev profile image
Alex Shev •

For a small store, the headless decision should compare operating cost and change latency, not just storefront flexibility. I’d list the content workflows, preview and rollback path, checkout constraints, SEO migration risk, and who owns updates after launch. A simpler theme is often the cheaper architecture when the business needs frequent merchandising changes without developer intervention.

Collapse
 
friga profile image
Artur Pokładek •

Agreed, and change latency is the part clients actually feel. Here the owner edits products and descriptions herself in Shopify admin, so merchandising never waits for us. Layout changes do, and that's the trade we accepted.

Collapse
 
nilesharma0108 profile image
Nilesh Sharma •

The parcel-locker constraint makes the headless decision concrete, rather than relying on a generic speed claim. I’d compare the full recurring plan/app cost against the build and maintenance burden, then keep performance conclusions separate until field data is available. Are you planning to share a follow-up with measured speed and the longer-term maintenance costs?

Collapse
 
friga profile image
Artur Pokładek •

Maybe, once there's enough real traffic to say something honest about speed. A follow-up with field data and a year of upkeep would be more useful than launch-week numbers anyway.