The launch report says “cut over.” The warehouse still ships from group screenshots. Finance still matches three sheets at month-end. Do not add modules first. Mess has three kinds: nobody walks the system; the system walks but the data is fake; the system does not cover the real exceptions. The medicine differs. Check the list below in floor order. Only then do you know whether to change habit, data, or features.
Are this week’s new orders all in the system check first
Sample the sales group, parcel slips, and outbound paper. If they do not match, nobody is using it — you are not short of features. See If nobody uses the system after launch, was it worth building.
Is the WeChat group still the official intake
The group still takes qty, price changes, and releases. The system is a backfill. See The risk of taking orders and shipping from WeChat groups.
Did accounts go to the roles often done
Training is not use. Check whether last login and the real document time are the same day.
Does stock decrement on outbound, not a month-end edit
If books and floor miss, first look for outbound without a system document. See How a system makes inventory match the books.
Are price changes, stockouts, and returns still verbal
A pretty main path with every exception in the group still feels messy on the floor. Wholesale is in How wholesalers and distributors should string inventory together.
Do sales, warehouse, and finance keep three customer names
One customer, three spellings, and reconcile will be messy. See Sales and finance looking at the same customers and contracts.
Three kinds of mess, three treatments
Unused: close group intake, outbound needs a system document, the owner checks progress in the system. Used wrong: clean customers and items, ban stock edits without a document. Not covered: turn the most frequent exceptions into states — do not buy another ERP. A unused suite looks like “the system is complete, the floor is still messy.” See A packaged ERP nobody uses is almost as bad as having none. Work-order floors also need dispatch to close. See After work orders close the loop, what changes in after-sales and quality.
Diagnosis needs a sample: one warehouse, one sales group, one week of documents. An all-hands meeting gives feelings, not evidence. When DaXi Technology walks the floor we ask for three things: orders in the group export, outbound in the system, and the statement finance wants. The layer that does not match is the change. To look at which layer is messy, go to the Business systems service page and name the industry and the most painful document. The path gap with and without a system is in How the work path differs with a business system and without one. If the old system is already bypassed, decide extend vs. rebuild first. See Should you extend the old system or rebuild it.
Ask three questions before you change a report
“Messy” is sometimes growth while rules still live in three people’s verbal deals. That is not a system failure. It is time to write the rules onto the document. See Why growth requires an operations system of your own. Do not hide bad foundations with a big screen: a pretty dashboard with outbound still off-document only displays the mess more politely. Make one outbound document the fact first. Then efficiency numbers become real.
Three fixed questions beat a workshop: what is this order’s system number; if there is none, why could it ship; who released the exception. If nobody can answer, you are still in the group-ops era. If they can answer but stock misses, clean master data. If they can answer and stock matches, but stockouts and returns still have no state, then schedule phase-two features. Reverse that order and you spend budget on reports nobody clicks. Do not sample the “well-behaved” team. Sample the warehouse with the most volume and the most complaints — that mess is real. One week is thin; sample another. Do not let one polite day stand in for evidence.