How Much Autonomy Should an AI Agent Have in Your Warehouse?
Quick answer. An AI agent in a warehouse needs three things defined before it goes live: what it may execute on its own, what it must recommend before acting, and what it must always hand to a human. That definition is the work most teams skip, and it is where the operational gap originates.
At a Glance
- 88% of organizations regularly use AI in at least one business function, and 23% are scaling an agentic AI system somewhere in the enterprise. (McKinsey, The State of AI in 2025)
- 51% of respondents whose organizations use AI report at least one negative consequence, with inaccuracy the most commonly cited. (McKinsey, The State of AI in 2025)
Adoption is broad, scaling is narrow, and inaccuracy is already the most common problem organizations report. Defining where an agent's authority ends, before it goes live and not after, is a decision leaders can get ahead of. Treating it as an operating model choice, not a technology setting, is what makes bounded autonomy work.
The Autonomy Question Nobody Resolves Before Go-Live
Warehouse teams are running AI agents today across receiving, wave planning, carrier selection, slotting, and exception handling. In many of those deployments, the boundary between what the agent decides on its own and what it hands to a human was set by the vendor's default configuration. Vendor defaults are generic by design and are not calibrated to your operation's risk. A setting that looks conservative during a pilot can authorize consequential calls in production at the speed of software, not the speed of a morning walkthrough.
The organizations getting measurable results from agentic AI are not always the ones with the most sophisticated models. They are the ones that answered the decision-rights question before the agent went live.
A useful reference point is how the same principle was applied before agents: a custom WMS deployed across 60 3PL facilities, with exception-handling logic defined by the operation, not inherited from a platform default. For the broader sequencing of automation investments, see Supply Chain Strategy with Automation: A Practical Framework. For the data and operating-model foundations beneath agentic deployments, see our earlier piece on agentic AI readiness.
Defining the Terms
Bounded autonomy is a formally defined set of constraints that governs which decisions an AI agent may execute independently, which require human confirmation before execution, and which must always be escalated regardless of the agent's confidence level.
A decision-rights framework is the operational document that assigns each category of warehouse decision to one of three tiers, with specified financial thresholds, volume parameters, and escalation conditions.
Decision rights in a warehouse have always existed. Supervisors carry them. The question of who can authorize a short-ship, override a receiving variance, or release a held load is not new. What changes with agentic AI is that the agent needs those same rights codified explicitly, because it cannot read organizational context or ask a floor manager before acting.
The Three-Tier Decision-Rights Framework
Tier assignment is based on financial exposure, reversibility, downstream impact, and compliance relevance, not on the agent's confidence score.
- Cycle count adjustment within pre-defined tolerance bands
- Wave release when labor, equipment, and dock availability meet pre-set thresholds
- Carrier selection within pre-approved rate cards
- Replenishment trigger for high-velocity SKUs within approved reorder parameters
- Receiving variance decisions that exceed the defined tolerance band
- Priority order insertion that disrupts an active wave already in progress
- Carrier re-tender within a pre-approved spot rate ceiling (spot rates vary by market, unlike contracted rate cards)
- Any decision that modifies a confirmed customer-facing commitment, including short-ship authorization
- Vendor claim processing above a defined dollar amount
- Regulated product decisions, compliance holds, or quarantine releases
- Any exception that has no precedent in the historical decision log
Calibration signal: override rate. As an Everest rule of thumb, if managers override Tier 2 recommendations more than 30% of the time, the threshold boundary is mis-calibrated. The tier assignments need revision, not just a log review. A very low override rate is not proof that the boundary is right either, since it can also mean recommendations are being approved without real review.
Where This Gets Missed
Five mistakes undermine bounded autonomy:
Keeping the vendor's default settings
A default reflects no knowledge of your financial thresholds, your customer commitments, or your compliance obligations. The boundary has to be set by the operation, then configured into the platform.
Assigning tiers by the agent's confidence score
Confidence describes how certain the model is, not what an error would cost. A decision with high exposure or limited reversibility belongs in a higher tier however confident the agent is.
Not tracking override rates
Without the override rate, nobody can tell whether the Tier 2 boundary is set correctly. Gaps then surface through production incidents instead of through calibration.
Widening the boundary too early
A good period is not a mandate to expand. Tier 1 should grow through the documented process described below, not on the strength of recent results.
Letting the agent act on stale data
A boundary assumes the agent can see the current state of the operation. When inventory positions, dock status, or labor capacity are out of date, a well-drawn tier becomes an unsafe one.
Case Study: The Same Principle, Applied Before Agents
Custom WMS Across a 60-Facility 3PL Network | Seasonal Retail, North America
This engagement predates the agentic use cases above. It shows the decision-rights principle applied to a warehouse management system.
A seasonal retailer operating across 60 distributed 3PL facilities could not find an enterprise WMS that handled its specific exception types within acceptable boundaries. Mis-sorts, blind receipts, and unlabeled cartons required decision logic that generic platforms calibrated to standard warehouse archetypes simply did not accommodate.
Everest built a custom SaaS WMS calibrated to this client's exact workflows and seasonal rhythms. Exception-handling logic was defined by the operation, not inherited from a platform default. The system knew precisely what to resolve autonomously, what to surface to a supervisor, and what to hold, before it went live at peak season across all 60 facilities. That is the same three-way split the tiers above formalize for an AI agent.
Source: Everest Technologies. everesttech.com/case-studies/seasonal-retail-warehouse-execution
Widening the Boundary Over Time
The initial framework is a starting point, not a permanent configuration. As override patterns stabilize and the exception log matures, Tier 1 can expand. The process matters as much as the boundary itself:
Set a 90-day observation window before adjusting anything. Widen only after the exception log has stabilized and the override rate has held consistent for at least 30 consecutive operating days, across a full operating cycle that includes non-peak periods.
Move one process at a time from Tier 2 to Tier 1. This isolates the effect and makes calibration straightforward.
Require a formal sign-off for each expansion. Operations, finance, and compliance should approve it and the process should be documented.
Do not change tiers immediately before or during peak. Stable results at peak show that the current boundary holds under stress. They are not, by themselves, a reason to widen it.
Where Everest Can Help
Building a decision-rights framework before an agentic deployment is straightforward when the right people are in the room. The harder part is knowing which questions to ask, which exception types carry the most risk, and where the integration layer will surface gaps that change the boundary. That is where Everest Technologies fits in. As a Manhattan Associates Platinum Partner with 300+ warehouse management system go-lives, Everest works across the platform, the integration layer, and the operation itself.
Before the platform conversation starts
Everest maps current decision flows, identifies who owns each exception type today, and establishes the financial and volume thresholds that will define tier assignments. That work produces a decision-rights document that goes into implementation rather than getting built retroactively from production incidents.
At the integration layer
An agent's boundary is only as reliable as the data it reads. Everest's integration work ensures the signals the agent acts on, including inventory positions, dock status, and labor capacity, are accurate, current, and consistently sourced. An agent acting on stale data is operating outside its actual boundary regardless of what the framework says.
After go-live
The override rate does not manage itself. Everest tracks decision-rights performance against baselines set before go-live, surfaces calibration signals, and supports the structured process for expanding Tier 1 when the operational evidence supports it.
If an agentic deployment is in planning or a current one is generating more exceptions than it resolves, the decision-rights framework is the right place to start. Everest Technologies is glad to walk through what that review looks like.
Let's talk about your warehouse autonomy strategyCommon Questions
Frequently asked questions
Tier 1 decisions are high-frequency, low-exposure, and correctable within the same shift at limited cost. The agent acts and logs. Tier 2 decisions carry moderate financial exposure, downstream dependencies, or exposure above the Tier 1 threshold. The agent recommends, and a human confirms before any action is taken. The tier assignment is based on exposure and reversibility, not on the agent's confidence score.
The recommended minimum is a 90-day observation window, with the override rate holding consistent for at least 30 consecutive operating days, across a full operating cycle that includes non-peak periods, before any boundary change. Tiers should not change immediately before or during peak. Stable performance under stress is evidence the current boundary holds, not, by itself, a reason to widen it.
Ownership typically sits with the VP of Operations or the equivalent supply chain leader, with sign-off required from Finance and Compliance for any change to tier boundaries. The framework document is not an IT artifact. It is an operating model document. IT implements what the framework specifies; it does not define the thresholds.
Vendor defaults are generic by design and are not calibrated to your operation's risk. The decision-rights framework review maps your actual decision flows against whatever the vendor has configured and adjusts thresholds to reflect your operation, not the vendor's reference model.
Sources
- McKinsey & Company. "The State of AI in 2025: Agents, innovation, and transformation." McKinsey Global Survey. November 2025.
- Everest Technologies. Seasonal Retailer Deploys a Custom-Built WMS Across 60 3PL Facilities. everesttech.com/case-studies/seasonal-retail-warehouse-execution