Things breaking.
Checkout failing, payments not updating, emails not sending, the admin panel timing out. The problems that cost money while they’re open.
CS-Cart Support and Maintenance
CS-Cart Support and Maintenance
Most of our work is with clients we’ve had for years. That’s not a sales line. It’s how this actually works. Someone who already knows your store fixes things in an afternoon that would take a stranger a week.
What’s covered
Keeping current.
CS-Cart version upgrades, add-on updates, PHP updates, and security patches. Done deliberately rather than when your host forces it.
Performance.
Watching load times and fixing them when they slip. Usually it’s one add-on, one missing index, or bot traffic hitting uncached URLs. Here is how we work out which.
Servers.
Setup, monitoring, backups, SSL, caching, and the tuning that keeps a store fast as the catalogue grows.
Small changes.
The steady stream of tweaks every trading store needs: a new payment method, a shipping rule, a report column, a template change.
Response times
We respond within one working day.
Every ticket, whatever it is: a store that’s down, a payment that isn’t updating, an add-on bug, or a new request. One number, no severity tiers to argue about.
Urgent things move faster than that in practice. A store that’s down doesn’t wait in a queue behind a report column.
Our hours are 10:00 to 19:00 IST, Monday to Friday. If you need cover outside that, tell us what you need and we’ll be straight about whether we can offer it.
If WhatsApp is easier than email, message us on +91 94788 81111. Same team, same response time.
How it works
Monthly retainer
An agreed block of hours each month covering monitoring, updates and changes. Unused hours don’t roll over forever. We’ll tell you if you’re consistently buying more than you need.
Pay as you go
No retainer. You send work, we quote it, you approve it. Slower to start on urgent things, because you’re not in a queue we’ve reserved for you.
Most stores start pay-as-you-go and move to a retainer once they notice they’re sending work every month anyway.
What we won’t do
We won’t quietly patch core files to fix something faster. It works today and it breaks your next upgrade. If a core change is the only way, we’ll say so and document it.
We won’t sit on a problem we can’t solve. If something needs your host, your payment provider, or a specialist we’re not, we’ll tell you on day one.
Proof
Read the case studies for stores we have looked after over years rather than weeks, including one where three of the add-ons we built became products in our catalogue.
Questions we get asked
Yes. Most stores we support were built by someone else. We start by reading what's there and writing down what we find, which is useful to you whatever you do next.
Common. We identify what was changed and move it into add-ons over time so your store becomes upgradeable again.
For server work, yes. For store work, admin access and a staging copy is usually enough. We'll ask for the least we need.
Yes. We'll want whatever documentation exists, repository access if there is one, and a week to read before we commit to anything.
