WMS User License Audit: Named vs. Concurrent Users — and What to Do When You're Over

I lead with the conclusion, always: if your WMS user license gets audited, the scary part isn't the overage — it's not knowing where it came from. In a named-user model, the money bleeds out through zombie accounts: people who left months ago, their logins still holding a license. In a concurrent-user model, the trap is the seasonal peak — the vendor's script only remembers the peak. When the audit letter lands, don't panic: run your own numbers first, and walk in with evidence. Your spreadsheet beats their script.

I've seen this exact hole three times.

In 2024, a 3PL warehouse in Hangzhou had bought 200 named-user licenses; fewer than 90 people actually logged in. The rest were ex-employees whose accounts nobody had reclaimed. Before renewal, I helped them sweep the list and kill 70 zombie accounts — every one a license paid for annually, for nobody.

The reverse happened in 2023 at an e-commerce warehouse in Shenzhen. They'd picked 80 concurrent users to save money. On the big promotion day, simultaneous logins spiked past 130. Pickers queued at the terminals. When the true-up bill arrived, the per-license price for the overage was noticeably higher than what they'd paid at signing.

Both warehouses fell into the same trap: at selection time, nobody had really understood what the two pricing models actually charge for.

Named User vs. Concurrent User: Where the Money Goes

Read the table by your turnover. A warehouse with three shifts and temp workers cycling through is a bottomless pit for named users — every new hire consumes a license, every departure needs a reclamation. For that shop, concurrent is far easier to manage: one 100-seat pool serves thousands of registered accounts.

Flip it around: a small warehouse with a stable crew on two fixed shifts is cheaper on named users. Don't let the "unlimited registrations" pitch seduce you — if you only have 60 people, paying for 80 concurrent seats is just burning money.

Let's do the math (illustrations, not quotes — check the vendor's latest pricing). A named-user license runs from a few hundred to several thousand dollars per year, depending on vendor and edition. A 200-person warehouse carrying 70 zombie accounts throws away dozens of licenses a year — enough to hire another supervisor. On the concurrent side: 60 online on a normal day makes 80 seats plenty, until the promotion-day peak hits 130 and the vendor bills the overage at a premium. Audit yourself before renewal: an overage you find is "expansion"; one the vendor finds is a "penalty." Different price tag.

The Audit Letter Arrived. Don't Panic: Your 72-Hour License Audit Checklist

Vendor audits rarely come out of nowhere — your contract has an audit clause: how much notice, who can audit, how often, what's in scope, who pays for the audit. Read the contract first, then the letter. Here is my 72-hour checklist, and no step is optional:

Step 1: Narrow the scope. In your reply, pin down three things: which product, which legal entity, which time period. If you're a group with multiple companies, don't let the vendor sweep data across the whole group. Narrower is better.

Step 2: Sign a confidentiality agreement and name a single point of contact. All audit data flows through that one person — no department hands over its own numbers on the side. Once everyone's speaking with different figures, you lose the reconciliation.

Step 3: Review the data-collection script before it runs. The vendor will ask you to run a script pulling login logs and concurrent peaks — read it first: what exactly is it counting? Logins, or deduplicated users? Is the peak measured in five-minute windows or by the second? I've seen this hole three times — at an auto-parts warehouse in Suzhou in 2022, the script counted API service accounts as "users" and conjured 40-plus phantom named users. They nearly paid an extra year of licenses for accounts that had never been human.

Step 4: Run your own numbers first. Pull the login logs and recalculate per the contract's definitions: in named-user mode, strip departed employees, service accounts, and test accounts; in concurrent mode, recompute the peak with the contract's measurement window. Now you know where the gap is.

Step 5: Reconcile line by line, challenging every discrepancy with your own evidence. The vendor says you're 50 over; you bring the termination list and the reclamation log and walk through them one by one. Anything where their methodology differs from the contract's definitions goes back.

Step 6: Before any settlement, it goes past the person with signing authority. A sales rep's verbal discount promise is worth nothing. It counts when it's on paper and signed by someone authorized.

You're Over Your User License Limit. Three Ways Out

If you're genuinely over, don't stonewall. Three paths:

First, true up — buy more. Right for warehouses that truly need the seats. One line to remember: bundle the true-up with your renewal. Buying overage licenses standalone is the most expensive way; rolling them into the next term brings the unit price down. And ask: is the true-up billed retroactively from the months you exceeded, or from the purchase date? Those two calculations can differ enormously.

Second, kill the zombies. Right for named-user shops. Pull every account with no login in 90 days, send the list to department heads, reclaim the departed, disable the long-idle. That's how the Hangzhou 3PL cut 70 licenses in 2024 — not a dollar extra, audit passed. Make it a quarterly routine, not a fire drill when the letter arrives.

Third, negotiate at renewal. Counterintuitive, but true: the audit letter isn't bad news — it's renewal leverage. The vendor audits to sell you more, not to kill you. Walk in with your own numbers and a clear expansion plan and you're driving. A script that works: "Our self-audit shows 30 concurrent seats over, but automation goes live next year, picking headcount drops 20%, so we need only 15 more — sign us for three years at that number, or we evaluate your competitor." The rep wants the renewal, not a lawsuit.

One trade-off, honestly: concurrent is cheaper, but a queue at login means a stopped pick line. Some warehouses squeeze their concurrent count, and on promotion day the 101st login gets refused while pickers stand waiting at the terminal. The license savings won't cover one stopped shift. Buy at peak plus a 20% buffer, never at the average — a standing line in my go-live-eve checklist.

Write the License Terms Into the Contract Before You Sign

Finally, selection. Too many warehouses evaluate WMS on features alone and never read the license terms — then the audit letter arrives three years later and everyone acts surprised. My go-live-eve checklist has the customer confirm each of these, line by line:

1. Lock the model in writing: named or concurrent, whether you can switch mid-term, and what switching costs.
2. The audit clause: notice period, maximum audits per year, how scope is set, who pays — I push back on anything under 30 days' notice.
3. The concurrency definition: what window the peak is measured over, whether service and API accounts count as users, whether the test environment counts.
4. Overage handling: automatic true-up or prior notice first, whether the true-up unit price is the contract price or list price, any grace period.
5. Account reclamation: how quickly a departed employee's account must be reclaimed, and whether the vendor accepts "disabled" as "reclaimed."

Only when those are settled is the contract actually read. Feature selection decides how well the system works for you; the license terms decide how much it costs you — and the second bill is usually bigger.

So back to the opening line: an audit overage isn't scary — not knowing where it came from is. This month, do one thing: pull your account list, flag everything with no login in 90 days, and reclaim the departed. Do that, and next time the audit letter arrives, you'll open it with a smile.

By Lin Xiao, WMS Implementation Consultant