ERP implementation from analysis to live operation
Most ERP projects do not stall because of the software. They stall on unclear requirements, messy data and teams that were never trained. We run implementation in clear phases, with a signed-off output at the end of each one, until your team actually works in the system.
ZATCAWhatsApp APIWhat does ERP implementation involve?
ERP implementation is the project that turns a product such as Odoo, SAP or Microsoft Dynamics into a system that actually runs your company. It covers documenting your document cycles, configuring the system around them, migrating your data, acceptance testing, staff training, then go-live and follow-up.
Most failed projects do not fail because of the software. They fail because requirements surfaced late, data was moved without cleaning, or a team was never trained on its part. That is why we spend enough time on analysis and design before any configuration.
In the Saudi market, local requirements are settled from the start: e-invoicing in both its generation and integration phases, a chart of accounts aligned with the Kingdom's accounting and tax rules, payroll linked to GOSI and Mudad, and integration with local payment gateways.
- Platforms
- Odoo, SAP Business One, Dynamics 365
- Phases
- Discovery, design, build, data, testing, launch
- Typical timeline
- 6 to 12 weeks for a mid-sized project
- Deliverables
- Configuration document, reconciliation report, user guides
- Training
- In Arabic, by role
- After launch
- On-site hypercare, then a support agreement
Why ERP implementations stall
The same causes show up in most companies, and every one of them can be prevented at the start.
Requirements found too late
Core needs surface after configuration, so work is redone and go-live slips.
Old, messy data
Duplicate items and unreconciled balances move straight into the new system.
A team that never bought in
Without role-based training and follow-up, people return to the old way of working.
Go-live with no fallback
A one-day cutover with no parallel run or fallback plan puts operations at risk.
How we run implementation
A phased method. Each phase ends with an output you review and sign off before the next one starts.
Fit-gap analysis first
We compare your processes with the standard system and separate what needs configuration from what needs development.
Signed-off configuration
Chart of accounts, warehouses, permissions and approval flows are documented before we build.
Data cleaned before it moves
We remove duplicates and reconcile balances with your finance team before any migration.
Acceptance tests on your scenarios
Your team runs real business cycles on the test system and signs the acceptance record.
Role-based training
Accountants train on their screens, storekeepers on theirs, with short Arabic and English guides.
Hypercare after launch
Our team stays through the first full operating cycle and resolves issues as they come up.
What you get
A go-live date you can keep
Scope is defined and signed off up front, so the plan does not shift with every meeting.
Correct opening balances
You start on the new system with numbers you trust.
A team that uses the system
Everyone knows their part, and side spreadsheets do not come back.
Full documentation
Every setting is documented, so the system never depends on one person.
What implementation covers
Configuration
- Company and branch structure
- Chart of accounts and taxes
- Warehouses and items
- Permissions and approvals
Data
- Ready migration templates
- Cleansing and de-duplication
- Opening balances
- Post-migration reconciliation
Quality
- Written test scenarios
- User acceptance testing
- Parallel run when needed
- Cutover and fallback plan
People
- Training per role
- User guides
- Key users inside your company
- Support for the first cycle
Saudi requirements in every ERP implementation
They go on the discovery checklist at the first meeting, whatever the platform.
E-invoicing (ZATCA)
Phase 1 to issue invoices from the system, and phase 2 to connect it to FATOORA by your company's wave, with every invoice and note type tested.
VAT
Taxes set on items, customers and suppliers, with a report that matches the return form.
Books and chart of accounts
A chart of accounts and entries aligned with the Kingdom's accounting and tax rules, with cost centers for branches and projects.
GOSI and Mudad
GOSI contributions in the payroll, and the wage protection file for your bank and Mudad.
Muqeem
Iqamas and expiry dates tracked on employee records, with a Muqeem link where needed.
Local payment gateways
mada, Apple Pay, STC Pay and instalment services, with collections matched to invoices.
Implementation phases
Odoo, SAP or Microsoft Dynamics?
We implement all three and recommend one after discovery. This is a general picture of the differences.
| Odoo | SAP Business One | Microsoft Dynamics 365 | |
|---|---|---|---|
| Usually fits | Small and mid-sized companies | Mid-sized trading and industrial companies | Mid-sized and large companies on Microsoft |
| Licensing | Free (Community) or subscription (Enterprise) | Per-user license | Monthly per-user subscription |
| Implementation time | Usually the shortest | Medium | Medium to long |
| Customization | Open-source Python modules | Add-ons through the SDK and partners | AL extensions and Power Platform |
| Arabic and localization | Arabic interface and Saudi localization | Through local partners | Through local solutions and partners |
| Hosting | Odoo cloud or a private server | Private server or partner cloud | Microsoft cloud |
The picture depends on the version, the local partner and your scope. We give a written recommendation after comparing your actual needs.
How long does an ERP implementation take?
General estimates to help you plan; we commit to an actual timeline after discovery.
One branch, a few modules and users, and simple data.
Several modules and branches, with FATOORA, POS or a store link and opening balances.
Several companies, manufacturing or contracting, with integrations, custom development and a phased launch.
What drives the timeline and cost?
- The platform, its license cost and the number of users.
- The number of modules, branches and companies.
- The quality of current data and how much cleaning it needs.
- The number of integrations and custom development.
- How quickly decisions are signed off on your side.
- The scope of training and post-launch support.
Implementation situations we handle
Moving from Excel to ERP
A company run on spreadsheets needs more data cleansing and training than configuration, and we plan for that from day one.
Replacing local accounting software
We move full history or balances only, as you prefer, and run both systems in parallel for a month when needed.
Rescuing a stalled rollout
We review what was built, decide what to fix and what to redo, and finish under a new plan.
Adding branches or companies
We extend the live system with new branches and permissions without stopping work.
Implementation models by industry
Distribution and wholesale
Several warehouses, sales reps and price lists.
Retail
Branches, POS and central stock.
Manufacturing
Bills of materials, production planning and quality.
Contracting
Project accounting and progress billing.
Professional services
Contracts, timesheets and recurring billing.
Healthcare
Medical warehouses and batch tracking.
Available integrations
FATOORA platform
E-invoicing switched on as part of the rollout.
Stores and POS
Sales and stock linked from day one.
Banks and gateways
Payment settlement and collections.
Attendance devices
Fingerprint data flowing into payroll.
Systems you keep
Connected through APIs.
Reporting
Power BI or in-system dashboards.
Technologies and platforms
We implement on the platform that fits your size and operations, and recommend it after the fit-gap analysis.
An ERP team led by experts who know the Saudi market
For more than 15 years we have analyzed how companies work and implemented ERP systems around it. Our team is led by consultants who combine accounting, operations and software, so they speak the language of the CFO, the warehouse manager and the developer at once.
- Business analysis before choosing a system, not the other way round
- Hands-on experience with Odoo, SAP, Microsoft Dynamics and custom systems
- Projects delivered in Saudi Arabia and the Gulf with ZATCA, GOSI and Mudad requirements
- Arabic training and support from the same team that delivered the project
- ERP experience
- 15+ years
- Delivery platforms
- Odoo · SAP · Dynamics
- Project coverage
- Saudi Arabia & Gulf
How to choose an ERP implementation partner
Questions that reveal how ready a team is before you commit.
- A written method with phases and deliverables
- Ask for a plan showing what is delivered at the end of each phase and who signs it off.
- Projects delivered in your industry
- Industry experience shortens analysis and surfaces special cases early.
- A data migration and testing plan
- How will data be cleaned, and how are opening balances reconciled before go-live?
- A launch and rollback plan
- What happens if something breaks in week one? A good plan answers before launch.
- Training and support in Arabic
- Role-based training, user guides and an agreed response time after launch.
Have this ready before you contact us
It helps us estimate the scope from the first session.
- Your business: trading, contracting, manufacturing, services.
- The expected number of system users.
- Number of branches, warehouses and companies.
- Your current system and how much data it holds.
- Preferred platform, if any: Odoo, SAP or Dynamics.
- Your target go-live date.
Plan an ERP rollout without surprises
Tell us which system you chose or are considering, and how many branches and users you have. We will send an initial phase plan.
What happens next
- We review your requestAn ERP consultant reads the details and notes what needs clarifying.
- Intro sessionA call or meeting to understand your operations and current systems.
- Written proposalScope, phases and cost in one clear proposal.
Frequently asked questions
Did not find your answer? Talk to an ERP consultant directly.
How long does ERP implementation take?
It depends on modules, branches, data volume and integrations. We set the timeline after discovery and hold to it with a signed-off phase plan.
Which platforms do you implement?
Odoo, SAP and Microsoft Dynamics 365, plus custom systems. We recommend a platform after the fit-gap analysis and a running-cost comparison.
Will operations stop during implementation?
No. Configuration and testing run on a separate environment, and cutover happens on a planned date with a fallback plan and a parallel run if needed.
What do you need from our team?
A key user from each department to join workshops, test and sign off outputs, plus a project owner on your side who can make decisions.
Is e-invoicing included?
Yes. We switch on e-invoice issuing and prepare the FATOORA connection. Final approval happens through the platform's tests on your company's account.
We already had a failed rollout. Can you help?
We start with a review of the current state, report what can be kept and what must be redone, then plan the rest of the implementation.
What are the steps of an ERP implementation?
Six phases: discovery and documenting document cycles, solution design and the configuration document, configuration and development on a test environment, data migration and reconciliation, acceptance testing and training, and finally go-live with hypercare.
Can the system be rolled out in phases?
Yes. We usually start with finance, sales and inventory, then add payroll, manufacturing or new branches in later phases, so the team does not absorb all the change at once.
How is data migrated from the old system?
We extract customers, suppliers, items and balances, clean duplicates and gaps, import them into a test environment, then reconcile balances with your accountant before they are approved for production.