Skip to Content

Infor M3 CSDE Deployment: Inside GROUPE DARON's experience

October 26, 2026 by
AUTHENTIC GROUP

An interview with Damien PETITJEAN

Transformation Director at DARON GROUP

At the end of January 2026, DARON GROUP deployed Infor M3 CloudSuite™ at its subsidiary in the Congo, following a 15-month project. A look back at a complex digital transformation project in a little-known industry.

Can you introduce yourself, specify your role at IMS and your role in this ERP project?

Damien Petitjean : My department is responsible for the group's transformation in terms of implementing new processes as well as the associated tools. In this project, I had the role of Sponsor as the director of the transformation department. But since I was familiar with M3 and had explored the new features of the Cloud part like the EDA, I was also heavily involved in the project to see and test what could facilitate usage by bringing more ergonomics and customization. All without getting into specifics.

Can you present your group and its activities?

Damien Petitjean : Daron Group specializes in ship chandling, which involves supplying vessels with provisions and other goods. It is essentially a distribution business: we import products or source them locally, store them, and deliver them. We operate in South Africa, Angola, Gabon, Congo, and Mozambique. We also have purchasing centers based in Europe. 

On-site, we have warehouses and cold rooms from which we directly deliver to ships. This concerns both food products — fruits and vegetables, meats, dry goods — and technical products like lubricants, paint, ladders, or ropes. In summary, everything a ship may need when it docks.

What role does Congo play in your organization and why start the deployment with this subsidiary?

Damien Petitjean : As part of our Infor M3 CloudSuite implementation project, we had already deployed an initial Core Model designed for our purchasing centers. With Congo, the objective was different: we needed to build a new Core Model specifically tailored to the ship chandling business, which could then be rolled out across all our African subsidiaries. This involved integrating warehouse management, mobility, order picking, traceability, and the specific commercial requirements of the ship chandling industry.

Historically, our subsidiary in Congo has been our largest, oldest, and probably most mature operation in terms of ship chandling processes. It was established in the 1960s, and Congo was the Group’s main market for many years. It also offered a less complex environment in which to build the Core Model. In Gabon, for example, we also operate a supermarket that will need to be included in the project scope. We therefore wanted to start with a site that would allow us to minimize the factors likely to complicate the configuration of the Core Model. 

Congo thus constituted both a transformation project for the subsidiary and the first step in building a group model.

How did your different entities operate before the implementation of the Infor M3 platform?

Damien Petitjean : Each site operated relatively independently. Each entity had its own database and master data repository hosted on a local server, with no integration between systems. This setup was more a collection of individual entities than a truly integrated operating model at Group level.

The systems were not integrated, and some processes were still carried out outside the software. Order picking, for example, was still a manual process: teams printed picking lists, physically prepared the orders, and then checked off items on paper before shipment.

What were the main operational challenges and difficulties you encountered in managing the group's entities?

Damien Petitjean: We were starting to reach the limits of our old system. We realized that the existing technology no longer allowed us to do everything we wanted or what we envisioned for the future.
 
We increasingly needed to connect our systems, develop and integrate new functionalities (online catalog, BI, automation, etc.). There were also growing requirements for traceability, particularly batch tracking and expiration date management, which were not supported by our previous software.
We did not have a common system, and the sites operated with their own databases and their own references.

The transition to M3 already gives us better visibility into what is happening. This is important because before, we did not have the same level of information and structuring. Reporting is still to be built, but we now know that we have the data and the means necessary to go much further.

Order preparation and processing were particularly structuring processes for our business. We sell to customers but also to boats, and the customer-boat relationship is essential. The same boat can have multiple customers: one for food, for example, and another for technical maintenance. Therefore, we had to succeed in reproducing this logic in M3 without too much disorienting the teams compared to their daily operations.

Why did you choose to deploy Infor M3 and what were the main objectives of the project?

Damien Petitjean : We had already completed an initial Infor M3 project for our purchasing center and needed to develop a new Core Model specifically tailored to ship chandling for our African subsidiaries..

When selecting our ERP, we initially considered solutions designed for SMEs. However, our operational requirements (multi-company, multi-currency, intercompany sales, legal and regulatory constraints, WMS, etc.) quickly led us to consider larger ERP solutions such as SAP, Microsoft Dynamics, and Infor M3. We chose Infor M3 because of its proven track record in the distribution industry and because connectivity tests conducted in Africa showed better results than those of competing solutions, such as SAP and Microsoft Dynamics, particularly given the high network latency across the continent. This was a major factor in our decision.

The objectives were multiple: to replace our historical systems that had become limiting, to digitize processes still done on paper, to automate certain exchanges, to improve traceability, and to structure the data.

What benefits were you expecting from this new project?

Damien Petitjean : We wanted to automate the replenishment orders from African sites to the purchasing centers, digitize the order preparation, and have more precise tracking. We were expecting a solid structuring of our data, an essential condition to implement Business Intelligence (BI) and Artificial Intelligence (AI). We were also expecting more precise tracking of our processes in the warehouse and management of the traceability of our products.

For us, the ERP really constitutes the essential building block: if we do not have a solid structure, we cannot properly develop these new uses.

Why did you choose Authentic for this project?

Damien Petitjean : We had already worked with the Infor / Authentic tandem on our first project for the purchasing center. The relationship had always gone very well, we had gotten to know each other, and we were happy to work together.

We particularly appreciated their ability to adapt to our highly unconventional project approach, as well as the quality of their advice in guiding us towards industry best practices based on their experience with other clients.
We did consult other integrators for comparison, but there was no reason not to continue working with Authentic Group. They already knew our teams and our project, and we were satisfied with their services.

How was the project organized?

Damien Petitjean : For this project, we adopted a highly operational approach. We do not necessarily follow extremely rigid project methodologies, as our main objective is to roll out the solution across all our sites as quickly as possible. Above all, we were looking for efficiency.

We also wanted to have processes in place that we could actually test as quickly as possible. Most issues only become apparent when you start working hands-on with the system. We therefore pushed this approach as far as possible, postponing certain topics that were not essential for go-live so we could focus first on the key business processes

In terms of project staffing, we had learned from our first project, which had essentially been managed by just two of us within the Transformation Department. We therefore expanded the team, with two people on the technical side, two more focused on business processes, one person handling PMO activities, and myself providing support as needed. We also appointed key users and involved local management.

The pace was quite intense. In this type of project, some people can be very busy for several weeks while others temporarily have more time. We therefore sought to develop the versatility of the team and to upskill several people.

Our objective was also to be as self-sufficient as possible. We needed to do things ourselves to understand what could be achieved with Infor M3.

Which processes did you prioritize?

Damien Petitjean : We tackled the data part quite early, as we knew it would take time. Initially, we worked with small datasets, but representative enough for the teams to really envision themselves.

Then, our priority was the entire order processing flow and operations in the warehouses. For the latter, we needed to hold workshops to precisely determine how we were going to operate. The order preparation presented many constraints specific to our business. Therefore, we wanted to secure this operation and avoid disorienting the teams too much compared to how they were used to handling orders daily.

Which processes did you intentionally postpone?

Damien Petitjean : We postponed system integrations, particularly with our purchasing centers, until all order-related processes had been properly defined. Purchase order management was also addressed at a later stage, as it was already included in the purchasing centers’ Core Model and we had a good understanding of how it worked.

We had a general idea of our target operating model, but above all, we wanted to align with Infor M3's standard processes, which are designed for the distribution industry. Our guiding principle, which had already been established during the purchasing centers project, was very clear: no custom developments.

You nonetheless developed your own mobility solution. Why?

Damien Petitjean : We needed functionalities that were not all available in the Infor solution and especially offline operation. In our context, this is essential. We need to be able to work without an Internet connection and then transmit the transaction when the connection returns. Factory Track did not meet this requirement.

We would have preferred to avoid developing our own system, but offline operation was a blocking point. Therefore, we developed our own mobility system, which naturally had to work correctly with the M3 configuration.
 

How did the Authentic teams support you on this project?

Damien Petitjean : Authentic Group provided valuable guidance on business best practices, drawing on their experience with other clients. This was extremely helpful. They also supported us in understanding how the modules work, configuring the system, and addressing areas where we lacked expertise.

The project management on the Authentic side was also carried out effectively. Even when the consultants were not physically present, they remained available to answer our questions and support us. 
As our internal teams were sufficiently self-sufficient, this remote working approach worked very well..

How did you prepare the local teams for this significant technological change? How was the change management handled?

Damien Petitjean : We had anticipated this transition and started preparing our teams two years in advance by introducing handheld barcode scanners and using mobile phones for goods receiving. The objective was to gradually familiarize employees with performing certain operations on mobile devices. This helped reduce the gap when transitioning to Infor M3. The change was significant, so we tried to break it down into several smaller steps, both before and during the configuration phase, to make the final transition as smooth as possible.

For the first deployment, we chose to stop at a process level that would not be too significant. We will then continue to gradually develop the uses to get closer to our target.

What specific challenges did you encounter during this project?

Damien Petitjean : Travel in Congo is relatively complicated. Therefore, we carried out almost the entire project remotely with the Authentic consultants.

We even conducted the testing phase and the go-live without an Authentic consultant on-site, except for Magalie who came for part of the testing phase. Our own team, however, traveled to Congo to support the local users. During the testing phase, the goal was really to verify that the model was functioning. Once this step was completed, we knew that the core of the system was operational, even though there were naturally still elements to correct.

Can a project of this magnitude therefore be primarily conducted remotely?

Damien Petitjean : Yes, but I think there is an important condition: the client-side teams must have a sufficient level of autonomy with the software.

We were quite confident in our level of autonomy. As long as we had the Authentic consultants available to answer our questions and guide us on topics we were not familiar with, it worked very well.
If we had identified significant gaps during the testing phases, we would have considered bringing in Authentic consultants for support. This ultimately was not necessary.

How was user training organized?

Damien Petitjean : Authentic trained us on the ERP modules, and then we trained our users ourselves. We also trained a lot independently, particularly on the EDA and IEC. For the order management part, we used Experience Designer extensively and developed the interfaces ourselves. Therefore, we were directly able to train the teams on their use.

What results have you observed since go-live?

Damien Petitjean : It is still a bit early to really measure time savings since, at the time of the interview, we only have two and a half to three months of hindsight. It should also be understood that a number of operations that were previously performed outside the software are now integrated into the system. Users sometimes feel like they are spending more time in the ERP, which is indeed the case for certain steps.

However, this gives us access to a level of information that we simply did not have before. Some of the benefits are therefore not yet immediately visible to users: they are, in a way, hidden benefits. The integration of financial processes and the ability to access the system easily from anywhere were the positive aspects that users highlighted right away.

What feedback do you have from users about the solution?

Damien Petitjean : Overall, we have positive feedback. Experience Designer has helped us a lot in adapting and optimizing the ergonomics of M3 to our processes and operations. Without this tool, I think user acceptance would have been much more difficult.

What operational benefits are already clearly visible?

Damien Petitjean : In terms of reporting, we have set up something relatively basic but we already have better visibility over all our operations. We now know that we have the means to go much further in analyses and to build a more complete and efficient reporting system.

The gains are also very concrete on the finance side thanks to the direct integration of operations and finance. When an invoice is issued, it now appears immediately in the customer account. Previously, this information was transferred overnight. Today, it is instantaneous, which brings a real gain in tracking. For the CFO, it’s a real plus. We can also link purchase orders to supplier invoices, which was not possible before.

Another important change: users can now easily connect from practically anywhere. Before, they had to be on-site or go through a VPN, with software that became extremely slow remotely. On this point, the teams immediately saw the difference.

Does the new ERP also allow you to respond to new regulatory constraints?

Damien Petitjean : Yes. We are seeing an increasing number of requirements related to electronic invoicing in African countries. It is clear that our previous system would not have been able to adequately support these changes. To implement these new processes, we need a modern, well-structured ERP system..

What benefits do you see at the group level?  

Damien Petitjean : The main benefit is being able to gradually structure the group around common processes and frameworks. We are building a common base of articles, suppliers, and customers. This allows us to move away from a logic where each entity operates independently. This common structure also constitutes the necessary foundation for subsequently developing BI, artificial intelligence, more interfaces, and new services.

Finally, the Core Model must also allow us to quickly deploy new sites. It is a tool designed to support the group's growth.

What was the main success factor of the project?

Damien Petitjean : For me, the main success factor is primarily the human factor. Internally, it clearly relies on the versatility of the team and its level of autonomy in configuring M3.
Then, there is the connection with Authentic and the ability of their teams to adapt to our project operating mode. Not all integrators could necessarily work this way, but the Authentic team has done very well.

What are your next transformation areas?

Damien Petitjean : We have three main priorities: Business Intelligence, artificial intelligence, and greater integration with our customers and suppliers. These are the three key areas we want to focus on moving forward.

What is your assessment of the collaboration with Authentic Group?

Damien Petitjean : At the beginning of the project, we were on a fairly classic launch. It took us some time to adjust and understand each other. Then, we found a way of working that provided us with the minimum necessary framework for project management while maintaining enough flexibility to remain efficient.

Authentic Group helped guide us in the right direction and supported us throughout the project, demonstrating great flexibility and adaptability. We particularly appreciated their responsiveness during the first week after go-live, when we felt fully supported despite working entirely remotely.

What are now the next steps in the group's digital transformation?

Damien Petitjean : The rollout to our other sites. The Core Model developed in Congo was specifically designed to be deployed across our other African subsidiaries. Gabon is scheduled for October 2026, followed by Angola in 2027, probably early in the year. We are aware that this is a very ambitious rollout schedule and that it requires certain compromises, particularly when it comes to consolidating the Core Model. However, the benefits of an ERP system like Infor M3 are a key factor in achieving our Group’s growth and modernization objectives.



" Authentic has guided us a lot on best business practices, particularly relying on their experience gained with other clients. This has helped us tremendously. "

Damien PETITJEAN
Director of Transformation at Groupe DARON

About Groupe Daron

Groupe Daron is a family-owned group of suppliers established in 1959 in Africa. It develops its activities around two main businesses, ship supply (Ship Chandler) and Supply Chain, ranging from international sourcing to solutions for transporting products worldwide.

To learn more: https://www.daron-group.com/fr

About Infor

Infor is a global publisher of industry-specific enterprise applications, deployed in the Cloud, developing comprehensive solutions for the key industries it serves. More than 60,000 organizations in over 175 countries trust Infor's 17,000 employees to help them achieve their business goals.


Share this article