ERP Selection Consultant, Nigeria

Nigerian shortlists by size and sector

The right shortlist in Nigeria depends on what the business does, how goods and money move, and who will run the system internally. I start from those facts rather than a vendor list.

• Small trading and service businesses frequently keep their books in Sage, QuickBooks or Zoho Books with spreadsheets alongside. The question is whether a better-configured accounting tool with inventory and CRM is enough, or whether a full ERP is justified.
• Depot-based distributors and manufacturers tend to weigh Odoo, ERPNext and Nigerian-built systems designed around distribution and point of sale.
• Bigger groups and Nigerian arms of foreign companies frequently bring in Dynamics 365 Business Central, SAP Business One or the parent's standard, and need to confirm availability and localization for a Nigerian entity before demos.
• Oil and gas service companies need contract, equipment and crew costing, which reshapes the list around job management.

Open-source options appeal where subscription costs paid in foreign currency are a concern, but they shift responsibility for hosting and upgrades to you or your implementer. I score that trade-off openly. Platform notes are on the Odoo in Nigeria and ERPNext in Nigeria pages.

Demo scenarios built on Nigerian tax and payments

A generic demo shows a clean invoice paid in full. Nigerian finance teams rarely see that, so the script uses the cases they do see, and each bidder works through them live on your own sample data:

1. Raise a VAT invoice to a customer who pays net of withholding tax, then record the credit note or receipt for the withheld amount when it arrives.
2. Pay a contractor, deduct withholding tax at the rate your advisor specifies and produce the schedule finance needs for remittance.
3. Import statements from several banks, plus a POS settlement and a payment gateway payout with charges deducted, and reconcile them.
4. Buy goods in dollars, record the rate used with the bank document attached, receive them into a depot and show landed cost in naira.
5. Transfer stock from head office to a regional depot, sell from it on credit and block a customer over the limit.
6. Show which customer and invoice fields would feed electronic invoicing, and how the bidder proposes to transmit and handle rejections.

Each step is graded by your process owners according to whether it ran natively, needed setup, relied on an extension or would require custom code. Tax rules and e-invoicing requirements have been changing, so your tax advisor confirms the current position before scenarios are finalized. Results go into the weighting model from my ERP evaluation service, and the ERP business analyst page for Nigeria covers how these needs are written up.

Weighing implementers and dollar-priced proposals

Nigerian proposals are often hard to compare. One implementer prices licenses in dollars and services in naira, another quotes everything in dollars, and another offers a fixed price with assumptions buried in an appendix. Some include hosting, others leave it to you. Without adjustment, the lowest headline figure usually belongs to the proposal that excluded the most.

I restructure every proposal into the same lines: licenses or subscriptions, implementation phases, data migration, integrations with banks and payment channels, e-invoicing connection, training, testing support, hosting and post-go-live support. Every line records its currency, what is included, what your staff are expected to do and what is excluded. Foreign currency lines are flagged so directors can see how the total moves with the exchange rate. Clarification questions go to every bidder at the same time.

The implementer matters as much as the product. I look at team depth on the proposed platform, who would actually work on your project, how they cover depots and branches outside the main city, how they handle staff changes, and whether custom code will be documented and accessible to you. Structured reference calls with similar customers help confirm the picture.

For proposals you already hold, the freelance ERP consultant page for Nigeria and the vendor proposal review page explain the review.

Hosting, power and data protection questions

Where the system runs matters more in Nigeria than in many markets. Head office may have stable power and good connectivity, while depots, plants and field sites rely on generators and mobile data. I ask every bidder how its system behaves during an outage, what staff can still do offline on phones or tablets, and how records catch up once the connection is back.

The hosting options each carry trade-offs. A cloud service abroad avoids running servers locally but depends on internet links. A local data center may give lower latency but needs a strong support arrangement. An on-premise server keeps working on the local network during an internet outage but puts power, backup and security on your shoulders. I compare these openly with your IT team.

Nigeria's data protection law sets rules for collecting, storing and transferring personal data on customers, staff and agents, and some organizations carry extra duties under it. Every vendor receives one written questionnaire covering where data sits, which subprocessors touch it, how access is logged, how backups work and how you would leave. Your legal advisor and data protection lead judge the replies; legal interpretation is theirs, while my job is getting complete answers before signature and scoring them.

Wider design questions for Nigerian businesses are on the ERP consultant page for Nigeria.

Contract points for a Nigerian ERP purchase

Selection is only complete when the contract matches what you tested. The statement of work and support schedule are checked line by line against the demonstrations and your requirements, producing a list of points such as:

• Currency and payment milestones. State which amounts are fixed in which currency, which rate applies to conversions and how milestone payments link to accepted deliverables.
• E-invoicing responsibility. The contract should say who builds and maintains the connection to the tax authority's electronic invoicing arrangements, and how changes are handled.
• Tax configuration. VAT and withholding setup should be configured on your advisor's instructions and accepted through testing, with updates covered by support.
• Bank and channel integrations. Each bank, POS provider and gateway in scope should be named, with its method and testing.
• Code, documentation and handover. Custom work should be documented and accessible if you change implementer.
• Support across locations. Response expectations for head office and depots should be written down.

Drafting the clauses remains with your legal advisor. Once the agreement is in force, my client-side implementation role in Nigeria holds delivery to it. The Nigeria overview describes the remote engagement, run during the hours Nigeria and India share.