Shopify | Shopify Plus
Custom theme architecture, private apps, checkout extensibility and app consolidation. The work that starts when the store is working and the stack around it is not.
In one paragraph
Custom theme architecture in Liquid with sections and blocks structured so a merchandiser can work without a developer, private and custom apps built on the Admin and Storefront APIs, checkout extensibility and Shopify Functions on Plus, app consolidation to remove the script-tag tax several installed apps impose on page speed, and integration with ERP, PIM and fulfilment systems. The distinction that matters: configuration is what the theme editor does, and engineering is everything the theme editor cannot.
What this is
Shopify is deliberately opinionated, and that is its strength: a brand can launch quickly and run without an engineer. The engineering work starts at the edges of those opinions, which is where a growing brand inevitably ends up.
Usually it arrives as one of three things. The theme has accumulated enough custom sections that nobody can safely change it. The store has twelve apps, four of which do overlapping jobs and all of which inject scripts. Or something outside Shopify, an ERP or a 3PL, needs to agree with it in real time.
What this page is not
This page is about building on Shopify. Moving to Shopify from another platform is a different job with different risks, and it has its own page.
What usually brings this in
The theme has been customised to the point where nobody will touch it.
Every change is quoted defensively, and the marketing team has stopped asking.
Twelve apps, each adding scripts to every page.
The store is slow, the subscription bill is significant, and several apps overlap.
Checkout needs behaviour Shopify does not offer out of the box.
Workarounds live in the theme, break on Shopify updates, and nobody is sure what is load-bearing.
Stock and orders have to agree with a system Shopify has never heard of.
Someone is exporting CSVs on a schedule, and the gap between exports is where the oversells happen.
What gets built
- Theme architecture a merchandiser can use
- Sections and blocks structured so layout changes are configuration rather than code. The test is whether your team can build a landing page without opening a ticket.
- Private and custom apps
- Built on the Admin and Storefront APIs, deployed under your own account, with the webhook and rate-limit handling that keeps them reliable rather than mostly reliable.
- Checkout extensibility on Plus
- Checkout UI extensions and Shopify Functions for discount, delivery and payment customisation, using the supported extension points so an update does not break the checkout.
- App consolidation
- Audit what each installed app actually does, replace the overlapping ones with purpose-built code where that is cheaper over two years, and measure the page weight before and after.
- Systems integration
- ERP, PIM, 3PL and subscription platforms, with reconciliation defined rather than hoped for.
Technologies
- Platform
- Shopify
- Shopify Plus
- Liquid
- Shopify Functions
- APIs
- Storefront API
- Admin API
- GraphQL
- Webhooks
- Frontend
- JavaScript
- TypeScript
- Hydrogen
- Next.js
- Integration
- ERP connectors
- 3PL
- Payment gateways
- Klaviyo
How delivery runs
Scope, in writing
What the work is, and what it explicitly is not. The second half is the one that protects both of us, and it is written before anything is quoted.
Architecture before code
The data model, the integration points and the failure modes, agreed on paper. Most of the expensive mistakes in commerce are made here and discovered six weeks later.
Build in reviewable slices
Work lands in increments you can see running, not in one drop at the end. You find out early if something is going the wrong way, which is when it is still cheap.
Test against the real thing
Production-shaped data, production-shaped traffic. A checkout that works on twelve test products tells you nothing about one carrying a hundred thousand.
Deploy, document, hand over
Release process written down, documentation aimed at your team rather than at me, and a defined window afterwards where fixes are mine.
Relevant builds
- Shopify · D2C
Online plant store
India’s most trusted online plant store on Shopify, with OTP login, GoKwik one-page checkout and custom product pages.
- Shopify
- GoKwik checkout
- Custom PDP
- E-commerce · Health & fitness
Sports nutrition store
Online fitness and supplement store delivering authentic sports nutrition at speed.
- Commerce build
- Catalogue
- Checkout
- Headless commerce · Fashion
Headless fashion storefront
High-performance headless commerce architecture for India’s fastest-growing men’s fashion brand.
- Headless
- Storefront API
- Performance
Questions
- Do I need Shopify Plus for custom development?
- For most things, no. Custom themes, private apps and API integration all work on standard Shopify. Plus is what you need for checkout extensibility, Shopify Functions, scripts and multiple expansion stores, and those are the specific reasons to pay for it rather than a general sense that the business has grown.
- Can you reduce the number of apps we are paying for?
- Often, and the saving is usually page weight before it is subscription cost. The audit is the deliverable: what each app does, which ones overlap, and which are cheaper to replace than to keep over a two-year horizon.
- Will custom work break when Shopify updates?
- Not if it is built on the supported extension points, which is why checkout work goes through UI extensions and Functions rather than through script injection. Work built on workarounds does break, and some of this job is replacing exactly that.
- Do you build headless Shopify storefronts?
- Yes, over the Storefront API with Next.js or Hydrogen. It is the right answer less often than it is proposed, and the headless commerce page covers when it is and is not.
Describe what is in front of you and you get a written scope and a figure, usually within a few days of a short call. No charge for either.