Short answer. An ERP is a single base shared by every department: an article, a customer, a supplier exist in it only once, and a sale entered once updates stock, the receivable and the margin. You need one when the same information is retyped in three tools and month-end figures do not agree, not because the company has reached a certain size. Three conditions for success: clean the records before migrating; play your own scenarios before choosing, to count what the software does not do; roll out in waves, starting with sales and stock. Eight months in the example, four waves, each one used before the next.
This page is for the manager of a trading, distribution, manufacturing or service company working with several tools and spreadsheets, and for the founder based in France who wants to read the figures of their company in Algeria without waiting for month end. The definitions quoted come from public sources: enterprise resource planning, the material requirements planning it grew out of, master data, the single source of truth, data migration, phased or big-bang adoption, vendor lock-in. The company, its article with four quantities, its 1,240 records and its calendar are a constructed example. This page gives no prices and does not cover tax, payroll or accounting obligations: see your accountant.
Do you need an ERP? Six signs
The figure contrasts, on six points, a company whose tools are enough and a company for which an ERP becomes useful.
What it is. Enterprise resource planning is the integrated management of main business processes, often in real time and mediated by software and technology. The research firm Gartner is credited with first using the acronym in the 1990s, for a functional extension of material requirements planning, which was born in factories. The word that matters is “integrated”: departments do not share files, they share a base.
The right criterion. It is neither turnover nor headcount: it is the number of times the same data is retyped, and the time spent each month reconciling files. A company of ten people that manufactures, stores and delivers may need one; a company of fifty that sells only services, not necessarily. If only two signs apply to you, a well-kept sales management program is often enough: that is the subject of the page on sales management software.
The same article: four answers, or one
The figure shows the available quantity of one article, according to four tools then in a single base.
Four copies. In the example, on the same morning, invoicing reports 120 pieces available, the warehouse spreadsheet 96, the purchasing one 104, accounting 131. Nobody is lying: each tool keeps its copy, updated at its own pace. The right quantity is found by going to count. A single master. The principle has a name, the single source of truth: structuring data so that every element is mastered, or edited, in only one place. That is the practical definition of an ERP.
What it changes. A sale entered once lowers stock, creates the receivable, feeds the margin and prepares the entry for accounting. A purchase received raises stock and creates the debt to the supplier. Nobody retypes any more, so nobody makes a mistake retyping. The trap. An ERP installed beside the spreadsheets, without replacing them, becomes a fifth copy: the project succeeds on the day the spreadsheets stop.
«An ERP installed beside the spreadsheets becomes a fifth copy.»
An ERP, in five layers
The accented layer is master data.
Master data. It is the data about the business entities that provide context for business transactions: articles, customers, suppliers. An item record carries a reference, a unit, a family; if it exists twice, stock and sales are split between two records, and no figure is right. Flows. One document is born from the previous one: the quote becomes an order, the order becomes a delivery, the delivery becomes an invoice. Nothing is retyped; it is validated.
Modules. Sales, purchasing, stock, production or projects, finance: only those that are used are switched on. A trading company has no need of the production module; a workshop does, and planning there follows the rules described in the guide to production planning. Control. Who enters, who approves, who changed that price: that is the guide to roles, rights and the audit log. Reading. Figures are read from the same base, the same day, as in the guide to the manager's dashboard.
Choosing an ERP, in six steps
The first step is accented: write your flows.
Your scenarios, not the demonstration. Write ten real situations: a sale with a discount and a partial delivery, a return, a supplier order received incomplete, an article sold by the metre and bought by the roll. Ask to see them played, with your records. What the software cannot do is called a gap: count it, then decide, gap by gap, to adapt the software or to change your way of working. Standard or bespoke. Most ERP systems incorporate best practices, and they vary in how conveniently the customer can modify them.
Three families. A package on the market, including suites such as Odoo, which is available in an open-source Community edition and a proprietary Enterprise edition; a package adapted by an integrator; or an application built around your flows, when the gaps are too many on what makes your business. The questions that remain. Where does your data live, and can you take it back whole? Vendor lock-in is the situation of a customer who cannot change vendor without substantial switching costs: measure it before signing. And what the ERP does not replace is connected, as explained in the guide to integrating existing software.
Cleaning the records before migrating
The figure follows a file of 1,240 articles, in three passes.
Why first. Data migration is the process of selecting, preparing, extracting and transforming data and permanently transferring it from one system to another. The important word is “preparing”. In the example, 180 records were duplicates and 150 had not moved for two years: more than a quarter of the file. Imported as they were, they would have distorted stock from day one. In the old tool. The cleaning is done beforehand, where people still know how to read the records.
Three files. Articles, customers, suppliers. For each: merge the duplicates, archive what is no longer used, complete what is missing, then name an owner, because a clean file with no keeper gets dirty again. The full method, with the rehearsal of the switch, is in the guide to taking over your data; the move from old software on one computer, in the guide to migrating old management software.
«You do not migrate software, you migrate data.»
Four waves in eight months, in 2027
Eight months in the example, the first one to frame and clean.
- What the manager receives: the flows written down, three master files cleaned, ten scenarios played and the gaps counted, a reasoned choice between standard, adapted and bespoke, then four waves, each with its spreadsheets closed and its figures read from the base.
- What the company no longer does: retype a sale in three tools, call the warehouse before promising, reconcile files three days a month, buy software on the strength of a demonstration.
- What is measured: number of re-typings per sale, gap between stock shown and stock counted, days to produce the month's figures, spreadsheets still open after each wave.
- What Symloop does: writing the flows, cleaning and taking over the data, the scenarios and the count of gaps, the set-up or the build, the connection to your existing tools, then the roll-out in waves and the measurement.
In waves, not all at once. There are two ways of putting a system into service. Big bang adoption: the new system is adopted instantly, with no transition period between the old and the new. Phased adoption: different parts of the organization are implemented in different subsequent time slots. For a company that cannot stop, the second limits what can go wrong to one wave. The order. Sales and stock first, because that is where the money and the promises made to customers pass; purchasing next; production or projects; finance and reading last, once the figures they read have become reliable.
A wave is finished when it is used, not when it is delivered: the spreadsheets it replaces are closed, and a figure is read in the ERP and nowhere else. Why projects get bogged down. Three causes are to be watched: records imported without cleaning, a scope that wants to cover everything from day one, and teams that keep their spreadsheets “just in case”. All three are dealt with before writing a line of configuration.
- What is ERP software?
- It is integrated management software: a single base shared by sales, purchasing, stock, production and finance. Each piece of data is entered in it only once, and every department reads the same figure at the same moment.
- Does my company need an ERP?
- If the same sale is retyped in three tools, if the stock shown is not the stock on the shelf and it takes several days to produce the month's figures, yes. If one program and a few spreadsheets are enough and the figures agree, no: company size is not the criterion.
- Which ERP should we choose in Algeria?
- The one that plays your ten real scenarios with the fewest gaps on what makes your business. Also look at where your data lives, whether you can take it back whole, who maintains it near you, and whether the screens exist in your teams' languages.
- What is the difference between an ERP and sales management software?
- Sales management software covers selling: quote, order, delivery, invoice, stock, payments. An ERP adds purchasing, production or projects and finance, in the same base. You move from one to the other when the re-typing shifts to those other departments.
- How much does an ERP cost in Algeria?
- It depends on four items: the software itself, by subscription, licence or build; its adaptation to your flows; taking over the data; training and support. Ask for a costing item by item and wave by wave, not an overall price.
- How long does it take to roll out an ERP?
- Eight months in this page's example, in four waves, for a medium-sized company. The first wave, sales and stock, is in service in the third month. The duration depends mostly on the state of the data and the number of gaps to deal with.
- Must everything be rolled out at once?
- No, with rare exceptions. Going live in waves limits what can go wrong to one wave, and each wave delivers something usable. Start with sales and stock, finish with finance.
- Why do ERP projects fail?
- Three causes are to be watched: data imported without cleaning, too wide a scope from the start, and spreadsheets the teams keep on the side. A project succeeds when the old files are closed and figures are read in one place only.
- Can we keep our accounting software?
- Yes. The ERP produces the entries and passes them to your accounting software, by export or by connection. Bookkeeping and filing obligations stay with your accountant, with their tools.
- Off-the-shelf ERP or bespoke?
- A package on the market if your flows resemble those of your sector and the gaps are few. A bespoke build if the gaps concern what sets you apart. Between the two, an adapted package. The count of gaps, on your scenarios, decides.