Here's my conclusion up front: if your WMS user permissions only have two tiers — admin and operator — your warehouse data security is basically undefended. That sounds harsh. After 30-plus go-live projects, it is simply what I have seen.

Most warehouses treat permissions as something to fix later. At go-live, admin accounts go to three or four people, the floor shares one operator login, and every role ends up in the same permission bucket — until the day something breaks and nobody can tell who deleted the order.

I have seen this exact failure three times. The scripts were nearly identical.

The first was the summer of 2023, at a 3PL warehouse in Ontario, California, serving two clients out of one building: one selling home goods, the other small appliances. One morning, the home-goods client reported that 40-plus units of a bestseller had gone missing, yet the system showed a clean outbound record. After a full day of digging, we found it: a picker for the appliances client had mistyped a client code, picked the wrong client's stock, and then created the outbound order, checked it and confirmed it himself — because his single account carried create, edit, check and confirm rights. Those 40-plus units (illustrative scenario figures) shipped to the wrong customers, took two weeks to chase down, and cost the warehouse a compensation payment. The root cause was not a careless employee. It was a permission design that let one person be both player and referee.

The second case was worse. In early 2024, a fashion e-commerce warehouse lost a supervisor to resignation. In his final week, he used his own account to delete more than 60 pending orders (illustrative scenario figures), a dozen of which had already been picked and were waiting for checking. The orders were gone; the goods sat in the picking area; the system showed no trace at all — because order deletion wrote no audit log and required no second confirmation. His replacement spent three days reconciling physical stock against the system, a week before peak season nearly cut them off at the knees. Afterwards the owner asked me: can the system require two people to confirm a deletion? Yes, I said. But at go-live, you told me to keep it simple.

The third was 2025, at a warehouse handling both brand owners and distributors. Finance found monthly outbound volume and invoiced volume off by nearly a percentage point. The trail ended at a stock controller with edit rights who had been "helping clients hit deadlines" by changing quantities and batch numbers directly on outbound orders, bypassing the checking step. His intentions were good. But once batch data was rewritten, a quality issue could no longer be traced to a specific batch. Good intentions, no brake pedal.

Three failures, one shared root: permissions are a management problem, not a technical one. The system can do far more than most warehouses ever ask it to.

WMS User Permissions, Layered: How to Cut Five Roles

Here is the split I use in most of my projects — five roles:

Picker: sees only their own assigned tasks and confirms picks by scanning, plus raises exceptions. No creating orders, no editing, no viewing other people's tasks, no cost prices or client settlement rates. Some managers call hiding prices from pickers "a lack of trust." I call it least privilege — data a person never uses should never appear in front of them.

Checker: can check orders and report discrepancies, but cannot change pick results. Wrong pick? Report it, send it back for re-picking, or escalate to a supervisor. A checker who edits results is grading their own homework, and the checking step becomes theater.

Stock controller: can move stock, count inventory and transfer goods — but no editing orders, no deleting orders, no changing prices. The boundary matters: they manage where goods are, not what the paperwork says.

Supervisor: can edit orders, approve transfers and handle exceptions — but deleting an order or changing a price needs a second confirmation, ideally from another supervisor or finance. Supervisors hold real power, so every one of their edits must leave a trail.

Finance: read-only on stock and inbound/outbound records, with access to settlement prices and reports — and zero ability to touch any operational document. Finance reconciles; it never operates.

One hard rule runs across all five roles: create, check and confirm must never sit in the same person's hands. This is segregation of duties, and it is the cheapest line of warehouse data security you will ever buy. Warehouses that call five roles "too fiddly" at go-live always end up spending ten times the effort cleaning up afterwards.

Stopping Cross-Client Contamination: Permission Isolation

For a 3PL, cross-client contamination is the nightmare: one client's goods shipped to another client's customer. It costs money at best and the client at worst. WMS user permissions are the fix, and the isolation needs three layers.

First, client-level isolation. Every operator account is bound to a list of clients they may work with. Anything outside that list is invisible — not even searchable. In the 2023 Ontario case, if the picker's account could only see the appliances client, searching the home-goods client's code would have returned nothing, and the contamination would have been stopped at the source.

Second, location-level isolation. Different clients' goods are stored apart wherever possible, and where they must share space, location permissions are split in the system. Picking tasks are only assigned to locations the worker is authorized for. Third, document-level isolation. Every outbound order, transfer and count sheet carries a client identifier, and a client field once set cannot be changed — you create a new document and run the process again.

Build these three layers and contamination becomes vanishingly rare. The cost is two or three extra days of configuration — nothing next to one compensation payment and one lost client.

Overreach and Deletion: Audit Logs and Alerts

Layered permissions prevent problems before they happen. Audit logs let you investigate after. Alerts catch problems while they are happening. You need all three.

An audit log must record five things: who, when, which document, which field changed, and the before-and-after values. Miss one, and the investigation trail snaps. On go-live night, I test it line by line: change a quantity, delete an order, adjust a price, then check the log to see whether the full story can be reconstructed.

Alerts need thresholds. My starting set: more than 3 deletions in one day triggers a supervisor notification; more than 5 edits by one account within an hour auto-locks the document and notifies a supervisor; any edit or deletion at 2 a.m. sends an SMS to the duty supervisor. Thresholds can be tuned to warehouse size, but they cannot be absent. And here is a counterintuitive judgment: the delete function itself is not the problem — deletion without cost is. After an incident, many warehouses want to switch off deletion entirely, but then legitimate voids and duplicates can't be processed either, and staff start tracking them in Excel outside the system. Keep deletion, but route it through approval, log it fully, and make it recoverable for at least 30 days. Every delete needs an undo button.

The Go-Live Night Checklist

I run this list the night before every go-live. In nine out of ten projects, it catches something on the spot:

  1. Create a test account for each of the five roles, and click through every permission: what should be visible is visible, what should not be returns an error.
  2. Use a picker account to try creating, editing and deleting an order — all three must be refused.
  3. Use a checker account to try changing a pick result — refused; they may only report a discrepancy.
  4. Cross-client test: an employee of client A searches for client B's goods — must return nothing.
  5. Edit one order's quantity, then check the audit log — before-and-after values must be complete.
  6. Delete a test order, then check the log — operator, time and order number must all be there.
  7. Trigger an alert: edit orders five times in a row and confirm the supervisor's phone receives the notification.
  8. Check departed staff: accounts of people who have left must be deactivated, not merely re-passworded.
  9. Check shared accounts: any warehouse-wide "generic operator" login must be withdrawn — one person, one account.
  10. Count admin accounts: more than three admins deserves the question — do they all need it?

WMS user permissions are never finished. Go-live is the beginning. Review roles and accounts every quarter: has anyone left without deactivation, do new hires have the right access, has anyone quietly accumulated rights they never use? Warehouse data security is not something you get automatically by buying a system. It is the daily operation of three things — permission design, audit logs and alerts — working together, day after day.

By Lin Xiao, WMS Implementation Consultant