The questions we are asked before every demo

An ERP is one system holding the records that several departments currently keep separately. Instead of an admission file, a fee register, an attendance sheet and the accountant’s spreadsheet each holding a version of the truth, there is one record per student, patient, item, customer or supplier, and each department works on the part of it their role allows.

The benefit is not the software. It is that a fact only has to be entered once, and anyone allowed to see it can answer a question about it without making a phone call.

Not always, and we will tell you so. If one person handles everything in one place and nothing is being retyped, a spreadsheet may genuinely be enough.

It stops being enough when the same figure lives in more than one file, when closing the month means reconciling by hand, when a routine question needs three people to answer, or when only one person knows where anything is. If none of that is happening to you, you do not need us yet.

Schools and colleges take School ERP. Hospitals, clinics and diagnostic centres take Hospital ERP. Shops, showrooms and service businesses that invoice take Billing & GST ERP. Distributors, wholesalers and anyone holding stock across locations take Inventory & Distribution ERP.

If your process does not fit any of those, Custom Business ERP is the modular platform we configure around it. We would rather put you on the suite that already does most of the job than sell you a custom build you do not need.

Pricing depends on the suite, the edition, the number of users and the number of branches. That is why we quote after a short conversation instead of publishing one number — a single-branch shop and a four-branch hospital should not see the same figure. Ask in the demo and you will have it in the same call.

Broadly yes: an offline deployment sits on your own server and is bought as a system, while a cloud deployment is a managed service billed periodically. We will confirm the exact terms for your setup in writing before anything is agreed.

All eight modules listed on each product page are part of that suite. We configure which modules each role can see; we do not charge for them individually.

Support is part of the quote, not an afterthought. Before you commit, we set out in writing what is covered, for how long, how you raise an issue, and what an annual maintenance arrangement includes — updates, backups, and help when a member of staff changes.

We do not publish a figure here because it moves with the edition and the size of the deployment. Ask for it in the demo and it will be in the written quote.

In the Offline / Local edition it lives on a server in your premises, under your control. In the Cloud edition it lives in managed hosting that we maintain, with scheduled backups. You choose which.

Yours. You can request an export of your data at any time, in both editions. Nothing on this site or in the software sells or shares your operational records.

Access is role-based. Front desk, accounts, teaching or clinical staff and management each see only the screens and records their role allows, and changes leave an activity trail.

In the Cloud edition, backups run on a schedule we manage. In the Offline / Local edition, backups are scheduled on your server and we set that up with you at go-live, including where the copies are kept and who is responsible for checking them.

We will also show you how to confirm that a backup actually restores. An untested backup is not a backup, and that is true whichever edition you are on.

Yes. Both editions handle multiple branches, departments, classes or warehouses under one login, with reporting per location and across all of them together.

Cloud is usually the simpler answer when your locations are in different buildings or different towns. An offline deployment can serve remote branches too, but that needs additional network setup — we will tell you what it involves rather than leave you to find out afterwards.

Yes. We import from spreadsheets, CSV exports and most existing billing or accounting programs, and we check the imported records against your originals before you go live. Your current system stays available while we run in parallel.

Most programs can produce an Excel or CSV export of masters, ledgers and stock, and that is what we work from. Where an export is not possible or is unusable, we work from your printed reports and enter masters and opening balances with you, checked line by line against your figures.

We will also be honest about how much history is worth bringing across. Current balances, open items and active master records almost always are. Ten years of closed transactions usually are not — they are better left in the old system, kept available for reference.

A typical rollout is a demo, then configuration and data import, then staff training, then go-live. We give you a dated plan after the demo, once we know how many branches, users and years of history are involved — we would rather commit to a real date than a brochure one.

Three things. One person who can answer questions about how you actually work day to day. Your existing records, in whatever form they are in. And a decision on the formats that matter to you — receipt, invoice, report card, discharge summary, the reports management reviews.

Everything else is our side. The most common cause of a slow rollout is imported data that nobody has time to verify, so we agree at the start who is checking it and when.

Yes. Training is on the actual screens your staff will use, by role, and we stay available while the first month closes.

Within reason, and we would rather show you where the line is than promise everything. Formats, fields, user roles, approval steps, report layouts and dashboards are configuration, and configuring them is part of a normal rollout.

A genuinely new module, or a workflow no other customer has, is development work. We scope that separately, quote it, and put the timeline in writing before starting. Custom Business ERP exists for organisations that need a good deal of that from day one.

Yes, and it is a planned path: assess, prepare, validate in parallel, then a scheduled cut-over. The offline system stays available until you confirm the switch. The four steps are set out on the Cloud & Offline page.

Yes. The Billing & GST suite holds GST rates and HSN codes on the item, splits tax on the invoice, and produces sales, purchase and return registers you can hand to your accountant. The other suites carry the billing modules relevant to them.

Email sales@jpcerpcloud.com for anything pre-sales and support@jpcerpcloud.com once you are running. Our registered office is in Dudahi, Kushinagar, Uttar Pradesh.

Fill in the short form on the demo page — name, mobile number, organisation, email, and which suite you are looking at. You will get a reference code on screen straight away, and we reply within one working day.

The demo itself runs about thirty minutes on your workflow, not a slide deck: the modules that apply to you, offline versus cloud for your number of branches and users, how your existing records would be brought across, and pricing for your actual setup.