A warehouse management system is judged on the ordinary day. The pick is directed, the label prints, the truck leaves. That is the demo.
The operating cost lives in the other day: the short pick, the damaged pallet, the label printer that stops at 4:40 p.m., the carrier that rejects a load after the door has closed.
What the vendor's own session page actually promises
Körber Supply Chain runs a supply chain master class series, and its session page for "WMS in the Cloud" is worth reading for what it does and does not claim. The page is authored by Scott Brask, Vice President of Cloud and Security Operations at Körber Supply Chain, and the material reviewed here carries no publication date, so it is treated as undated.
The case it makes is operational and financial: that running a WMS in the cloud can provide flexibility for warehouse operations, help with compliance against operational and data security regulations, and help reduce capital expenditures.
Notice what is not on that list. Exception handling. The vendor argument is about where the system runs and how it is paid for, not about who owns the work when a step inside it fails.
That is not a criticism of the page. It is a description of the category. Platform marketing sells the platform, and the queue at the dock is somebody else's slide.
Where the operational frameworks actually speak
NIST's Special Publication 800-82, now in its third revision, exists because operational technology is not office IT. Its framing is that OT systems carry performance, reliability and safety requirements that differ from those of enterprise IT, and that security controls must be chosen with those constraints in mind rather than imported wholesale.
For a warehouse, that distinction is not academic. A stopped outbound door is not an outage ticket with a workaround. It is trailers in the yard, labor standing, and a customer receiving an apology instead of a shipment.
The NIST Cybersecurity Framework organizes around six functions: Govern, Identify, Protect, Detect, Respond and Recover. The first four get the budget. Recover is where exceptions live, and it is the function most often represented by a phone tree.
CISA's Secure by Design initiative adds the procurement edge. It is voluntary guidance rather than a certification, and its stated position is that the burden should sit with producers rather than with the customers downstream. For a buyer, that translates into a question asked during selection: what will this system record about a failed step, and who can retrieve it later.
Three places the exception queue can live
This section is analysis. None of the three is a vendor recommendation.
Inside the WMS. The platform's own exception screens, its own workflow rules, its own alerts. Cheapest to build, because you are configuring rather than integrating. The constraint is that exceptions crossing a system boundary — a carrier rejection, a supplier short-ship, a customer hold in the ERP — arrive as a note rather than as data.
At an integration layer beside it. A service that receives events from the WMS and from the systems around it, applies a routing rule, and assigns the exception to a queue with an owner. This is where the vendor's own product stops and yours begins, and it needs the discipline of any other integration: named ownership, versioned contracts, and a log that survives a review.
On a human's clipboard. Common, undocumented, and the one that fails silently when that person takes a week off. It is not a strategy, but pretending it does not exist is worse than naming it.
A note is not a workflow. It has no owner, no due time, and no record that outlives the shift it was written on.
Four questions before the next change
- What is downtime worth per hour? Not whether the system is highly available. What one hour of a stopped outbound door costs, so availability can be priced instead of admired.
- Who owns the exception after it leaves the WMS? A named role, not a team. If the answer is "whoever notices," the queue is the clipboard.
- What does the audit record show? The failed step, the system that raised it, the person who resolved it, and the timestamp. Reconstructable from logs alone, without asking anyone present.
- How is a change tested before it touches the floor? Applies to your own routing rules as much as to the vendor's release cycle.
A 30-day check
- Days 1 to 5. For one week, log every exception that left the WMS and how it was resolved. Count the ones that moved by phone, email or verbal handoff.
- Days 6 to 10. For each, name the system of record at the moment of failure. Where no system held it, that is the gap.
- Days 11 to 15. Pick three of the logged exceptions and reconstruct them from logs and records only.
- Days 16 to 22. Estimate the cost of one hour of stopped outbound flow. Use it to price the next availability conversation.
- Days 23 to 30. Write the test plan for one routing change: what you would have to prove before it runs in production.
What remains unestablished
- What any current HighJump or Körber WMS release includes. No product documentation was reviewed for this edition, and no claim is made about module capability, version features or roadmap.
- The date and current status of the Körber session page. The material reviewed carries no publication date, so nothing is asserted about when the session ran or whether the program continues.
- Whether any warehouse operator has measured exception volumes, handling time or availability against these frameworks. No measurement was reviewed.
- Whether agent-based automation changes exception rates in a warehouse. No such measurement was reviewed, and none is asserted.
- Market data. No stock, index or valuation figures were reviewed for this edition.
Evidence notes and limits
Körber Supply Chain's master class session page for "WMS in the Cloud" is the source for the description of that session and its framing: that running a WMS in the cloud can provide flexibility for warehouse operations, help with compliance against operational and data security regulations, and help reduce capital expenditures; and for the attribution of the session to Scott Brask, Vice President of Cloud and Security Operations at Körber Supply Chain. The page reviewed carries no publication date, and the article states that plainly. No product capability, performance figure, customer result or HighJump release detail is drawn from it, and the page is presented as a vendor's own description of its own session.
NIST Special Publication 800-82 Revision 3, Guide to Operational Technology (OT) Security, is cited in paraphrase for two propositions only: that it exists as guidance rather than a certification, and that it treats OT systems as carrying performance, reliability and safety requirements distinct from those of enterprise IT, with controls selected accordingly. No quotation is reproduced, no control identifier is asserted, and no conformity determination is drawn from it.
The NIST Cybersecurity Framework is cited for its six named functions — Govern, Identify, Protect, Detect, Respond and Recover — and for nothing else. The observation that Recover is the least-staffed function is this publication's analysis, not a NIST finding.
CISA's Secure by Design initiative is cited for its voluntary character and for its stated position that the cybersecurity burden should sit with producers rather than the customers downstream. No certification, conformity determination or measured outcome is asserted from it.
No product documentation, contract, audit, incident record, deployment or third-party test was reviewed. The three placements for an exception queue, the four questions and the 30-day check are this publication's analysis. Nothing here establishes that any organization reduced handling time, improved availability or prevented an incident.
The advertisement above is separate from this analysis and is not a source for any claim in it.