ERP Selection Consultant, Egypt

When the problem is too many proposals, not too few

An Egyptian manufacturer or distributor going to market for an ERP may receive several proposals within a short time. One offers Odoo with a long list of modules, another Dynamics 365 Business Central with a compact scope, a third ERPNext with heavy customization, and perhaps a local product as well. Each looks complete in its own terms.

The first step is to put them on the same footing. I take your requirement list and map every proposal against it, line by line, marking each requirement as included, included with assumptions, excluded or simply not mentioned. Common differences that only appear this way include:

• The tax authority connection quoted separately, or left to a third party.
• Arabic print templates limited to a few documents.
• Data migration covering master data only, with no open balances or history.
• Training for key users but not for the wider team.
• Support starting after an undefined stabilization period.

Once the gaps are visible, I send each implementer a short list of written questions so they can clarify or revise. Only then does a fair comparison of price and fit become possible. If you already hold proposals and want only this part, my ERP vendor proposal review covers it as a smaller piece of work.

Making Egyptian Tax Authority integration a scored test

The Egyptian Tax Authority runs electronic invoicing for business sales and an e-receipt system for consumer sales, applied to taxpayers in stages. Every vendor will say they support it. The selection should find out how.

The written questionnaire and, where a test environment exists, a live demonstration have to cover:

• Is the integration built into the product, developed by the implementer, or bought in from an outside provider that charges separately?
• How documents are digitally signed and who manages the signing arrangement.
• How your items are mapped to the coding the authority expects, and who maintains that mapping.
• How rejected or invalid submissions appear to users, and how they are corrected and resent.
• For retail or consumer sales, how e-receipts are issued from point of sale and what happens when the connection drops.
• Who keeps the connector current as the authority revises its technical specifications.

Which of your sales fall in scope, and when, is a question for your tax advisor; I do not interpret the rules. Their guidance becomes the basis of the demo scenarios. An integration that depends on one person at a small implementer is a risk the scoring sheet should show plainly. The Egypt ERP consultant page gives wider background on the tax authority systems.

Shortlists and demos for manufacturers, contractors and distributors

Shortlists in Egypt follow the shape of the business. Manufacturers usually need bills of materials, production orders and costing that absorbs imported inputs; contractors need project budgets, progress billing and subcontractor control; distributors care about multi-warehouse stock, price lists and collections. Candidates frequently include Zoho, Odoo, ERPNext and Dynamics 365 Business Central, with SAP Business One or a local product sometimes proposed. I record strengths and limits for each without ranking platforms in general.

Demo scripts then use your own data. Typical Egyptian scenarios include:

• Importing raw materials priced in dollars, landing the costs and issuing them to a production order whose finished goods are sold in pounds.
• Raising a progress invoice on a construction or fit-out contract with retention, and submitting it as an e-invoice.
• A retail or counter sale that needs an e-receipt, including what happens offline.
• Arabic invoices, delivery notes and statements, reviewed for wording by your staff.
• A management report showing margin before and after currency effects.

For each scenario, process owners score whether it was handled as standard, by configuration or only through development. For two frequent candidates, the Odoo and Dynamics 365 comparison is useful context, as are my Odoo notes for Egypt and the ERP for manufacturing comparison.

Cost of ownership when part of the bill is in foreign currency

In Egypt, the question is not only how much an ERP costs but in which currency each part is priced. Some subscriptions are set in US dollars or euros, while implementation services may be quoted in pounds, and hosting can be either. When the pound moves, the balance between those elements shifts, and a budget that looked comfortable at signing can tighten quickly.

I lay out ownership cost by driver for each option: subscriptions or licenses, implementation effort, connectors including the tax authority integration, customization, migration, hosting, training and ongoing support. For each, I note the pricing currency and how it is invoiced to an Egyptian entity, then show how the total would change under a weaker or stronger pound. I use no forecasts, only the sensitivity, so management can judge the exposure.

This also affects negotiation. Fixing service rates in pounds for a defined period, agreeing how renewals are priced, or choosing a model with fewer paid users can matter as much as the headline discount. Your finance team and advisors decide how to manage currency risk; my role is to make it visible before the contract is signed. For a general view of what moves ERP budgets, see the ERP implementation cost guide.

Hosting, data protection, contract markup and remote delivery

Hosting decisions need written answers. In which country and data center will records sit, how often are backups restored as a test, how would you export everything if you changed implementer, and how does the arrangement fit Egypt's personal data protection law? Interpreting that law is for your lawyers; collecting each vendor's position in writing, and scoring it, is my part.

Before signing I mark up the preferred proposal and statement of work. I look for the tax authority integration written as a deliverable with acceptance criteria, Arabic templates listed by document, migration of open balances and history defined, training covering every role, a change control process with clear approval steps, and support terms with response commitments. No vendor or implementer pays me anything, whether as commission, referral fee or margin, which keeps the markup firmly on your side.

Everything happens remotely; Cairo working hours overlap comfortably with mine for live sessions, and decisions are captured in documents your team can open at any time. Without written requirements yet? The Egypt ERP business analyst page explains that first step. After the decision, ERP implementation oversight in Egypt follows the build so the evaluated scope is the delivered scope. The Egypt hub and the ERP vendor selection service describe the wider approach.