A lot of Shopify briefs we get from Indian brands start the same way: "We need a custom app for this." Sometimes they do. More often, the job is a theme edit, a few metafields and an app that already exists. The difference matters, because a custom app is something you now own, host and maintain forever.
So before we write a line of code, we run through the five-step decision path below.
Step 1: Is it about how the store looks or what it shows?
If the request is about layout, content or display, start with the theme.
Shopify's Online Store 2.0 themes are built from JSON templates and sections. The theme architecture docs describe JSON templates as "a wrapper for sections", and sections as reusable modules that merchants can add to templates. In practice that means:
- A new homepage block, a size-chart tab, a "made in India" badge or a delivery note on product pages is a section or block in the theme.
- Data that changes per product (fabric, care instructions, warranty period, a PDF spec sheet) goes in metafields, and the section reads it.
- The merchant can then move and edit these in the theme editor without calling a developer.
Good rule: if the store owner should be able to change it next month without you, build it as a section with settings, not as hard-coded Liquid.
Typical "theme" jobs: custom product page layouts, bundles shown as content, store locator pages, B2B enquiry forms on product pages, landing pages for campaigns.
Step 2: Does an existing app already do this well?
Before custom code, search the Shopify App Store. Reviews, support response and how the app loads on the storefront matter more than the feature list. We check three things:
- Does it add heavy scripts to every page? Open the storefront, check the network tab and a mobile Lighthouse run before and after installing it on a dev store.
- Does it store data you'll need later (orders, customer fields) in a way you can export?
- What happens to the theme if you uninstall it? Leftover snippets are common.
If an app covers 90% of the need and the other 10% is cosmetic, a theme tweak on top is usually cheaper than a custom app.
Step 3: Does it need to change data, logic or checkout?
This is where custom apps start making sense. Signs you need one:
- Admin workflows the store team runs every day: bulk-tagging orders for a courier, approving wholesale customers, syncing stock from a warehouse sheet.
- Integrations with an ERP, accounting tool, or a courier that has no good app.
- Logic at checkout: custom discounts, payment or delivery rules.
For a single merchant, Shopify's distribution docs say you'll typically use custom distribution, meaning the app is installed on that one store and not listed publicly.
Step 4: Check the plan before you promise checkout changes
Teams get caught out most often at this step. We confirm two things in Shopify's docs on every brief:
- Checkout UI extensions for the information, shipping and payment steps are available only to stores on Shopify Plus. Blocks on the Thank you page are a separate target.
- Shopify Functions (the way to customise discounts, delivery and payment logic) have limits too: the Functions docs state that only Plus stores can use custom apps that contain Function APIs, and some Functions capabilities are Plus-only.
So if a non-Plus brand asks for "hide COD above a certain cart value" or "an extra field on the shipping step", the answer may be: use a public app that offers it, change the approach, or plan for Plus. Better to say that in the first call than after the build.
Step 5: Who will maintain it?
A custom app is a small software product. Someone has to:
- Host it and keep it running.
- Update it when Shopify's API versions change.
- Keep access tokens and secrets safe.
- Fix it when the store team changes how they work.
If nobody owns that, a theme section plus a well-supported app is often the better business choice, even if it's less elegant.
The quick version
| The request | Usually the answer |
|---|---|
| Change how pages look or what content they show | Theme sections + settings |
| Show different data per product | Metafields read by a section |
| A common feature (reviews, wishlists, subscriptions) | Existing app, checked for speed |
| Daily admin workflow or ERP/courier sync | Custom app (custom distribution) |
| Change checkout steps or discount/payment/delivery logic | Check the plan first: Plus, an existing app, or a different approach |
What we write down before starting
Whichever route wins, we put four lines in the scope:
- Where the change lives (theme section, metafield, app, or custom app).
- Which Shopify plan it depends on.
- Who can edit it after launch, and how.
- Who maintains it, and what happens if it is removed.
Writing those four lines down early has saved us more arguments than any code review.
I'm part of the team at Brightcode, a web development studio in Delhi NCR. We build and fix Shopify and WooCommerce stores for Indian brands (e-commerce development). If you're still choosing a platform, our Shopify vs WooCommerce comparison covers fees and COD in India, and our note on hiring Shopify developers in Delhi NCR lists what to check in a developer.

