ENATIV Logo
ENATIV
Back
© 2026 ENATIV
ProjectsServicesKnowledge hubContact
contact@enativ.pl
  1. Knowledge hub
  2. ›
  3. E-commerce
  4. ›
  5. Shopify

Shopify

A ready-made store platform for a standard buying process and a fast launch, also as a headless back end.

E-commerceUsing since 2025 · Featured project: The Travelling Cows

Category
E-commerce
Using since
2025
Featured project
The Travelling Cows

In practice

I recommend Shopify when a store has a standard buying process and has to launch quickly, with no engine to maintain. In The Travelling Cows I used it as a headless back end for a store of physical products, with cart and checkout on Shopify's side. When the rules outgrow it, I stop recommending it.

What is Shopify?

Shopify is a ready-made store platform. The catalogue, cart, checkout and order admin work out of the box, and themes and apps extend them. A simple store can go live after configuration alone, with no code. Shopify runs the servers and platform updates.

You can also use only the back end instead of a theme. A headless front uses two APIs: the Storefront API serves the catalogue and the cart and hands the customer off to checkout, and the Customer Account API covers sign-in and the customer's orders. The front can sit in any stack, Next.js included. You enable access through a sales channel in the Shopify admin: Headless if you host the front yourself, Hydrogen if you use Hydrogen and Oxygen hosting.

Headless API
Storefront API, GraphQL
Storefront
Hydrogen or your own stack

How I work with Shopify

I start by checking whether a theme and apps cover what the store needs. If they do, I add no headless front, because one costs more to build and run than a theme. I don't go headless because other stores do. I go headless when I can name one specific thing a theme cannot do.

  1. Platform boundary

    I settle what Shopify does itself and what has to be built around it. The catalogue, cart and checkout stay on its side, and a custom front reads data through the Storefront API.

  2. Catalogue refresh

    Shopify webhooks refresh the catalogue on the front end. That's how the store in The Travelling Cows is built.

  3. Delivery and orders

    I connect delivery with InPost: the customer picks a parcel locker on the map or a courier, and Shopify orders land in the CMS and in the client account, as in The Travelling Cows.

When it fits, and when it doesn't

A ready-made platform wins when the store's own logic is not your edge.

A good fit when

  • A standard buying process: cart and checkout with no unusual rules.
  • A launch in weeks, without building and hosting an engine of your own.
  • A team where nobody wants to maintain a server or a database.
  • A store of physical products inside a larger platform, as in The Travelling Cows.

Not a fit when

  • Many sellers on one storefront, with commissions and split payments.
  • Price lists or checkout rules that an app cannot handle without workarounds.
  • The code and customer data have to stay on your infrastructure.
  • Nobody on your side will look after a headless front once it is live.

For rules of your own I look at Medusa.js, whose entry holds the comparison. For many sellers I start from the multi-vendor marketplace entry.

Frequently asked questions

No. A theme and apps cover most stores, and I add a headless front only when a theme cannot meet the requirements. Such a front takes more work than a theme, and someone has to keep developing it after launch. So before deciding I check whether the difference pays off.
Shopify maintains the platform, meaning the servers and engine updates. The shop content and the choice of apps stay on your side. A headless front adds code of your own that somebody has to keep updated, so I settle with you up front who takes it on. Theme and app updates still need watching, so ready-made does not mean hands-off.
In The Travelling Cows the customer chooses a parcel locker on the InPost map or a courier, and the Shopify order lands in the CMS and in the client account. The integration itself is covered in the InPost entry.
When the requirements can only be met with workarounds: one app stacked on another, or sellers settled by hand. Then I weigh the work on those workarounds against building on an engine such as Medusa.js. I prefer to plan a migration early rather than run it under pressure.

On this page

  • In practice
  • What is Shopify?
  • How I work with Shopify
  • When it fits, and when it doesn't
  • Frequently asked questions

Related topics

  • Shopify
  • Medusa.js
  • Headless commerce
  • Stripe
  • InPost
  • Next.js

Related services

  • E-CommerceHeadless Shopify, Medusa.js, and custom storefronts with Stripe.

Choosing a platform for your store?

Tell me what you sell, how delivery works and who will run the store. I will say whether a Shopify theme is enough or whether you need a custom front end or an engine.

Describe your projectSee The Travelling Cows