Implementing M&C ERP with Fujigo: the working process and what you get

Choosing an ERP platform is only half the story — the other half, and often what determines success or failure, is implementation. Industry data speaks plainly: according to aggregated surveys from Panorama Consulting and Gartner over many years, about 50–75% of ERP projects exceed budget, extend timelines, or fail to achieve expected benefits [1]. The leading causes aren’t technology, but change management, poor data migration, and how to work with the implementation team [2].

This article describes how Fujigo implements M&C ERP — and why the “ready-made business core” method reduces exactly those statistical risks.

Starting with the difference: the business core already exists

An ERP project from scratch usually starts with a long question: “How does your business operate?” — then builds each process, each form from zero. With M&C ERP, the answers for most import business are already in the system: shipments with vessel/port/ETD/ETA, customs declarations, duty and freight allocated to cost, Japanese-style documents, serials and warranty.

Therefore, the first survey meeting isn’t to “ask what you need so we can build”, but to compare your business with the existing core — find the matching parts (the majority) and the differing parts (need adjustment). This method changes the nature of the project: from “build new” to “configure + customize the difference” — less time, less cost, and more importantly, less risk, because the core parts already work and can be demoed from the start.

5-step process

Step 1 — Survey and comparison. The Fujigo team works with the business to understand current processes: ordering, transportation, customs, warehouse, accounting, sales. The result is a comparison document: which business uses M&C ERP standard core, which needs configuration, which needs custom development. Bilingual Vietnamese–Japanese working documents — Japanese staff participate from the start instead of waiting to be “updated later”.

Step 2 — Configuration from existing core. Set up catalogs, permissions, approval workflows, document templates according to the business’s organization. Thanks to Fujigo’s standard DevOps process, demo/project environments are set up quickly — the business has a system to “try it out” early instead of waiting until the end of the month to see the product.

Step 3 — Customize the difference. Specialized business not in the core is built on the Frappe platform in a way that doesn’t break the core — see technical details in Built on Frappe. Each customization part comes with bilingual documentation.

Step 4 — Training and test run. By user role: sales, procurement/import-export, warehouse, accounting, management — each role is trained on exactly the screens they use daily, in their language (Japanese for Japanese staff, Vietnamese for Vietnamese staff). Test run with real data for one cycle before officially switching over.

Step 5 — Post-go-live operations. Incident support, regular platform updates, additional business when the business expands. Because the platform is open source and the core is shared between customers, the core updates customers receive are results validated across multiple implementations, not experiments on your own system.

Three things to ask any ERP implementer

Whichever partner you choose — even if not Fujigo — these three questions help filter most risks early:

1. “When can I see the system actually running?” — if the answer is “after analysis is complete, maybe 6 months”, delay risk is already showing. With an existing core, the right answer should be “right at the first demo”.
2. “Will the customization parts prevent me from upgrading?” — customization by modifying the core is borrowing from the future.
3. “What language will my Japanese staff work in on the system?” — for businesses with Japanese staff, this is the question that determines end-user acceptance level, the top factor in project success or failure.

Conclusion

ERP failure statistics aren’t meant to scare, but to choose the right approach: reduce the “build from scratch” part, show the business the system early, disciplined customization, role and language-based training. That’s how Fujigo implements M&C ERP — and why this entire chain starts with an invitation to try before deciding.

---

Contact us for a demo account of M&C ERP.

---

References

1. ERP Research — “ERP Failure Statistics & Case Studies”: aggregated Panorama Consulting & Gartner surveys, 50–75% of ERP projects exceed budget/timeline/fail to achieve benefits. https://www.erpresearch.com/en-us/erp-implementation-failure-case-studies
2. Kreative Core Tech — 2026 ERP statistics summary: leading causes of failure are poor change management, poor data migration, inexperienced teams; Panorama 2025 records 68% failure-to-achieve-goals rate. https://kreativecoretech.com/erp-statistics