Implementation leaves a module list: GL, A/R, inventory, production, QC, HR… Open production and the wizard wants routings, work centers, and standard hours first. Make-to-order on your floor does not run that way, so the button stays gray. The floor goes back to WeChat. The owner sees the menu and thinks digitalization is done. The warehouse sees the gray button and knows the system is not theirs.
Why a gray button is as bad as having none
With no system, people know the rules live on people and they still match the sheet carefully. With a dead packaged ERP, responsibility is pushed to “it should be in the system.” Real work stays on the spreadsheet, plus a new delay: “we will enter ERP later.” The path gap is in How the work path differs with a business system and without one. SaaS that misses the floor is a lighter version of the same fail. See When SaaS does not match how the floor actually works. Packaged vs. custom is in How packaged software actually differs from a custom system.
Suites are not unusable. Companies whose finance, tax, and standard inventory match the product do well. The gap is your exceptions: several prices on one order, ship by project, install dispatch, rework splits. Those are not checkboxes. They ask you to change the work to fit the module. If you cannot, the module stays gray. See Should a mid-size company buy ERP first, or start with custom modules.
You already bought the suite. Now what
Keep what works: GL, cash, tax. Build the operations layer on the real path, then write back the vouchers you need. See Do you have to connect finance and the ERP you already run. Do not spend three years finishing master data just to light gray buttons. If the floor is messy, diagnose unused, used wrong, or not covered. See The system is live and the floor is still messy: how to diagnose it. Extend vs. rebuild is in Should you extend the old system or rebuild it.
DaXi Technology does not replace for the sake of replacing. First ask the warehouse where they click to ship today. If the answer is not the suite, do not buy another license. To build buttons the work can click, go to the Business systems service page and say where the suite stalls. Work-order close and dispatch are often the grayest block. See After work orders close the loop, what changes in after-sales and quality.
Accept on outbound, not on modules turned on
The implementer accepts by module. You accept by outbound. Different bars become mutual blame. Write acceptance as “for two straight weeks, every new order outbound from the system,” not “the production module is on.” Gray buttons can stay on the menu as a future option. Do not put them in lesson one, or the floor will think unused features are their fault.
Annual license renewals are the sunk cost suites hide best. After operations move out, manufacturing, HR, and BI suites can often stop. Keep finance. Do not force the shop to light gray buttons because “we already paid.” The demo the owner saw is usually perfect master data the implementer loaded — it does not match your bin names. In evaluation, have them walk one outbound with your real item codes. Gray or not shows immediately. An unused suite occupies the mental slot “we already have ERP,” and the custom work that can actually walk documents never gets scheduled. That wastes a year or two more than having none.