We had a client in Dongguan who took on a beauty brand warehouse in March 2025. Three weeks after go-live, the whole operation stopped for a night over one question of WMS user permissions and roles. An operator who had been on the job for less than two weeks wanted to delete three orders he had created by mistake. He ticked one box too many, the select-all box followed, and 312 outbound orders disappeared in one click. Pick lists were already printed. The floor kept shipping while the system could no longer find the orders, and the customer service phones never stopped ringing. That evening the brand sent an email. Its first question was not about compensation. It was why anyone in the warehouse could delete an order.

The bill is the reason I still tell this story in sales meetings. Of the 312 deleted orders, 196 had to ship the same day. The warehouse called in 14 people to rebuild the orders by hand and did not finish until 2 a.m. Overtime, re-shipping, and service vouchers came to 48,000 yuan. The heavier cost came after that. The brand deducted 8 percent from that month's service fee, about 60,000 yuan, and changed the renewal from one year to three months at a time. Total damage: 108,000 yuan. The annual software fee for that warehouse was 96,000 yuan. One bad permission cost more than a year of the system itself. The vendor's answer was that the system was designed with two levels, admin and operator, and nobody had asked for anything finer. That answer was technically true. The mistake was ours, for treating permissions as a checkbox in the contract instead of a negotiation point.

One deleted batch cost more than a year of software fees

Deleting an order is not like deleting a file. Inventory has already been allocated, picking tasks released, and waves planned. Delete the order and every link after it breaks. Some warehouses try to recover the records from the database, but in practice the recovered order numbers, statuses, and batch assignments rarely line up again.

I asked that operator what happened. He said he did not mean to do it. The delete button sat in the bulk-action bar, one click, no second confirmation, and nobody had told him that button was off limits. I believed him. The worst permission design puts a dangerous action where a new hire's hand naturally lands and then blames the person for touching it. Someone two weeks into the job should never have held the power to delete orders, and the system should never have offered it to him.

A second client showed the other side of the same problem. In January 2026, a 3PL warehouse in Guangzhou that handles phone accessories found a shortage of 217 earphones in a stocktake. It took three days to trace. Two supervisors had been adjusting inventory on their own. One changed 120 units and wrote down damaged goods. The other changed 97 units and wrote down customer returns. Neither adjustment had an approval, a photo, or a linked document. The system log showed only an account name and a time. When the brand asked for proof, the warehouse had nothing to show and absorbed a 32,000 yuan loss itself. The client stayed, but the rate came down. The brand put it plainly: if you cannot tell me who changed my stock, how can I trust you with high-value goods.

WMS user permissions and roles: start with this matrix

Two levels are not enough. Permissions have to be split by action and by risk. The actions that matter are changing inventory, deleting orders, moving stock between locations, and seeing cost prices. Each one needs its own owner.

This is the table I now bring to every negotiation. Use it to audit your own system. Any empty cell is a gap to close before you sign.

Role Change inventory Delete orders Move stock See cost prices Approve adjustments
Operator No No Only run assigned tasks No No
Warehouse lead Request only, no direct change Request only, no direct delete Can start, needs review No Review own team only
Warehouse manager After approval After approval Can approve Own warehouse average only Can approve
Customer service / sales No Request void, manager approval needed No No No
Finance / client contact No No No Settlement price only View records only
System admin No direct change to business data No direct delete of business orders No No Manage accounts only

The row most people skip is the last one. A system admin manages accounts. The admin does not touch business data. Open that door and you have handed out a master key. I have seen warehouses where one shared admin login ends every investigation at the same account, and nobody can tell who actually did anything. The first step in any permission scheme is one person, one account, one role. Disable the account on the day someone leaves. Never share passwords. It sounds basic. Fewer than half the warehouses I visit actually do it.

Here is the counterintuitive part: tighter permissions do not always mean safer operations. Some clients insist that every adjustment needs their own approval, with three layers of sign-off. On the floor it is unworkable. Goods wait to ship, the system waits for approval, and the operator's shortcut is almost always sharing the warehouse manager's login. Once an account is shared, the audit log is worthless and the whole grading scheme collapses to zero. Good grading does not add locks on every step. It gives the floor the frequent low-risk actions and keeps the rare high-risk ones upstairs. Adjusting three damaged units and adjusting 300 units from a stocktake should never travel through the same approval line. The first can pass with a lead's review. The second needs a manager plus the client.

How to write WMS roles into the contract

In contract talks, permissions are the easiest section to wave through. The vendor says the system supports permission management. The client says good, let's move on. Months later, when something goes wrong, both sides discover that supporting permission management and delivering this table are two different things. Supporting it is a feature on a list. Delivering it means each action can be switched on or off by role, each change leaves an approval trail, and each trail survives an audit.

In negotiation I paste the table above into the contract as an appendix and write down three things. First, which actions need approval, who approves them, and what happens when nobody approves in time. Second, deleting orders and changing inventory must leave a record kept for at least a year: who did it, when, what the value was before, and what it became after. A missing field counts as a vendor breach. Third, how accounts are managed, how fast a departing employee's access is cut off, and who carries the liability when a shared account causes a loss. Three paragraphs in writing beat a hundred verbal promises.

Splitting permissions looks like extra cost: another week or two of implementation, half a day of training. One deletion accident usually costs more than a year of software fees — the Dongguan case ran to 108,000 yuan against a 96,000 yuan annual fee. Permissions are insurance, not a cost line. When you negotiate price, do not only push the software fee down. Ask whether the vendor can deliver this table as written and whether that carries an extra charge. Some vendors quote low precisely because they split fine-grained permissions into a second phase, then charge extra after signing. I have watched that play out too many times.

Next time you negotiate a contract, ask these three questions: how many people have to approve an order deletion, and can the system enforce that number; how does the approval line split between adjusting three units and adjusting 300 units, or do they share one line; and when something goes wrong, can the log name the person, and how long is it kept. If the other side cannot answer, or says we can decide that later, do not rush to sign.

By Susan, 3PL Sales Director