Liquid written properly
Theme logic in the theme, not injected through the admin or bolted on with script tags that nobody can find later.
A store you can run yourself, built by someone who reads the Liquid.
Shopify removes the maintenance burden entirely, which is worth real money. I build custom themes, extend them properly, and give you a straight comparison of its fees against owning the platform outright.
Shopify’s proposition is simple and genuinely valuable: you never think about hosting, security, PCI compliance, updates or scaling again. For a business without technical staff, that removes an entire category of risk and cost. Stores stay up during traffic spikes without anyone being called.
The theme layer is more capable than people assume. Liquid is a real templating language, sections and blocks give merchants genuine page-building control, and metafields allow structured product data beyond the defaults. A custom theme here is proper development work, not configuration.
The costs are ongoing and worth arithmetic rather than assumption. There is the subscription, transaction fees where you do not use Shopify Payments, and app subscriptions – which accumulate quietly. A store running eight apps at twenty dollars a month is paying more for those than for the platform. That is fine if they earn it, and worth auditing if nobody has checked.
Where it genuinely struggles is complex B2B pricing, unusual fulfilment rules and deep customisation of the checkout, which is restricted outside the top tier. If your business has those, the platform will fight you and I would rather say so before the build than after.
Themes built from your brand in Liquid, with sections and blocks your team can rearrange without a developer.
A store that looks like you rather than a purchased theme with the colours changed.
Extending a purchased theme properly – in the theme’s own structure rather than bolted on with injected script.
Changes that survive theme updates instead of vanishing at the next release.
Product data beyond the defaults, modelled as metafields and surfaced in templates.
Specifications, care instructions and compatibility data as real fields, not description text.
Choosing and configuring apps, and auditing the ones you already pay for against what they deliver.
Fewer subscriptions, less script on every page, and a clearer monthly bill.
Products, variants, customers and order history moved from WooCommerce, Magento or elsewhere, with URLs redirected.
A move onto the platform without losing catalogue data or search visibility.
Moving to WooCommerce where owning the platform and dropping the fees is the better arithmetic.
The same store without the recurring platform and app costs.
Mostly about restraint, which is unusual advice on this platform.
Theme logic in the theme, not injected through the admin or bolted on with script tags that nobody can find later.
Every app is a subscription and usually script on every page. If a small amount of theme code does the job, that is cheaper and faster forever.
Merchants get real page-building control inside your brand, so routine changes do not need a developer.
Gateways exercised across success, failure and refund in test mode before the store takes a real order.
Subscription, transaction fees and app costs projected against your expected volume, next to the alternative.
Your team is shown products, orders, sections and reporting, with written notes.
Businesses buying simplicity, deliberately.
Selling direct, where speed to market and reliability matter more than owning the platform.
Nobody in-house to handle updates, security or a server at two in the morning.
Launches, sales and campaigns where scaling is somebody else’s problem.
Selling through social, marketplaces and retail alongside the website.
Paying for a dozen subscriptions nobody has audited against what they actually deliver.
Volume now high enough that the arithmetic against ownership is worth doing properly.
For Indian stores there are specifics worth settling before the build. Payment gateways – Razorpay, PayU and Cashfree integrate, and using any of them rather than Shopify Payments carries an additional transaction fee that belongs in the arithmetic. Cash on delivery needs proper handling rather than being treated as an edge case.
GST is the other one. Tax rates, HSN codes and invoice formats that satisfy Indian requirements usually need an app or custom work, because the platform’s native tax handling was not built for the Indian regime. That is a known cost, and better known before launch.
I work with store owners across Bangalore and India, and with clients in the UK, USA, Canada, the UAE and Singapore.
Razorpay, PayU and Cashfree, with the fee implications stated.
Rates, HSN codes and compliant invoices sorted before launch.
Cash on delivery and courier integration handled properly.
India, the UK, USA, Canada, the UAE and Singapore.
Serving Chennai, Bangalore, India, Canada, UK, USA, Dubai, Singapore.
Retail, mostly, and it is very good at retail.
Typically needs: Variants across size and colour, seasonal drops and a high return rate.
How I help: Variant modelling that stays manageable, size guides in metafields, and returns handled through the platform.
Typically needs: Ingredient detail, subscriptions and repeat purchase.
How I help: Structured product content as metafields, with subscription apps chosen rather than accumulated.
Typically needs: Perishables, delivery zones and time-limited availability.
How I help: Zone and slot handling, with stock rules that reflect how the kitchen or warehouse actually works.
Typically needs: Heavy shipping, lead times and configurable options.
How I help: Weight-based shipping, lead times shown on the product page, and variant options that affect price.
Typically needs: Specification comparison and compatibility.
How I help: Specifications as metafields, driving comparison and compatibility filtering.
Typically needs: Large imagery, certification details and higher-value baskets.
How I help: Image handling that stays fast, certificate fields, and gateways configured for larger transactions.
Six stages, with the fee arithmetic done before anyone commits.
I establish what you sell, how variants work, how you ship and invoice, expected volume, and whether the platform’s fees make sense against the alternative.
You get: A written scope, the fee projection and a fixed quote.
Why it matters: The fees are a running cost for the life of the store. They belong in the decision, not in a surprise invoice later.
Product structure, variants and metafields are modelled, the app set is chosen deliberately, and gateway and tax configuration is settled.
You get: A product model, an app list with costs, and a tax and payment plan.
Why it matters: Apps chosen reactively are how a store ends up paying more in subscriptions than in platform fees.
Design for the templates that sell – collection, product, cart and checkout – at phone width first with real product imagery.
You get: Designs for the key templates, approved before building.
Why it matters: Collection and product pages are where the money is made, so they get designed rather than inherited.
The theme is built in Liquid with sections and blocks, the catalogue is loaded, and apps and integrations are configured.
You get: A working store on a development theme you can browse and test-order on.
Why it matters: Building sections properly is what lets your team change pages afterwards without calling me.
Full order testing across devices and payment methods, tax and shipping verified against real scenarios, speed measured with all apps running.
You get: A tested store and the performance numbers with the real app load.
Why it matters: Apps are the main source of slowness here, and it only shows once they are all installed.
Launch at a quiet hour with live gateway keys, analytics and Search Console configured, then training on products, orders, sections and reporting.
You get: A live store, trained staff and written notes.
Why it matters: The platform is meant to be run by merchants. A store that needs a developer for a price change has failed at that.
The platform, its templating layer, and the alternative.
Scoped against your catalogue, not bundled as a package.
The platform handles basics well – clean URLs, automatic sitemaps, editable metadata and fast global hosting. What it does not let you change is the URL structure itself: products sit under a fixed path, and collection-scoped product URLs create duplicates that need canonical handling.
Those are constraints rather than faults, and they are manageable once you know about them. Nobody can guarantee a ranking on any platform.
Product data held in metafields rather than typed into descriptions is readable, consistent and easy to mark up accurately. That is the single most useful thing a store can do for automated readers, and it also makes filtering and comparison possible.
The practical reasons, rather than the adjectives.
Subscription, transaction fees and apps projected against your volume, next to what owning the platform would cost. Then you decide, knowing the number.
Most Shopify agencies solve problems by installing something. Every app is a monthly cost and usually script on every page, and theme code is often cheaper and faster forever.
I have no reason to push you onto one. I build WooCommerce too, so the recommendation is about your business rather than about what I happen to sell.
GST, HSN codes, compliant invoices, Indian gateways and cash on delivery sorted before launch rather than discovered in the first week of trading.