We’ve built 125+ add-ons that are in our catalogue, and a lot more that were built for one client and stayed there.
The thing that matters most isn’t the feature. It’s that it’s built as a proper add-on: using hooks, in its own directory, with its own settings and its own database tables. Not edited into core files.
A store built that way stays upgradeable. One with edits buried in core files turns every upgrade into a negotiation.
Our biggest category by a distance: 90 of them, across the Gulf, India, South Asia, Africa, Europe, the US and Australia. If your market’s gateway doesn’t have a CS-Cart integration, this is routine work for us rather than a research project. Browse the gateways we already support, or read how to choose a gateway by market.
Live rates at checkout, label and shipment creation, tracking back on the order automatically. DTDC, Ekart, Safexpress, Shiprocket, UPS, ShipStation and more.
ERP and accounting systems, delivery platforms, marketplaces, review platforms, search services, CRMs. Two-way sync, webhooks, and the cron jobs that keep it all current.
The unglamorous things that save a team hours a week: automated clearance pricing, order splitting and merging, bulk reporting, scheduled jobs, admin screens that work on a phone.
Anything that changes how customers browse, choose or buy.
with settings, language variables and an uninstall that actually cleans up
If a core change is genuinely unavoidable we tell you, and we document it so your next upgrade doesn’t silently lose it
for anything with settings, so your team and any future developer can see what it does
You own it. No licence key, no phoning home
Read the case studies to see add-ons we built for one store that became products anyone can buy, and the integration frameworks behind the bigger builds.
Every add-on in our catalogue started this way. You can open any product page and see the supported versions, the settings and what it does.
Fixed price per add-on, quoted from a written spec. If the spec changes, we quote the change first.
Small integrations are usually days. A payment gateway is usually a couple of weeks including sandbox testing. Anything touching orders, stock or money takes longer, because it should.
That's the point of building it as a proper add-on. We also test our catalogue against new releases.
Usually. We'll look and tell you honestly whether fixing or rebuilding is cheaper.
Yes. Several of ours started as client work. If yours could be a product, we'll say so, and you decide whether it stays private.
That's most of what we do. If it has an API, it's a scoping question rather than a research question.
Your complete CS-Cart team: add-ons, development and support from an official partner.
