OCMod, not core edits
Modifications through the platform’s own mechanism. Edited core files are why so many of these stores cannot be upgraded.
A light PHP store platform, still running a lot of Indian shops.
OpenCart is simple, free and widely used across India. I build on it, extend it, upgrade installs that have fallen behind, and migrate stores off it when the ecosystem has stopped serving them.
OpenCart is a lightweight PHP shopping cart that has been popular in India for a long time, largely because it is free, undemanding about hosting and quick to get running. For a small to medium catalogue with straightforward needs, it does the job without the resource requirements of heavier platforms.
Its architecture is simple in a way that cuts both directions. The MVC structure is easy to read and extend, so custom work is quick for anyone who knows PHP. But the extension ecosystem is thinner than WooCommerce’s, and many popular extensions are commercial, unmaintained, or both. OCMod and vQmod let extensions modify core behaviour without editing files – useful, and a frequent source of conflicts when several extensions modify the same thing.
The typical store I am asked to look at was built five or more years ago, runs an old 2.x or 3.x version, and has several paid extensions whose developers have disappeared. It works, it is not receiving security updates, and nobody wants to touch it.
That gives the same two honest options as any ageing platform. Upgrade and maintain, if the extensions you depend on still have a path. Or migrate, usually to WooCommerce, where the ecosystem is larger and finding a developer next year will be easier. Both are real answers, and which one applies is a question about your specific store.
Modules written to the platform’s MVC structure using OCMod rather than editing core files.
Functionality that survives upgrades, instead of changes erased by the next one.
Custom themes and child themes built to your brand, responsive and tested on real devices.
A store that looks like your business rather than the default template.
Moving between versions with extension compatibility established first, on a staging copy.
Security support without an upgrade that breaks the shop.
Razorpay, PayU, Cashfree, cash on delivery, and the courier services your warehouse actually uses.
Payments and shipping that work for Indian customers rather than for a default install.
Query work, image handling, caching and removing extensions that are no longer earning their place.
A faster store and fewer moving parts to go wrong.
Products, categories, customers and orders moved, theme rebuilt, and every URL redirected.
A larger ecosystem and easier hiring, without losing catalogue or search visibility.
Mostly about not making an already fragile install worse.
Modifications through the platform’s own mechanism. Edited core files are why so many of these stores cannot be upgraded.
Every extension checked for whether it is still maintained, before an upgrade discovers it for you.
Upgrades and extension changes applied to a copy and checked, never straight onto a store taking orders.
Gateways exercised across success, failure and refund in test mode before a real transaction.
The extension pool is thinner and developers are scarcer. That affects your five-year cost, and you should hear it.
What is installed and what was modified, because these stores almost never come with notes.
Mostly established Indian stores that have been running for years.
A working store with a manageable catalogue and straightforward fulfilment.
Running 2.x or 3.x with no security updates and an unclear upgrade path.
Depending on paid extensions whose developers have gone quiet.
Where the low resource requirements are genuinely part of why it was chosen.
The person who built it has moved on, and nobody will quote for the platform.
Weighing another few years here against migrating to a larger ecosystem.
This platform had a strong run with Indian small businesses, and a good number of those stores are still trading. What has thinned is the support around them – the agencies that built them have moved to other platforms, and store owners find nobody willing to quote for maintenance.
The Indian requirements are the same as anywhere: GST with correct interstate handling, HSN codes, Razorpay or PayU rather than assuming Stripe, cash on delivery treated as a real method, and courier integration with pin-code serviceability at the cart.
I work with store owners across Bangalore and India, and with clients in the UK, USA, Canada, the UAE and Singapore – though this platform is mostly an Indian and Eastern European story in practice.
The platform’s natural audience here.
Tax rates, HSN codes and invoice formats.
Work most agencies no longer quote for.
The alternative costed alongside, honestly.
Serving Chennai, Bangalore, India, Canada, UK, USA, Dubai, Singapore.
Mid-size Indian retail, mostly.
Typically needs: A few hundred to a few thousand products with ordinary fulfilment.
How I help: Category structure and filtering tuned, with payments and couriers integrated for Indian customers.
Typically needs: Size and colour options and seasonal stock turnover.
How I help: Option handling modelled properly, with bulk catalogue updates made practical.
Typically needs: Specification data and part compatibility.
How I help: Attribute-driven specifications and filtering that works at catalogue size.
Typically needs: Large catalogues where finding the right part is the whole job.
How I help: Search and filtering tuned around part numbers and compatibility data.
Typically needs: High SKU counts with low margin per item.
How I help: Bulk import and stock workflows, with performance work so large categories stay usable.
Typically needs: Regional fulfilment and dealer pricing.
How I help: Customer group pricing where the platform supports it, with courier and serviceability rules.
Audit first, because these stores rarely are what anyone remembers.
I audit the install: version, PHP version, every extension and whether it is still maintained, core modifications, theme customisations and current performance.
You get: A written audit and an honest upgrade-versus-migrate comparison with both costs.
Why it matters: Nobody should choose a direction for a store nobody has actually looked inside.
We settle the direction and scope – what gets upgraded or rebuilt, what extensions are replaced, and what the target looks like either way.
You get: An agreed plan and a fixed quote.
Why it matters: Store projects drift when the platform question is left open while work has already begun.
Design for the templates that sell: category, product, cart and checkout, phone width first, against real product data.
You get: Designs for the key templates, approved before building.
Why it matters: Default templates are where most of these stores lose customers, and that is fixable.
The build: theme, custom modules through OCMod, payment and courier integration, and catalogue work – on a staging copy throughout.
You get: A working store on staging you can place test orders on.
Why it matters: These stores are live and trading, so nothing intermediate should reach a customer.
Full order testing across devices and payment methods, tax and shipping verified, and for migrations the complete redirect map tested.
You get: A tested store and, where relevant, a verified redirect map.
Why it matters: A payment path that fails silently is the most expensive fault a store can carry.
Launch at a quiet hour with live gateway keys, then training on catalogue, orders and stock, with written notes.
You get: A live store, trained staff and documentation.
Why it matters: The absence of documentation is exactly why the last developer was irreplaceable.
The platform, what it runs on, and where stores usually move.
Scoped from the audit, not offered as a package.
The platform supports SEO-friendly URLs, per-product metadata and sitemaps, but very little of it is on by default. A default install produces URLs full of parameters and duplicate paths to the same product through different categories.
Most of the work is configuration rather than content. Nobody can guarantee a ranking – the point is that a store should not be held back by settings nobody switched on.
These stores frequently keep specifications inside description HTML rather than in attributes, which makes the data invisible to filtering and to anything automated. Moving it into real attributes helps customers and machines at the same time.
The practical reasons, rather than the adjectives.
Most agencies stopped taking this work, which is why so many of these stores sit unmaintained. The work is not hard; finding someone willing is the hard part.
The extension pool is thinner and developers are scarcer than for WooCommerce. That is a real five-year cost and you should hear it before deciding, not after.
Everything through OCMod. Plenty of these stores cannot be upgraded because someone edited core years ago, and I will not set that trap for the next person.
GST, HSN codes, Razorpay and PayU, cash on delivery and courier integration configured as part of the work rather than bolted on.