ERP Implementation in Pakistan: Avoiding the Usual Failures
ERP implementation in Pakistan often stalls for the same reasons. Here is why projects fail in SMEs, and the practical steps that help yours succeed.
When ERP projects in Pakistan fail, it is usually for human reasons, not technical ones. The system is chosen without the people who must use it, old data goes in messy, and Excel never gets switched off. You can avoid most of this by starting small, cleaning your opening figures, making one person responsible, and asking vendors hard questions before you sign.
Why ERP projects stall in Pakistani SMEs
Owners who have lived through a failed rollout usually tell the same story. The software was bought, there was some training, and a while later the godown was back on the register, accounts was back on Excel, and the ERP had become an expensive screen nobody opened. The reasons repeat.
The people who use it were never asked
The owner and the consultant pick the system in a meeting room. The storekeeper, the dispatch clerk and the accountant meet it on go-live day. If it slows them down or confuses them, they quietly go back to what they know. They are not being difficult. They have work to finish before load-shedding starts.
The system is asked to copy the old mess
Every business has workarounds: a column in Excel that means three different things, a WhatsApp group where purchase approvals happen, a register only one person understands. If you ask the new system to copy all of that, you get the old problems on a new screen.
Opening data goes in dirty
If your stock figure was guesswork before go-live, it stays guesswork after. Many projects load unchecked balances and party ledgers, staff see wrong numbers on day one, and trust is gone.
Everything goes live at once
Sales, purchase, inventory, production, accounts and payroll all switch on together. Every department hits problems at the same moment, and nobody has time to fix any of them properly.
Nobody inside owns it
The vendor cannot run your business. Without someone on your side who chases entries, settles arguments and decides how things will be done, the project drifts.
What to settle inside your business first
Before you look at any software, spend a little time on your own house. It costs nothing and it shapes everything after.
- Write down the problems you want gone. Be specific: "warehouse, sales and accounts show different stock", "production cost is an estimate", "monthly reports take days". These become your test for every vendor.
- Pick one project owner. A trusted manager with authority, not the most junior person who "knows computers".
- Decide what goes first. Usually the area that hurts most, often stock or purchase.
- Decide who sees what. Which roles should enter data, which should approve, which should only view.
- Agree a cut-off date. Opening stock and balances need a clear date and a physical count to match.
Questions to ask any ERP vendor before you sign
A good vendor welcomes hard questions. Ask these of everyone you speak to, and get the answers in writing.
- Can we see it working live, with sample data like ours? Slides prove nothing. Ask them to show a stock movement flowing through to the accounts.
- How does our existing Excel data come in? Who cleans it, who checks it, and what happens to records that don't fit?
- What happens when the internet or power goes? Can staff keep working, and what happens to entries made during the cut?
- Where is our data kept, and how is it backed up? How do we get a full copy out if we ever leave?
- Who supports us, when, and in what language? A support line your storekeeper cannot talk to is not much use.
- Does it handle the tax and invoicing rules that apply to our business? Ask them to show it, not just say yes.
- What exactly does the quote cover? Users, companies, departments, training, changes after go-live.
If a vendor goes vague on any of these, treat that as your answer.
A rollout plan that survives real life
Once you have chosen, the way you roll out matters as much as the software.
- Start with one area. Get stock right before you add production costing on top of it.
- Do a physical count and lock the opening figures. Everyone should agree the starting number before the first entry.
- Train by role, on their own screens. The godown keeper needs to learn stock in and stock out, not the whole system.
- Run old and new side by side for a fixed, short period, then stop. Announce the date the register closes, and close it. Parallel running with no end date is how projects die.
- Review the exceptions every week. Missing entries, negative stock and figures that don't tie are where the learning happens.
- Add the next department only when the first one is steady.
Where Sentinel fits
Sentinel is an ERP that ExaSnap sells and supports, and it addresses several of the problems above. It does not replace the groundwork. It makes that groundwork easier to keep up.
It is one system for every department: CRM, sales, purchase, inventory, manufacturing with bills of materials, dispatch, accounting, HR, payroll, warehouse and documents. Warehouse, sales and accounts work from the same records instead of three versions. Every entry records who made it and when, so the stock ledger and the books show who did what. The books reconcile across one or several companies, with a trial balance that ties.
Access is by role, so each person sees and changes only what their role allows. That also means less to learn. Shop floor screens can be in Roman Urdu for staff who used to run their part of the business in Excel, and Sentinel works on desktop and on every phone.
The AI agent helps with the weekly exception review. You can ask it questions in plain English or Roman Urdu, like "Kis item ka stock kam hai?". It runs checks for stock below zero, totals that don't add up, missing fields and unfinished work, and raises each problem to the person responsible. It never changes a record by itself.
Questions owners ask
How long does ERP implementation take?
It depends on how many departments you start with, how clean your opening data is, and how much time your people can give it. Be wary of anyone who promises a date before seeing your business. Ask for a written plan with stages instead.
Should we keep Excel running alongside the new system?
Only for a short, fixed period while staff gain confidence. Set the date it stops before you begin. If both run with no end date, people will trust the familiar one, and the ERP never takes hold.
Why do ERP vendors give a quote instead of a price list?
Because the cost really does change with your setup. For Sentinel, the quote depends on how many people use it, how many companies it keeps the books for, and which departments you need. You can see how that works on the plans page.
If you are weighing an ERP and want to see how Sentinel handles stock, accounts and the checks in between, book a live demo. Bring your hardest questions about stock, accounts and access, and judge it on what you see.