Skip to content
BestERPinKuwait

Scoring model v1.0

ERP Evaluation Methodology

Every ranking on this site derives from the model set out below: 11 criteria with fixed weights, 45 assessed capabilities, and a written justification behind every number.

Principles

  1. 1

    The overall score is calculated, never assigned

    There is no editorial number that sits above the criterion scores. Change a criterion score or a weight and every ranking on the site moves. This is enforced in code: the scoring function has no parameter for an overall score.

  2. 2

    A score without a justification cannot be published

    Every criterion score carries written reasoning explaining what produced it. The scoring function rejects an empty justification, so an unexplained score cannot reach the site.

  3. 3

    Weights are published and fixed

    The weights below apply to every system equally. They are set for the Kuwaiti market and are stated openly so you can judge whether they match your own priorities.

  4. 4

    We do not publish figures we cannot verify

    Where a vendor does not publish pricing, we say so rather than estimating. Where we have not assessed a capability, it is marked 'not assessed' rather than guessed.

  5. 5

    Every review states who the product is wrong for

    A review that cannot name a limitation is marketing. Every review carries a mandatory 'who it may not suit' section, without exception.

Scoring criteria

11 criteria, weighted to total 100%. Each system is scored 0–10 on each.

Kuwait & GCC Suitability

15% weight

How well the product and its delivery model fit Kuwaiti operating reality: Arabic and English interfaces, KWD handling and 3-decimal precision, GCC group structures, local implementation availability and regional expansion paths.

Scoring guidance: A 9–10 means Arabic/English parity, native KWD handling, established Kuwait delivery capability and demonstrable GCC deployments. A 4–5 means the product works but localisation or local delivery depends heavily on a partner's own investment.

Core ERP Functionality

15% weight

Depth and completeness of finance, procurement, sales, inventory and the operational modules a mid-market business actually runs on day to day.

Scoring guidance: Scored on functional depth within each core area, not on the number of applications available. A broad catalogue with shallow modules does not score higher than a narrower, deeper core.

Workflow Flexibility

12% weight

The ability to model real approval hierarchies, exception paths, branch- and entity-specific rules and cross-module process chains without writing bespoke code.

Scoring guidance: High scores require configurable multi-level approvals, role- and value-based routing, and process rules that survive product upgrades.

Implementation Flexibility

10% weight

How readily the product can be shaped to a customer's process during implementation, and what that shaping costs in future upgrade and maintenance terms.

Scoring guidance: Rewards configuration-first products and penalises architectures where meaningful change requires custom code that must then be re-tested at every upgrade.

Multi-Company & Multi-Branch

10% weight

Support for multiple legal entities, branches, warehouses and inter-company operations, including consolidated reporting and entity-scoped permissions.

Scoring guidance: A 9–10 requires native inter-company transactions, consolidated financial reporting and per-entity access control without duplicating the deployment.

Integration & API Capability

10% weight

Quality of documented APIs, webhook/event support, authentication model and the practicality of integrating banking, e-commerce, POS, logistics and government portals.

Scoring guidance: Assessed on API coverage relative to the product's own data model, documentation quality and whether integrations are supported or merely possible.

Reporting & Analytics

8% weight

Operational reporting, executive dashboards, self-service report building and the ability to answer cross-module questions without exporting to spreadsheets.

Scoring guidance: High scores require cross-module reporting from live data and dashboards that a finance or operations manager can adjust without developer involvement.

AI & Automation

5% weight

Rule-based automation, alerting, scheduled processes and applied AI capabilities that measurably reduce manual work.

Scoring guidance: We score shipped, usable automation. Announced roadmap capability and AI branding without an accessible feature do not earn points.

Scalability

5% weight

Headroom in users, transaction volume, entities and process complexity before a re-platform becomes necessary.

Scoring guidance: Considers both technical scale and organisational scale — governance, segregation of duties and multi-entity growth.

Total Cost Considerations

5% weight

Licensing model transparency plus the implementation, customisation, upgrade and support costs that determine real total cost of ownership.

Scoring guidance: Scores the predictability and transparency of total cost, not headline licence price. A low list price with high customisation dependency does not score well.

Local Support Availability

5% weight

Availability of qualified support in Kuwait, response expectations, escalation paths and the depth of the local skills market.

Scoring guidance: Rewards support delivered in-country and in-timezone, with named escalation, over ticket-only support routed offshore.

How the score is calculated

Each criterion score is multiplied by its weight expressed as a fraction of the total, and the results are summed. A system scoring 9.0 on Kuwait & GCC Suitability contributes 9.0 × 0.15 = 1.35 to its overall score out of 10.

Worked example of the weighted calculation

Worked example of the weighted calculation
CriterionWeightExample scoreContribution
Kuwait & GCC Suitability15%9.01.350
Core ERP Functionality15%8.51.275
Workflow Flexibility12%7.60.912
Implementation Flexibility10%8.00.800
…and so on for all 11 criteriaContributions are summed and rounded to one decimal place.

Capability assessment

Separately from scoring, every system is assessed against 45 specific capabilities across 22 functional categories. These drive the comparison matrix.

We use seven support levels rather than a tick or a cross, because “available through a partner” and “delivered by the core product” are not the same answer, and flattening them is how comparison tables become misleading.

How to read this table

Native
Native — delivered by the core product
Module
Available as a first-party module or add-on
Partial
Present but limited relative to category expectations
Partner
Typically delivered through an implementation partner
Third party
Requires a third-party product or integration
Not available
Not available
Not assessed
Not assessed

Facts, assessments and opinions

Statements about products are labelled by type throughout the site, so you can weight them appropriately.

Fact
Objectively verifiable and backed by at least one cited source. Our helper functions refuse to create a factual claim without a source attached.
Editorial assessment
Our reasoned judgement, derived from this methodology and from implementation experience. Reasonable people can disagree with these, which is why they are labelled rather than presented as fact.
Opinion
A stated viewpoint — usually advice about how to run an evaluation. Clearly marked as a view rather than a finding.

Sourcing

Every source in our register records its publisher, type and the date an editor last checked it. Sources are listed at the foot of each page that relies on them, with the access date shown. ERP products change continuously, so a claim without a date behind it is not worth much.

We prefer vendor documentation and published pricing pages over secondary reporting, and we mark first-hand product verification separately so you can see which claims we checked in the product ourselves.

Content freshness

Each page records when it was published, last updated and last fact-checked, and carries a review interval — 180 days by default, shorter for volatile topics such as pricing. When the interval elapses the page is flagged for re-checking, and a “review due” marker appears in its byline.

Our independence

We have no financial stake in which system you choose. We do not resell, implement or take referral fees from any ERP vendor, and nothing on this site is sponsored. What we do have is a point of view, formed from the evidence set out above — so read the reasoning rather than the ranking, and weigh it against your own requirements.

What we can commit to, and what you can check: the same methodology applied to every system, a written justification for each score, a mandatory statement of where each product is not the right choice, sources on every factual claim, and an editorial policy that commits us to correcting errors, including ones that favour us.

There is no paid placement on this site. No vendor has any influence over what we publish about them. If you believe something here is wrong, tell us and we will check it against the source.

Methodology questions

Current coverage

Systems
9
Criteria
11
Capabilities
45
Individual scores
99