An ERPNext Team On Call, Not a Ticket Into the Void
Once ERPNext runs your invoicing and dispatch, an unanswered issue costs real money. Our maintenance contracts give you named engineers, response times written into the agreement, monitored backups and upgrades that are tested before they reach your live system.
50+ ERP and software projects. Zero failed projects since 2021.
The cost of ERP downtime is not the fix, it is the wait
A blocked invoice on the last day of the month holds up dispatch, cash collection and the close behind it.
No explaining your business again on every ticket
You get the same small group of engineers month after month, with your configuration, your customizations and your integrations already in their heads. That is the difference between an issue resolved in an hour and one that spends the first day being understood.
- A named team, not a rotating queue.
- Your setup documented and kept current.
- Escalation path agreed before you need it.
Most incidents give warning before they stop work
Disks fill, background job queues back up, scheduled syncs start failing quietly and backups stop completing. We monitor all of it and act on the warning, so the majority of what we fix never becomes something your team notices.
- Server, queue and scheduler monitoring.
- Backups verified and restores actually tested.
- Security patches applied on a schedule.
Three levels of cover
Pick the one that matches how much of your operation depends on ERPNext being available.
What happens when you raise an issue
What the contract covers every month
Ticketed help desk
Email and portal access with priorities and response targets written into the agreement.
Backups and restore tests
Daily backups that are verified, with a periodic restore proving they actually work.
Monitoring
Server resources, background job queues, scheduler health and failing sync jobs.
Security patching
Framework and operating system patches applied on a schedule, tested first.
Version upgrades
Run on staging, checked against your customizations, then scheduled with you.
Included change hours
A monthly block for small changes, new reports, permission fixes and user questions.
What a real support contract gives you
Why teams choose TCB Infotech for ERPNext support
ERPNext support and AMC questions
What does an ERPNext AMC actually cover?
What response times do you commit to?
Do you support an ERPNext instance your team did not build?
Are version upgrades included?
What is not included in the contract?
Can we move our support to you mid-year?
Put Your ERPNext on a Support Contract
Book a free consultation. Tell us how your instance is hosted and what has been going wrong, and we will recommend the plan that fits and what it should cost.
Book a Free Consultation →No commitment. An honest view of the cover you actually need.
What an ERPNext Maintenance Contract Includes
A support agreement is only worth what is written into it. Here is exactly what we commit to, what we watch on your instance, and what you receive each month.
Cover for the system, and time for the things you keep needing
Priorities and targets agreed before anything goes wrong
Issues are raised by email or portal and triaged against priorities you have already agreed, so nobody argues about severity during an incident. A named engineer who knows your setup picks it up, reproduces it on staging, and you can see the status at any point.
- Written response targets by priority level.
- A named team rather than a rotating queue.
- Diagnosis on staging, not experiments in production.
The work that stops incidents from reaching your users
We watch disk and memory, the background job queue, the scheduler and any failing sync jobs, and act on the warnings. Backups run daily, are verified, and are periodically restored to prove they work. Security patches go on in a tested, scheduled way rather than in a rush.
- Resource, queue and scheduler monitoring with alerts.
- Daily backups with periodic restore tests.
- Framework and operating system patching on a schedule.
Staying current without a project every time
Version upgrades run on a staging copy first, where your customizations, print formats and integrations are tested against the new release. You get the report, then pick the window. Alongside that, a monthly block of hours covers the small requests that would otherwise queue up for months.
- Upgrades rehearsed on staging with a rollback plan.
- Customizations and integrations checked before you move.
- Included hours for reports, permissions and small changes.
Everything that comes with the contract
Written service agreement
Priorities, response targets, cover hours, escalation path and exclusions, all on paper.
Named engineers
A small assigned team, with a documented backup person so cover never depends on one individual.
Monthly report
Tickets raised and closed, response times met, changes released and any root cause findings.
Staging instance
A maintained copy of production for reproducing issues and rehearsing every release.
Living documentation
Your setup, customizations, integrations and runbooks kept current as the system changes.
Access you control
Your servers, your repository, your credentials, with our access revocable at any time.