When Odoo fits
Many Moroccan SMEs deploy Odoo, or migrate to it from Excel or Sage, to bring sales, purchasing, inventory, accounting and manufacturing together in a single database, accessible from a browser. In Odoo, an order reserves the stock, triggers the delivery, generates the invoice and feeds into accounting, with nothing keyed in twice.
SADIS, a Moroccan company with its registered office in Laâyoune and an operational office in Casablanca, deploys and configures Odoo, handles the migration of your data from Excel, Sage 100 or an older version of Odoo, then connects it to your other tools.
Odoo is a good fit when you want to cover several functions in one tool and roll it out module by module, aligning some of your practices with the standard. It is less suitable if your accounting and payroll are already well handled elsewhere, if the need is limited to one very specific function, or if nobody in-house can lead the project. In that case, two other options are worth looking at: extending Sage, or developing custom management software.
Community or Enterprise
Odoo Community is open source and requires no subscription. It can be installed on the server of your choice, but some applications are not included. Odoo Enterprise, sold by Odoo on a subscription basis, adds applications, hosting by Odoo and version migration tools; pricing and terms should be confirmed with Odoo.
Scoping and assessment
An Odoo project starts with how you work. We look at how your processes actually run, from quote to payment and from purchase request to goods receipt, including the exceptions nobody ever wrote down. Then we review the tools in place and the exchanges with your accounting firm, your bank, an ordering platform or a field app.
If payroll is to run in Odoo, scoping also checks what the chosen edition and version can produce for Morocco (CNSS and AMO contributions, income tax withheld from salaries) and what will stay in your current payroll software. The link between time tracking, payroll and accounting is described on our accounting and payroll (FR) page.
The outcome is a written scope: modules, edition, data to migrate, connections and the steps left for later.
Configure before developing
Odoo is highly configurable: warehouses, restocking, price lists, taxes, chart of accounts, numbering sequences, access rights, approval workflows. Much of what looks like a specific need can be handled there. Where the gap with the standard is minor, we work out with you whether it makes more sense to adjust the practice.
Accounting and tax settings are configured with your chartered accountant. How fully the Moroccan localisation is covered depends on the edition and the version: it is checked and completed where needed.
Migration and cutover
Migrating data from Excel or old software is often underestimated.
- Inventory Customers, suppliers, items, prices, stock, balances, relevant history.
- Cleanup Duplicates, obsolete items, inconsistent codes, customers without an identifier.
- Trial imports Into a test database, checked by your teams.
- Rehearsal The whole sequence is run end to end before the day itself.
- Cutover Stock and balances brought over as at the cutover date, old tool switched off, work starts in Odoo.
We set the date with you to keep disruption to the business to a minimum, and support your teams in the days that follow, on site or remotely.
A major version migration follows the same logic: data is transformed and custom modules are reviewed, and the further the installation strays from the standard, the more work this takes. An existing Odoo installation can also be kept and cleaned up.
From Sage 100
Moving from Sage 100 to Odoo follows the same sequence, with a few Sage-specific points. Customers and suppliers are brought over with their ICE and payment terms, the chart of accounts is mapped to Odoo's account by account, and opening balances are fixed with your chartered accountant. Relevant history (invoices, credit notes, entries for financial years still open) is either imported or kept in the old Sage database for reference.
The two systems can run side by side during the transition, for example until a financial year is closed. If Sage 100 is well maintained and the need concerns a single function, extending it is often more sensible than migrating: our Sage deployment page and the article Sage or Odoo: choosing an ERP in Morocco (FR) will help you decide.
Custom development
When configuration is not enough, we add custom modules: a pricing calculation, an approval workflow, an extra screen or document, or progress statement calculations in a construction ERP for site tracking (FR). They are kept separate from Odoo's original code, they are documented, and their source code is handed over to you. If the need strays too far from the way Odoo works, a connected business application is a better option than forcing the ERP to fit.
API connectors
We develop custom connectors and REST APIs between Odoo and your other tools. Each exchange is defined in writing: the data concerned, which way it flows, when, and which software is authoritative.
- A B2B ordering platform The catalogue, prices and stock come from Odoo, and orders flow back into it.
- A mobile app or web app For sales reps, technicians or storekeepers.
- Software you keep An accounting package, for example, linked through a bridge that avoids double entry.
On the data side, we work with Odoo's PostgreSQL databases and with the SQL Server databases of connected software.
Purchasing digitalisation
Purchase requests, purchase orders, goods receipts and invoice matching run through the ERP, with approval thresholds. Process structuring and buyer training are described on the quality, ISO 9001 and training page.
DGI electronic invoicing
The DGI is gradually rolling out electronic invoicing (FR) in Morocco. On the timetable, only its official texts are authoritative. An Odoo deployment started today prepares for it: customers' ICE numbers recorded, taxes correctly configured, a controlled invoice and credit note cycle, and the ability to exchange data with an external platform.
Role-based training
An ERP the teams have not taken on board ends up abandoned in favour of the old files. So before cutover, everyone trains on their own cases in a test database: sales reps track their quotes in the CRM (FR), storekeepers receive goods, buyers manage requests for quotation, and accountants reconcile and close the books.
Independent advice
We are not an official Odoo partner or reseller, at any level of its partner programme, and we hold no Odoo certification. What we do is the work around the software, from scoping to maintenance. We also work with Sage and on custom software, and we recommend Odoo when it fits and something else when it does not.
The founders spent six years on freelance assignments within large French industrial groups before founding SADIS in Morocco.
