Skip to content
All results

Technology consulting

Core operations are moving into one ERP — and the team is already seeing the difference.

A printing manufacturer, EgyptManufacturingEgypt

Under NDA.

The manufacturer had commercial, purchasing, inventory, production and finance processes operating with too much fragmentation between teams. Sahla is implementing Odoo in phases, starting with core operational structure and progressively moving departments onto a shared system.

The result

Core departments on shared ERP path
from0 departmentsto5 core functions
implementation phase
ERP operating model
fromfragmented processesto1 shared system
during phased rollout

Project is still in progress. Metrics describe implementation scope and early outcomes, not final post-go-live performance.

Who they are

An established Egyptian printing manufacturer with operational complexity across sales, purchasing, inventory, production and accounting.

Before the project, important operating information was distributed across separate processes and people, making coordination between departments harder than necessary.

The problem

The business lacked one dependable operational picture.

Teams relied heavily on manual coordination, information had to be followed up across departments, and process variations had accumulated over time. Moving directly into ERP configuration without resolving those differences would simply have reproduced inconsistent processes inside a new system.

Our approach

Sahla started with workflow discovery and scope alignment before configuring the ERP.

Together with the client's team, Sahla documented how sales, purchasing, inventory, production and financial processes actually worked, identified workflow variants, challenged unnecessary exceptions and translated the resulting operating model into Odoo.

The rollout is phased so each core process can stabilize before additional automation and integrations are introduced.

The results

The project is still underway, but the client is already seeing a more structured operating environment.

More information is beginning to live inside one system, departmental workflows are becoming easier to follow, and management is gaining a clearer shared picture of operations rather than depending entirely on manual follow-up.

Honest caveats

Manufacturing ERP projects expose process ambiguity very quickly.

Several issues that initially appear to be software requirements are actually operating decisions: who owns a step, when inventory moves, which variant is legitimate, and which exceptions should continue to exist.

Those decisions have to be resolved with the business rather than hidden inside customization.

  • Timeline: Discovery → kickoff → phased configuration → rollout in progress
  • Stack / tools:
    • Odoo
    • CRM
    • Sales
    • Purchase
    • Inventory
    • Manufacturing
    • Accounting
    • Python

We are already seeing a difference in how the operation is structured. Information is easier to follow and teams are starting to work from the same picture.

Management · Under NDA.

Facing something similar in your operation? Bring it to us.

Forty-five minutes with a consultant on the decision you are trying to get right, then a written view of whether data you already hold can support it.

We use privacy-friendly analytics by default. May we also use cookie-based analytics to understand how the site is used? Privacy Policy