When Shopify, when custom — and how to choose for your online store

Everyone who wants to launch an online store faces the same question at the start: Shopify or custom?

The question is actually framed wrong. Shopify isn't "cheap off-the-shelf software" and custom isn't "expensive and advanced". Both can be the right choice; both can be the wrong choice. It all depends on who owns the catalog, how standard the requirements are, and how the store fits into something larger.

In our portfolio we have all three variants in use. Here's why each one chose what it chose.

BeeBike: Shopify + custom sync

BeeBike sells bicycles through the site. BeeBike doesn't make the catalog — the supplier sends an XML feed with all products, prices, and stock. Payment, cart, checkout are standard e-commerce flows. Branding matters but fits into a custom Shopify theme.

For BeeBike, Shopify is the right choice because it covers 95% of the work. A customer arrives, browses products, adds to cart, pays by card, gets confirmation — Shopify does all of that out of the box. We only had to solve the 5% Shopify doesn't do: how to keep the catalog always aligned with what the supplier actually has in stock.

The solution is a background service that pulls the supplier's XML feed, detects changes, and pushes updates to Shopify only when something actually changed. It's not competition for Shopify — it's an extension.

Cost: relatively low. Time from contract to launch: short. Maintenance: Shopify mostly does the job, we check the sync service occasionally.

Sushi XO: custom + POS integration

Sushi XO sells sushi for delivery and pickup. The restaurant already has a POS system they use for the kitchen. They wanted a loyalty program the POS doesn't support. They wanted SMS authentication instead of passwords. They wanted branding that isn't a SaaS template — typography, colors, rhythm that match their restaurant.

Shopify wouldn't have worked well for Sushi XO. Shopify doesn't integrate with an arbitrary POS system. Shopify has no loyalty module that plugs into a POS that doesn't support loyalty. Shopify can be good, but it can't respond to the specific ordering flows Sushi XO operators wanted.

A custom solution was the right choice because:

• The central logic was atypical (loyalty that exists alongside a POS that doesn't support it)
• The integration was specific (that particular POS, not some standard)
• The branding had to be full, not a theme on a template

Cost: higher than a Shopify solution. Time: longer. But the system matched the actual business exactly, and the restaurant grew from one location to five on the same system.

Indigo Luxor: custom inside a larger product

Indigo Luxor is a platform for digital collecting with sticker scanning, quizzes, prize draws, and Discord integration. The store is just one part of that ecosystem — ordering products from the same user account used for scanning and the quiz.

Shopify wasn't even considered here. The reason: Shopify can't be embedded inside another application with its own user management system. A user on Indigo Luxor has one login that gives them access to the album, the quiz, prizes, and the store. Shopify would split that login in two.

A custom solution was the only thing that could keep the product unified.

How to choose

From three examples a simple heuristic falls out.

Shopify does the job when:

• The catalog is yours (it doesn't come from an external source)
• Payment is standard (card, maybe some wallet)
• Shipping is conventional
• Branding can fit a theme
• The store is a standalone product, not part of a larger application

Hybrid (Shopify + custom service) works when:

• Shopify covers most of it, but there's one specific piece that doesn't fit (e.g. a catalog from an external feed)
• You have the resources to maintain a small service alongside Shopify

Custom is the right choice when:

• Integrations are specific (a non-standard POS, ERP, bank)
• Loyalty / authentication / check-out are seriously atypical
• The store is part of a larger product with shared user accounts
• Branding has to be full

What we most commonly see go wrong

The most common mistake: Shopify is chosen because it's "cheaper and faster to launch", and after a few months it becomes clear that key specifics of the business require workarounds that pile up into complexity. Then a parallel system gets built alongside Shopify, and in the end Shopify becomes just part of the problem, not part of the solution.

The second mistake, rarer: custom is chosen for a job that's standard, because "we want our own control". After a year, a system Shopify would run for 10% of the cost runs for 100% of the cost and 100% of the maintenance time.

The right choice isn't "cheap vs expensive". The right choice is "where is your uniqueness". If it's in the product, custom. If it's in the marketing and operations around standard sales, Shopify.