Most ERP selection processes in Kuwait go wrong in the same place: the requirements document. It gets written as a feature list, vendors respond by ticking every box, and the decision ends up being made on price and rapport because nothing else has been meaningfully differentiated. This guide sets out a different sequence — one that produces a shortlist you can defend and a contract that survives contact with reality.
Start with process, not features
A feature list tells a vendor nothing about your business. Every ERP evaluated on this site has multi-currency accounting, purchase orders and stock transfers. What differs is how those capabilities behave when your specific process runs through them.
Instead, document three to five processes end to end, including the exceptions. A useful order-to-cash description for a Kuwaiti trading company reads something like this: a customer enquiry arrives, a quotation is raised, the margin is checked against a floor, discounts above a threshold route to the general manager, credit exposure is validated before confirmation, the order reserves stock across branches, shortfalls trigger a purchase requisition, dispatch is scheduled, an invoice is raised, and collection is tracked against terms.
Size the requirement honestly
Two symmetrical mistakes cost Kuwaiti businesses real money. The first is buying an enterprise platform for a mid-market operation, paying for functional depth and governance capacity that never gets used. The second is buying a small-business package for an organisation that will outgrow it within three years, then funding a full re-implementation.
- Employee count and expected ERP user count, separately — approvers who log in twice a week are still users
- Number of legal entities today and in your credible three-year plan
- Number of branches, warehouses and stock-holding locations
- Transaction volumes at peak, not average
- Whether your growth plan involves new entities, new countries, or simply more of the same
Build a shortlist of three
Three is the right number. Two gives you no reference point for judging a proposal; five or more exhausts your team before the demonstrations begin, and the later vendors get a less rigorous evaluation than the earlier ones.
Systems Kuwaiti businesses most often shortlist
Larger organisations should also evaluate SAP S/4HANA and Oracle Fusion Cloud ERP. Our ERP Finder produces a scored shortlist from your own requirements.
OctoVyre
A Kuwait-built ERP platform organised around connected end-to-end business processes rather than independently installed applications.
Odoo
A modular business application suite with an unusually broad catalogue, an active global community and a large independent partner market.
Microsoft Dynamics 365
A family of ERP and CRM applications whose decisive advantage is how completely it integrates with the rest of the Microsoft estate.
SAP Business One
SAP's SME and lower mid-market product: a much lighter platform than S/4HANA, delivered entirely through partners.
Oracle NetSuite
A cloud-only mid-market ERP with unusually strong multi-subsidiary consolidation, aimed at growing and internationally structured businesses.
Run demonstrations that reveal fit
A vendor-led demonstration shows you the product at its best. That is what it is designed to do, and there is nothing dishonest about it — but it will not tell you whether the system fits your business. Take control of the agenda.
A demonstration structure that works
- 1
Send your scenarios in advance
Give every vendor the same three processes, including the exception cases, at least a week before. Anyone unwilling to prepare against your scenarios is telling you something useful.
- 2
Insist on live configuration
Ask them to build your approval matrix in the product during the session. Slides and pre-recorded videos do not answer the question.
- 3
Use your own data
Provide a sample chart of accounts, an item master extract and a customer list. Products behave differently against real data than against demo data.
- 4
Score immediately
Have each attendee score against your published criteria before leaving the room. Impressions decay and converge within a day.
- 5
Ask what it cannot do
A vendor who cannot name a limitation has either not understood your requirement or is not being straight with you.
Evaluate the partner as rigorously as the product
For any partner-delivered platform — Odoo, Dynamics 365, SAP Business One, NetSuite and most others — the implementation partner is at least as large a variable in your outcome as the software. Two implementations of the same product by different partners routinely produce very different results.
Partner due diligence
- Kuwait delivery record with reference customers you can actually call
- Named consultants who will work on your project, with their availability confirmed in writing
- Which of your requirements they intend to meet with configuration versus custom development
- Who re-tests custom work at each product upgrade, and at whose cost
- What support covers after go-live, with response commitments in the contract
- What happens commercially if the project overruns
Verify the Kuwait specifics
Several requirements are easy to assume and expensive to discover late. Test them during evaluation rather than during implementation.
Kuwait-specific checks worth running in every demonstration
| Requirement | How to test it |
|---|---|
| KWD three-decimal handling | Enter a price with three decimals, apply a percentage discount, and check the rounding through invoice and financial report. |
| Arabic interface | Switch the interface to Arabic and complete one full transaction, not just view a screen. |
| Multi-branch stock visibility | Ask to see stock for one item across every branch, on one screen. |
| Approval hierarchy | Have them configure your real approval matrix live, including a value threshold and an escalation. |
| Consolidated reporting | Request a consolidated trial balance across your entity structure using your chart of accounts. |
Make the decision defensible
Publish your evaluation criteria and weights before the demonstrations, score against them immediately afterwards, and record the reasoning. This does two things: it stops the loudest voice in the room from deciding, and it gives you a documented rationale when someone asks in year two why this system was chosen.
Our ERP Finder applies a transparent scoring model to your requirements and explains why each system scored as it did.
Find My ERP