How to choose an ERP in Lebanon

Do you actually need an ERP yet?

You need one when somebody is manually moving data between systems every month and decisions are being made on numbers that are weeks old. If your accountant is happy, you run one location in one currency and stock is a small number on your balance sheet, staying where you are is the right call.

The honest version nobody selling software will tell you: plenty of companies buy an ERP two years before they need one, and spend that time paying for complexity they cannot use. Accounting software plus discipline genuinely works for a while.

The signals that you have crossed the line are specific rather than vague. Not 'we want to be more efficient' but 'the stock figure in the accounts is a guess', or 'we cannot price a job properly because we do not know the landed cost', or 'two branches gave me two different answers about the same item this morning'.

• You have a second location

  The moment stock exists in two places, spreadsheets stop being able to tell you the truth about either.

• You trade in more than one currency

  This is the most common breaking point in Lebanon, and the hardest to work around manually.

• Month end takes more than a week

  Usually a sign that operational data is being rebuilt by hand rather than flowing in.

• Nobody owns the stock number

  If finance, the warehouse and sales each keep their own version, you already have the problem an ERP solves.

What should you actually test in a demo?

Bring your own messy process and ask them to run it. A generic tour proves nothing, because every ERP looks capable when the vendor picks the example. The question is whether it handles the specific thing that eats your week, not whether it has a dashboard.

Prepare three real scenarios before the call. A typical sale including whatever makes yours unusual, a purchase from receipt to payment, and your month-end close. Ask to see each one performed, not described.

Watch how many screens a routine task takes. Software that needs eleven clicks for something your team does forty times a day will be quietly abandoned within six months, regardless of how good the feature list looked.

Ask what the system cannot do. A vendor who says 'everything' is either not listening or not being straight with you, and both are bad signs for the implementation.

What does an ERP really cost you?

The licence is rarely the expensive part. The real cost is your team's time during migration and the productivity dip in the first two months, and that cost is roughly the same whichever vendor you pick. Budget for people, not just software.

Ask any vendor to break the engagement into licence, implementation, data migration, training and ongoing support, and to be explicit about what is included versus billed separately. Vagueness at this stage reliably becomes a change request later.

Then ask the question most buyers forget: how many hours of our people's time do you need, and from whom? An implementation that needs your finance manager for two days a week during their busiest quarter is not the same deal as one that does not.

The honest caveat on cheap options: a low licence cost with a partner-led implementation somewhere else in the world can end up more expensive than a higher licence with local delivery, once you count the coordination.

Should you pick a local vendor or an international one?

It depends on which risk you would rather carry. International platforms give you a bigger ecosystem and a name your auditor recognises. Local vendors give you support in your time zone and a system already shaped around how the market trades here. Neither is universally right.

A genuine argument for international: if a parent company, an investor or a future acquirer expects a particular platform, that constraint outranks everything else on this page.

A genuine argument for local: when a posting breaks two days before a filing deadline, the difference between a vendor eight hours behind you and one in the same city is the difference between a bad afternoon and a bad week.

The question that cuts through it is accountability. With most international platforms you buy software from one company and implementation from another. When something breaks, establish now whose problem it is.

• Ask who supports you after go-live

  The vendor, a partner, or a reseller? Get the name and the hours.

• Ask what happens at version upgrades

  Particularly if the system has been customised for you.

• Ask for a reference in your sector

  Not a logo on a slide. An actual company you can phone.

How long does implementation take?

For a first phase of two or three modules, weeks rather than months is realistic. Full suites across several departments take longer. Most of the elapsed time goes into cleaning and migrating your existing data and agreeing how processes should work, not into configuring software.

The single biggest predictor of a slow implementation is the state of your current data. Duplicate customer records, items entered three times under different names, and an opening stock count nobody trusts will each add weeks, and none of them are the vendor's fault.

Phasing helps more than people expect. Going live with accounting and inventory, running them for a quarter, then adding sales is almost always calmer than switching everything on at once, and it gives your team a win early.

What are the mistakes that actually cost people?

Buying on a feature comparison, skipping the data cleanup, not appointing an internal owner, and going live in your busiest month. Those four account for most of the ERP projects that end badly, and none of them are about the software.

Feature lists are the least useful comparison tool available, because every vendor can tick every box at the level a list operates. Two systems can both claim multi-currency and mean completely different things by it.

The internal owner point is the one most often ignored. A project with no single person inside your business who is accountable for it will drift, because the vendor cannot make decisions about how your company should work.

And going live in December, or during your peak season, is a decision people make for budget reasons and regret for operational ones.

• Do not buy on a feature matrix

  Test workflows instead. A matrix cannot show you how many clicks something takes.

• Clean your data before migration, not during

  Duplicates and unreliable opening counts follow you into the new system.

• Name one internal owner

  Someone with authority to decide how a process should work.

• Do not go live in your busiest month

  Pick the quietest quarter you have, even if it delays the start.

Where does Wizard fit into this?

Wizard Cloud ERP is built in Lebanon by Wizard Solutions and sold mostly to trading, distribution, retail and service companies here and in the Gulf. If you are a complex manufacturer or need a globally recognised platform for group reporting, it is probably not the right answer, and we would rather say so on this page.

The cases where it tends to be the right fit are the ones where multi-currency matters, where support hours matter, and where you want one company accountable for both the software and the implementation.

If you are still deciding between approaches rather than vendors, the comparison pages set out where Odoo, SAP Business One, Dynamics Business Central and staying on QuickBooks each make more sense.