Charming Printing shared their Odoo implementation story on LinkedIn. We were the partner on that project, and a client choosing to talk about it publicly means more than anything we could write ourselves.
Why a client sharing it matters
Any implementer can describe a project as a success. The company that lived through it has no reason to, unless it was.
An ERP rollout is disruptive. People change how they work, old habits get questioned, and there is a period where everything feels slower before it gets faster. A company that puts its name to the outcome afterwards is telling you the disruption was worth it.
What the project involved
Charming Printing runs around fifteen offices and factories across America, Asia and Europe, making trim and label printing, packaging and RFID for fashion retail brands. Before Odoo, most sites ran their own systems and Vietnam ran a separate local solution.
The rollout put manufacturing, inventory and sales on one platform. The change their team noticed most was not a feature. It was that staff started setting up their own checks on the workflow, because the data had become reliable enough to act on.
We wrote about the project in more detail in an earlier post.
The part we think about
Multi-site implementations succeed or fail on whether the sites agree to work the same way. The software is the easy half. Getting fifteen locations to accept one way of numbering a product is the half that takes the time, and it cannot be done from outside the company.
Charming Printing’s team did that work. The system just gave them somewhere to put it.
If you are looking at an ERP rollout across several sites and want to talk to someone who has done it, get in touch.
