Reuters reported that approximately 3,300 positions will be affected in Uber’s largest workforce reduction since the pandemic. CEO Dara Khosrowshahi said the company is removing management layers, simplifying team structures, clarifying ownership and redirecting investment toward its largest opportunities. Uber itself describes the objective as becoming a “simpler, faster” company. Importantly, Khosrowshahi did not attribute the workforce reduction directly to artificial intelligence.

That distinction matters because the deeper logistics story is not simply about automating individual jobs. It is about reducing the coordination required to make an increasingly complex enterprise operate.

The Coordination Tax

Large organizations accumulate complexity almost naturally. Products, geographies, customers and channels multiply, followed by planners, analysts, supervisors, project managers and functional organizations to manage them. Each addition can make sense individually while the cumulative result is an organization in which a surprising amount of work consists of coordinating other work.

Uber is explicitly attacking that problem. The company says growth brought more layers, more coordination and increasingly fragmented ownership. It is broadening management spans, reducing positions concentrated on coordination and eliminating many “micro-teams” with only one or two reports. Uber says the number of employees seven or more organizational layers below the CEO will decline by 20%, while the number of micro-teams will fall by nearly half.

Anyone who has worked around a large logistics organization should recognize the pattern. A routine transportation exception can generate an alert, an email, a carrier call, another information request, a supervisor escalation, a customer update and eventually a KPI entry explaining what happened. No single step is necessarily unreasonable. The inefficiency lies in the number of people and systems through which information must travel before somebody has enough context and authority to act.

AI agents begin to change that equation. An agent can monitor a transaction, identify an exception, gather contextual information, consult business rules, communicate with other systems, recommend an action and, within defined guardrails, execute it. The opportunity is therefore larger than making every planner or analyst incrementally faster. In some workflows, the larger gain comes from eliminating the handoffs themselves.

This Is a Systems Engineering Problem

This is why I believe much of the current discussion around AI in logistics remains too narrow. We tend to evaluate individual technologies when the more important issue is how those technologies interact with people, physical assets, information flows, decision rights and business processes.

That is the central argument in our recent white paper, Systems Engineering in Logistics. Logistics performance does not emerge from a TMS, WMS, control tower, robotics platform or AI model operating independently. It emerges from the behavior of the larger system.

Uber’s restructuring is a useful real-world example. The company is not simply deploying another AI application. It is reconsidering management spans, operating structures, accountability and capital allocation while introducing increasingly capable digital systems.

The logistics industry has spent decades digitizing individual functions. Transportation received a TMS, warehousing received a WMS, planning acquired specialized applications, customer service adopted CRM platforms, and visibility produced control towers. The technology architecture became more sophisticated, but the organizational architecture often remained substantially unchanged.

AI provides an opportunity to revisit that architecture. If systems can increasingly exchange information, interpret events and execute routine decisions without waiting for a human intermediary, logistics leaders should ask more than, “Which tasks can AI automate?”

A better question is: “Which organizational boundaries exist because humans historically had difficulty coordinating information and decisions across them?”

Uber Freight Is Already Showing Us the Model

Uber’s own freight business provides a concrete example of what that transition looks like.

In its second-quarter 2026 prepared remarks, Uber said Freight is investing in AI capabilities designed to optimize transportation decisions for customers. The company specifically identified earlier detection of shipment risks and automation of routine operational workflows, including responding to shipment inquiries, validating documents and correcting shipment data.

Those may appear to be incremental applications, but they target precisely the activities that generate administrative work throughout transportation organizations. Every automatically resolved shipment inquiry or corrected document can remove an email, a queue, a handoff or an escalation.

The progression matters. The first wave of generative AI in business was mainly about individual productivity: write an email faster, summarize a document, generate code, help an analyst find an answer. The next wave connects AI to workflows, enterprise data, APIs and business rules.

At that point, AI stops being merely a productivity application and becomes part of the operating model.

Logistics is particularly exposed to this transition because freight procurement, appointment scheduling, track-and-trace, carrier communication, invoice reconciliation, inventory exceptions and delivery management all depend on large volumes of structured information moving among organizations and systems.

That is fertile ground for agentic automation.

Uber Is Also Betting on Physical Autonomy

There is another dimension to the Uber story. While simplifying its human organization and expanding AI use, the company is simultaneously making a very large investment in autonomous transportation.

Uber said in its Q2 2026 prepared remarks that it expects to commit more than $10 billion over the coming years through equity investments, infrastructure and vehicle commitments intended to bring autonomous vehicles to market at scale. Autonomous vehicles were already live on Uber in seven cities, the company said, with as many as 15 expected by year-end. Its partners have committed approximately 120,000 vehicles to the Uber network over the coming years.

What is particularly interesting is how Uber defines its role. The company does not need to manufacture every vehicle or develop every autonomous-driving system. Instead, it can provide demand aggregation, dispatch intelligence, vehicle integration, fleet operations, charging infrastructure, financing, insurance and regulatory relationships around an ecosystem of partners.

Uber is increasingly positioning itself not simply as a transportation marketplace, but as an orchestration layer across digital and physical transportation.

That distinction should matter to logistics executives. Autonomous transportation does not end with removing the human driver. The network still requires demand forecasting, capacity allocation, dispatch, maintenance, charging or fueling, customer communication, exception management and financial settlement.

If physical automation develops alongside digital agents capable of coordinating those activities, the operating model changes much more profoundly.

Digital and Physical Autonomy Converge

We are therefore beginning to see two forms of autonomy develop at the same time. Physical autonomy moves vehicles and goods with less direct human operation. Digital autonomy makes and coordinates a growing number of the decisions surrounding those movements.

Consider an autonomous delivery network in which AI agents forecast demand, allocate capacity, reposition vehicles, schedule charging, monitor maintenance, communicate with customers and manage exceptions. Removing the driver is only one component of the automation. Much of the administrative infrastructure surrounding the vehicle can also become increasingly autonomous.

The important development is not any one technology. It is the interaction among them.

That is again a systems-engineering issue.

What Logistics Leaders Should Look For

This does not mean logistics companies should begin eliminating management layers simply because Uber is doing so. Nor does it suggest that human judgment becomes unimportant. The implication is that companies should begin identifying where coordination costs have become embedded in their operating models.

Where does information sit waiting for somebody to move it? Where does an exception pass through several employees before reaching someone with the authority to resolve it? Where are multiple groups maintaining slightly different versions of the same operational truth? Where do recurring meetings exist because underlying systems and decision rights remain poorly integrated?

These are no longer merely process-improvement questions. They are increasingly systems-architecture and AI questions.

The organizations that gain the most from AI may therefore not be those that deploy the largest number of copilots. They may be the organizations willing to redesign processes once the technological limitations that created those processes begin to disappear.

Human expertise remains essential, but its value shifts toward judgment, relationships, system design, accountability, risk management, strategic tradeoffs and genuinely novel exceptions. Routine information gathering, reconciliation and coordination become increasingly machine-assisted or machine-executed.

The likely result is a flatter logistics organization with clearer process ownership, broader spans of control, fewer administrative handoffs and more automated decision execution.

Uber’s restructuring is worth watching because several developments are occurring simultaneously. The company is reducing organizational layers, redesigning operating structures, applying AI to transportation workflows and investing billions of dollars in autonomous mobility.

Viewed independently, each initiative is interesting. Viewed as a system, they point toward something much larger.

The future logistics enterprise may not simply automate more tasks. It may require far fewer layers to coordinate them.

The post Uber’s Restructuring Shows Where AI in Logistics Is Really Going appeared first on Logistics Viewpoints.

The core job has not disappeared

At the center, the category remains the operational system that manages inventory location, warehouse work, task priorities, replenishment, picking, packing, staging, and shipping inside the distribution operation. Core execution discipline matters because advanced analytics or AI cannot compensate for weak transaction integrity, incomplete master data, or unreliable operating state. A modern platform has to do the foundational work consistently before its higher-order intelligence becomes valuable.

That foundation now spans inventory control, receiving and putaway, replenishment, wave and waveless work release, picking and packing, labor coordination, shipping, yard and dock interfaces, analytics, and increasingly automation orchestration and AI-assisted decision support. The breadth matters, but breadth alone is not the differentiator. Two products can check many of the same boxes and behave very differently under real operating pressure.

The category boundary is expanding

The market is being pulled outward by labor scarcity, tighter customer cutoffs, omnichannel fulfillment, higher SKU complexity, automation investment, faster order cycles, and the need to coordinate people and machines in real time. As a result, platforms are being asked to operate on shorter planning cycles, exchange more events with adjacent systems, and support decisions that used to be handled through email, spreadsheets, meetings, or manual follow-up.

The architectural context is increasingly ERP and OMS upstream; WMS at the inventory-and-work core; WES/WCS, robotics, conveyors, sortation, labor systems, YMS, parcel, and TMS around the execution edge. That makes interoperability part of functional performance. A capability that cannot receive the required state, make a timely decision, or push a usable action into the execution environment is less valuable than its demo may suggest.

What still defines the boundary

A WMS should remain accountable for warehouse inventory and work state even as orchestration, automation control, and decision support extend beyond the traditional application boundary

A useful category definition should therefore separate adjacent capabilities from genuine responsibility. The question is not whether the platform can display or discuss warehouse management systems; it is whether it can reliably perform the work, govern the decisions, and sustain the operating state that the category requires.

The 2026 buyer test

Buyers should evaluate operational fit, configurability without excessive customization, automation integration, real-time work orchestration, data and API architecture, scalability, implementation model, upgradeability, and measurable warehouse outcomes. The practical proof should come from operating scenarios such as a late inbound trailer, a constrained dock, a wave that threatens a carrier cutoff, an automation cell that goes down, or an urgent order that must be reprioritized without destabilizing the rest of the facility. Those scenarios force providers to show how the product behaves when plans change, data are incomplete, objectives conflict, or the preferred option disappears.

That is what makes the 2026 market different. The category is no longer defined only by what the software records. It is increasingly defined by how effectively it helps the operation decide and act.

A broader WMS category needs stronger boundary discipline

As WMS expands into orchestration, automation, labor, analytics, and AI-assisted work, buyers should be more—not less—precise about accountability. Inventory state, work state, task release, exception handling, and shipping execution still need an authoritative operating core. Adjacent tools may contribute specialized intelligence or equipment control, but the architecture should make clear which system owns the state that downstream decisions depend on.

This matters during implementation as much as selection. A platform can look broad in a demonstration yet create fragile operations if inventory, work priorities, automation signals, and carrier cutoffs are reconciled through custom logic outside the product. Buyers should ask where state lives, how quickly it changes, which interfaces are standard, and how the design behaves during upgrades, automation outages, or sudden reprioritization.

Related Logistics Viewpoints research

• 2026 Warehouse Management Systems Market Map
• The New Architecture of Logistics
• Systems Engineering in Logistics
• The Digital Backbone of the Warehouse: Trends Shaping the 2026 WMS Market

The post What Is a WMS in 2026? The Warehouse Management System Is Becoming Something More appeared first on Logistics Viewpoints.

Taken together, the week’s developments point toward a logistics environment in which operational execution is becoming more technologically sophisticated just as the external operating environment becomes more difficult. That combination matters because better technology is arriving at precisely the moment logistics organizations have more variables to manage.

Freight Markets Are Finally Beginning to Tighten

After a prolonged freight recession, the U.S. trucking environment appears to be changing. Recent reporting points to strengthening truckload economics as transportation capacity tightens and demand improves in selected sectors. Spot freight rates have reportedly risen materially, while contract pricing has also begun moving upward, with data-center construction and manufacturing activity contributing to freight demand, particularly in areas such as flatbed transportation. (marketwatch.com)

The change does not mean every carrier or every freight market has suddenly entered a boom, but it does suggest that the balance between shippers and carriers is becoming less one-sided than it has been during much of the post-pandemic freight downturn. For logistics executives, this is the point in the cycle when transportation strategy becomes important again.

Shippers that became accustomed to abundant capacity and aggressive carrier pricing should be careful about assuming those conditions will continue indefinitely. Routing guides, contractual relationships, carrier mix, fuel exposure, and network flexibility deserve renewed attention because freight markets eventually rebalance.

Fuel and Geopolitics Are Becoming Logistics Variables Again

The change in transportation economics is being amplified by energy markets. Oil prices moved higher this week as the U.S.-Iran conflict again raised concerns about Middle Eastern supply and shipping through the Strait of Hormuz. Vessel traffic through the strait has fallen sharply, while disruptions to refining capacity in the Middle East and Russia have put additional pressure on diesel markets. (reuters.com)

The logistics implications extend well beyond the price displayed at a truck stop. Higher diesel costs flow through truckload transportation, parcel, rail, ocean shipping, and ultimately shipper fuel-surcharge programs. Reuters reported that transportation companies have increased fuel surcharges as the conflict pushed energy costs upward, rekindling the perennial debate over how closely carrier surcharge formulas actually track underlying fuel costs. (reuters.com)

The global diesel trade itself is also being reshaped. Asian refiners significantly increased diesel shipments to Africa during August as Middle Eastern supplies declined, while Turkey sharply increased imports from the United States and India after Russian supply disruptions. (reuters.com)

These are energy stories, but they are also logistics stories because fuel availability, refinery geography, shipping-route security, freight rates, and transportation costs remain deeply interconnected.

UPS Is Repositioning Around Integrated Logistics

One of the most strategically interesting developments of the week came from UPS. The company announced a new operating structure intended to make better use of its worldwide transportation and logistics network while continuing its shift away from being defined primarily as a domestic small-package carrier.

UPS is standardizing more operations globally and putting greater emphasis on integrated logistics, international operations, healthcare logistics, industrial and automotive markets, and higher-value customers. The restructuring follows a substantial reduction in lower-margin Amazon package volume and the closure of a significant number of domestic sorting facilities. (freightwaves.com)

The strategic direction deserves attention because parcel networks are extraordinarily difficult and expensive assets to build. The challenge for companies such as UPS is increasingly to use those assets across a wider collection of logistics services rather than compete primarily on moving another residential package. The distinction between parcel carrier, freight provider, healthcare logistics provider, international transportation company, and integrated logistics provider continues to blur.

That is another example of a larger trend across logistics: traditional category boundaries are weakening.

Transportation Software Keeps Consolidating

The transportation-management market produced another notable transaction. Descartes Systems Group acquired Tai Software for approximately $100 million, adding a freight-broker-focused TMS platform to the company’s broader logistics technology portfolio. Tai supports truckload, less-than-truckload, drayage, cross-border freight, quoting, carrier sourcing, execution, invoicing, and customer workflows. (descartes.com)

The transaction is interesting for more than its size. Freight brokerage remains an information-intensive business in which relatively small improvements in automation can materially affect operating leverage. Traditional brokerage requires people to perform large numbers of repetitive activities, including quoting freight, identifying carriers, communicating with drivers, updating customers, tracking shipments, investigating exceptions, invoicing transactions, and reconciling documentation.

AI and workflow automation increasingly allow transportation platforms to absorb more of that administrative work. That makes TMS platforms more strategically valuable because they are evolving from systems that record transportation activity into systems that increasingly orchestrate it.

A related signal came from the investment community. Mubadala Capital acquired a majority position in Arrive Logistics, with Arrive planning additional investment in its technology and AI-enabled transportation platform. (wsj.com) Capital is still interested in logistics, but increasingly the attraction lies where technology can improve the economics of logistics execution.

Amazon Pushes Automation Toward the Delivery Station

Warehouse and last-mile automation also continued moving forward. Amazon’s reported Project Tetromino targets one of the harder parts of the company’s logistics network to automate: the delivery station. These facilities sit between fulfillment operations and the final delivery route, where packages must be received, sorted, sequenced, staged, and ultimately loaded into delivery vehicles.

Amazon is reportedly investigating greater use of robotics, automated storage, AI, and package-sequencing technologies to automate more of that work. Internal projections cited in reporting suggest the approach could significantly improve productivity at future delivery stations. (businessinsider.com)

This is strategically important because the next generation of logistics automation is moving away from isolated automated tasks. The first wave of warehouse robotics focused heavily on moving inventory or assisting workers. The emerging wave is increasingly about orchestration: how inventory, robots, software, labor, conveyors, transportation schedules, and customer commitments operate as one coordinated system.

That question applies equally to fulfillment centers, distribution centers, sortation hubs, and delivery stations.

AI Is Moving from Advice Toward Execution

This week’s technology stories reinforce a trend that Logistics Viewpoints has been following closely: AI is moving from answering logistics questions toward performing logistics work. That does not mean autonomous transportation and warehouse systems are about to operate without human supervision. It means the software layer is beginning to assume responsibility for increasingly bounded operational activities.

Transportation applications can already automate portions of load creation, carrier sourcing, documentation, exception management, and customer communication. Warehouse systems are increasingly optimizing tasks, inventory placement, robotic fleets, labor allocation, and workflow priorities, while supply chain copilots are beginning to evolve toward agentic systems that can interact with enterprise applications rather than simply summarize their contents.

The critical question therefore shifts from whether AI can provide a useful recommendation to which operational actions AI should be permitted to perform, under what constraints, and with what level of human oversight. That distinction will become increasingly important as logistics AI moves closer to execution.

Freight Security Is Becoming Harder to Ignore

Not every important logistics technology problem involves automation. Cargo theft remains a growing operational concern, with reported U.S. cargo theft increasing 5% sequentially during the second quarter, according to data cited by FreightWaves. California and Texas remain major hotspots, electronics are among the most frequently targeted commodities, and warehouses, truck stops, and rail facilities continue to attract criminal activity. (freightwaves.com)

The problem has become increasingly sophisticated. Recent incidents involving fraudulent pickups illustrate how thieves can exploit the digital and administrative layers of freight transportation rather than physically hijacking a truck. In one widely reported California case, thieves allegedly used fraudulent trucking information and documents to obtain approximately $70,000 of beverage cargo from a distribution facility. (theguardian.com)

That should concern shippers because transportation networks increasingly depend on electronic identity, digital documentation, brokers, subcontractors, and rapid tendering. The same connectivity that makes freight networks more efficient can create new vulnerabilities, which means carrier identity verification, pickup authentication, cybersecurity, and transaction validation are becoming part of mainstream logistics risk management.

Rail Consolidation Remains a Major Strategic Question

The proposed Union Pacific-Norfolk Southern combination also continues moving through the regulatory process. The Surface Transportation Board has established a procedural schedule and resumed its review of the proposed transaction, while the railroads and opponents continue debating the merits of the combination. The STB has explicitly noted that moving the process forward does not constitute approval of the merger. (stb.gov)

For shippers, the importance goes well beyond the two companies. A transcontinental rail combination would potentially reshape competitive dynamics across U.S. freight transportation and could eventually influence intermodal service, network design, pricing, terminal investment, and relationships between railroads and motor carriers.

This is likely to remain one of the most consequential structural transportation stories to watch.

The Bigger Picture

What makes this week’s news interesting is that several different logistics cycles are converging. Freight markets appear to be tightening while fuel prices and geopolitical risk are again affecting transportation economics. Major providers such as UPS are reconsidering how their physical networks should compete, transportation technology continues consolidating, and private capital is backing logistics companies that can use AI and automation to improve productivity.

At the same time, Amazon is pushing robotics deeper toward last-mile execution, cargo thieves are exploiting increasingly digital freight networks, and regulators are evaluating transportation combinations that could reshape the structure of U.S. freight networks for decades. These developments reflect an increasingly complicated environment in which logistics organizations must simultaneously manage physical assets, technology platforms, network economics, security, and external risk.

The competitive advantage is therefore unlikely to come simply from having more automation, more software, or more transportation capacity. It will come from coordinating those assets better by connecting transportation, warehousing, labor, inventory, automation, data, and decision-making into an operating architecture capable of adjusting as conditions change.

That is where logistics appears to be heading. The future of logistics will not simply be more automated; it will be more adaptive.

The post This Week in Logistics: Freight Tightens, AI Moves into Execution, and Networks Get More Strategic appeared first on Logistics Viewpoints.

Recent developments suggest that transition is beginning to become more visible.

Autonomous trucking company Gatik announced a $200 million Series D financing round on August 25. The size of the investment is significant, but the more consequential story for logistics is the operating activity behind it. The company says it has completed approximately 85,000 fully driverless commercial orders and has accumulated more than $600 million in contracted revenue.

Those figures are company-reported and should not be treated as independently verified operating benchmarks. Nevertheless, they illustrate the increasing commercial maturity of a segment that has historically been dominated by pilots and demonstrations.

A Different Approach to Autonomous Trucking

Gatik’s approach differs from some of the more ambitious autonomous-trucking strategies pursued over the past decade. Rather than beginning with the objective of automating virtually any long-haul trucking environment, the company has concentrated on high-frequency regional movements between distribution centers, warehouses, and stores—more constrained operating environments than generalized long-haul trucking.

The distinction matters because logistics environments vary considerably in complexity. A truck repeatedly traveling between known facilities along established routes presents a more bounded operating problem than a vehicle expected to operate across a broad range of origins, destinations, road conditions, and transportation scenarios.

For autonomous freight, these constrained operating domains can create an important path toward commercialization. Companies can concentrate technology, mapping, operating procedures, and exception management around routes where shipment frequency is high and operating conditions are comparatively predictable.

The logistics lesson is straightforward: autonomous transportation does not have to solve every trucking use case before it can create economic value. It needs to solve specific transportation problems reliably enough to compete with existing operating models.

Middle-Mile Logistics Could Be an Important Entry Point

Middle-mile transportation is particularly interesting because of its repetitive nature. Large logistics networks routinely move freight between the same facilities as distribution centers replenish stores, manufacturing facilities ship to warehouses, regional facilities exchange inventory, and consolidation centers feed downstream fulfillment operations.

Many of those movements occur frequently enough to provide the repetition autonomous systems need to accumulate operating experience. That creates a potentially different commercialization path from the popular image of an autonomous truck replacing a human driver across arbitrary long-haul routes.

Instead, autonomous trucking could initially develop as another specialized logistics technology deployed where operating conditions and economics make sense.

The precedent exists elsewhere in logistics. Warehouse automation did not begin by automating every activity inside a distribution center. Companies initially targeted highly repetitive processes where automation could produce measurable improvements in throughput, labor utilization, accuracy, or cost.

Autonomous freight may follow a similar trajectory.

Automation Is Moving Deeper Into Logistics Execution

The development also fits a broader pattern across logistics technology. Automation is gradually moving beyond highly structured warehouse processes into more complex physical operations.

Robotics companies are targeting trailer loading and unloading, pallet transportation, inventory monitoring, parcel handling, and other activities that have traditionally depended heavily on manual labor. Transportation represents another step in that progression.

The economics, however, will ultimately determine the pace of adoption. Autonomous vehicles must compete against an established trucking system with enormous infrastructure, mature operating practices, and considerable flexibility.

Potential benefits such as higher asset utilization or reduced dependence on driver availability therefore have to be weighed against vehicle costs, remote support, maintenance, insurance, regulatory requirements, safety systems, and the infrastructure required to operate autonomous fleets.

That makes actual commercial operating history especially important. The autonomous-trucking market does not need more evidence that a truck can drive itself under controlled conditions. Logistics companies need evidence that autonomous fleets can operate reliably, repeatedly, and economically as part of real transportation networks.

The Economics Matter More Than the Demonstration

This distinction is becoming increasingly important across logistics automation. The relevant question is no longer simply whether a technology works. It is whether deploying that technology changes the economics or performance of the logistics operation enough to justify adoption.

For autonomous trucking, that means examining metrics such as cost per mile, vehicle utilization, intervention rates, service reliability, downtime, maintenance requirements, and the ability to integrate autonomous vehicles into existing transportation-management processes.

It also means understanding where autonomy creates the greatest value. A highly repetitive route operating several times each day may have very different economics from an irregular lane with constantly changing origins, destinations, and operating conditions. Similarly, a transportation network facing chronic driver shortages may value autonomy differently from one with abundant capacity.

Autonomous trucking is therefore unlikely to arrive uniformly across the transportation market. Adoption is more likely to proceed lane by lane and operating environment by operating environment.

From Autonomous Vehicles to Autonomous Logistics

The longer-term implications extend beyond the vehicle. A truly autonomous transportation operation requires more than a self-driving truck.

Loads still need to be planned. Vehicles need to be dispatched. Dock appointments need to be coordinated. Exceptions need to be resolved. Freight needs to be matched with available equipment, and downstream facilities need to know when it will arrive.

As autonomy expands, transportation management systems and logistics orchestration platforms will therefore need to manage increasingly heterogeneous fleets containing human-operated vehicles, autonomous vehicles, and potentially multiple autonomous operating models.

That creates a broader opportunity for logistics software. The vehicle may execute the movement, but the logistics system still has to determine what should move, when it should move, which asset should move it, and what should happen when conditions change.

The evolution of autonomous trucking is therefore part of a larger transition toward more automated logistics execution.

What Logistics Leaders Should Watch

The next stage of autonomous freight should be judged less by demonstration miles and funding announcements and more by commercial operating evidence. Fleet size matters, but so do utilization, intervention frequency, reliability, customer retention, geographic expansion, and unit economics.

Gatik’s latest financing provides additional capital to pursue that expansion. Its reported commercial activity also suggests that autonomous middle-mile transportation is beginning to accumulate the operating history needed to evaluate the model more seriously.

The technology still has substantial distance to travel before autonomous trucks represent a meaningful share of North American freight transportation. But the question surrounding autonomous trucking is beginning to change.

For years, the industry asked whether autonomous trucks could operate safely enough to move commercial freight. Increasingly, logistics operators will be asking a more consequential question:

Where can autonomous freight operate reliably enough—and economically enough—to become part of the transportation network?

That is the point at which autonomous trucking stops being primarily a technology story and becomes a logistics story.

The post Autonomous Freight Is Moving From Experimentation Toward Commercial Logistics appeared first on Logistics Viewpoints.

A transportation plan changes, but the warehouse does not see the effect soon enough. A late inbound shipment changes inventory availability, but the downstream fulfillment plan continues as if nothing happened. A warehouse completes an outbound wave, but carrier capacity is no longer aligned with the original plan. An exception is visible in one application while the people or systems able to resolve it are working somewhere else.

For years, logistics technology has been built primarily around functions. TMS manages transportation. WMS manages warehouse activity. YMS manages the yard. OMS manages orders. Visibility platforms monitor movement. Automation systems control physical equipment. Each solves a legitimate problem.

But modern logistics is increasingly exposing the limits of treating those functions as independent operating islands. Logistics is beginning to behave more like an operating system.

From Functions to a Connected Execution System

Calling logistics an operating system does not mean that one new software platform will replace every existing application. The opposite is more likely. Specialized execution systems will remain important because transportation, warehousing, fulfillment, yard operations, and global trade are different disciplines with different constraints.

The change is in how those systems interact.

A modern logistics operation increasingly needs to sense what is happening across the physical network, understand the operational significance of those events, decide what should change, execute the response, and learn from the outcome. That creates a recurring loop: sense, understand, decide, execute, learn.

The faster and more reliably that loop operates, the more responsive the logistics network becomes.

The Physical Layer Still Comes First

Logistics remains a physical business. Trucks, trailers, containers, warehouses, dock doors, conveyors, forklifts, robots, roads, ports, and people ultimately determine whether goods move.

That matters because digital transformation language can obscure a basic reality: software cannot create a dock door that does not exist, unload a trailer without labor or automation, or make a congested port uncongested. Physical constraints remain real.

What software can do is make those constraints more observable and help the operation use available capacity more intelligently. A trailer location becomes an event. A dock becomes a schedulable resource. A robot becomes a continuously monitored asset. A predicted arrival becomes an input to labor planning. Physical logistics begins to produce a digital state that other systems can interpret.

The Execution Layer

Above the physical layer sit the systems that direct work. TMS determines how freight should move. WMS directs warehouse tasks. YMS coordinates trailers and yard resources. OMS helps manage order execution. Warehouse execution and control systems coordinate increasingly complex automation.

These systems are not disappearing. They are becoming components of a larger execution architecture.

The important question is increasingly not whether a company has a TMS or WMS. It is whether the decisions made in one execution domain can influence another domain quickly enough to improve the overall result.

The Observation Layer

Logistics cannot coordinate what it cannot see. Telematics, IoT devices, RFID, computer vision, carrier feeds, warehouse events, geofencing, and visibility platforms are expanding the amount of machine-readable information available about physical operations.

But more data does not automatically create better logistics. An organization can drown in events just as easily as it once suffered from too little visibility. The observation layer becomes valuable when it distinguishes meaningful changes from routine noise and connects those changes to the decisions they affect.

The Intelligence Layer

This is where optimization, analytics, simulation, digital twins, machine learning, and generative AI begin to matter.

The role of intelligence is not simply to describe the network. It is to interpret what the observed state means. Which late shipment matters? Which warehouse constraint will propagate downstream? Which route change protects service at an acceptable cost? Which exception can be handled automatically and which requires human judgment?

AI expands the range of information that can be interpreted and the number of routine decisions that software can support. But intelligence without connection to execution risks becoming another dashboard. The real value comes when analysis shortens the distance between an event and an effective response.

The Orchestration Problem

This is the emerging center of the architecture.

Logistics has spent decades improving individual systems. The next problem is coordinating decisions across them. A transportation event may require a warehouse response. A warehouse constraint may require a carrier response. A customs issue may change an inventory commitment. A labor shortage may change a fulfillment sequence.

No individual execution system necessarily owns the entire decision.

That is why orchestration, exception management, control layers, and agentic workflows are becoming more important. They address the decision space between established systems.

The Economics Are About More Than Automation

The business case for this architecture is often framed as labor reduction or automation. That is too narrow.

A connected logistics operating system can affect freight cost, warehouse throughput, asset utilization, inventory exposure, service, detention, labor productivity, and resilience. It can also reduce something that is harder to see on a financial statement: decision latency.

When an exception waits thirty minutes, three hours, or a day for the right person to notice it, understand it, and authorize a response, physical capacity can sit idle while service deteriorates. Faster decision cycles can therefore create operational value even when the underlying number of trucks, doors, or workers does not change.

The Architecture Is the Strategy

The most important logistics technology question is shifting. It is no longer simply, “Which system should we buy?” It is increasingly, “How will our systems, data, assets, and people operate together?”

That does not require a grand replacement program. In many organizations, the more practical path will be incremental: improve event quality, connect execution systems, establish clearer decision rights, automate bounded workflows, and measure whether exceptions are being resolved faster and with better outcomes.

The winners will not necessarily have the most technology. They will have the architecture that converts physical state into effective action with the least friction.

That is the central argument of this series. Logistics is becoming a connected physical and digital execution system. Transportation, warehousing, visibility, automation, data, and AI are not separate transformation stories. They are layers of the same emerging architecture.

And that immediately exposes one of the oldest organizational boundaries in logistics: the divide between transportation and the warehouse.

Related Logistics Viewpoints research

• The New Architecture of Logistics
• Systems Engineering in Logistics
• 2026 Supply Chain Decision Intelligence Market Map
• The Supply Chain Operating Model After AI

The post Logistics Is Becoming an Operating System appeared first on Logistics Viewpoints.

That distinction matters because logistics is full of dependencies. A later customer cutoff changes picking waves, dock schedules, carrier tender timing, and linehaul departure. A transportation consolidation rule changes warehouse staging and order cycle time. A warehouse automation decision changes labor requirements, replenishment timing, maintenance needs, and trailer flow. An AI recommendation can identify a better routing or exception response and still create little value if the decision and execution path around it has not changed.

This is the case for applying systems engineering to logistics: design the operating system before optimizing its individual components.

Local optimization is the wrong unit of analysis

Most logistics organizations are still managed as adjacent functions. Transportation has its objectives. Warehousing has its objectives. Yard and dock operations, parcel and last-mile delivery, customer service, inventory execution, and IT have theirs. Each function can make a rational decision and still make the total logistics system worse.

Consider a common tradeoff. Transportation may seek fuller truckloads and fewer departures. Warehousing may prefer large, stable waves that maximize labor productivity. Parcel operations may steer volume toward the lowest-cost service. Each choice can look efficient from inside the function making it. Taken together, however, they can lengthen order cycle time, increase staging congestion, miss carrier cutoffs, and weaken the customer promise.

That is not necessarily a failure of intelligence. It is a failure of system design.

Systems engineering starts from a different premise. It asks what the entire system is intended to accomplish, what requirements must be satisfied, what constraints must be respected, and how the parts interact. Interfaces and dependencies become first-class design issues rather than implementation details to be managed later.

Define the requirement before admiring the feature

Technology selection often reverses this logic. An organization sees a new TMS, WMS, control tower, AI capability, robotics platform, or digital twin and begins asking where it can be used.

A systems-engineering approach starts with a more disciplined question: what problem does the logistics operating system need to solve?

A requirement such as “reduce order-to-delivery variability for priority customers” is fundamentally different from “implement a control tower.” The first states an operating outcome. The second names a possible solution. Once the requirement is explicit, technology can be evaluated against it and the necessary tradeoffs become visible.

If the requirement is faster exception response, for example, the operation may need better carrier and facility data, different decision rights, more flexible transportation or warehouse capacity, or redesigned handoffs before it needs another application. This is one reason technology programs can disappoint even when the software works as designed: the organization installs a component without redesigning the system around it.

The handoffs are usually where the system breaks

Systems engineers spend considerable time on interfaces because complex systems often fail at their boundaries. Logistics networks are no different.

The interface between order orchestration and physical execution matters. So does the interface between a shipper and a carrier, a WMS and an automation layer, a yard appointment and a dock schedule, a TMS recommendation and carrier tendering, or an AI recommendation and the human expected to act on it.

A process can be excellent within one department and still fail at the handoff. This is increasingly important because logistics is an ecosystem rather than a company-owned operating chain. Shippers, carriers, 3PLs, parcel providers, ports and terminals, warehouses, software platforms, customers, and automated agents all participate in the same outcome even though no single organization controls the entire system.

The engineering challenge is therefore not simply to optimize assets. It is to engineer interactions.

Engineer the bad day, not just the average day

Logistics design has historically emphasized efficiency under expected conditions: planned volumes, expected transit times, normal staffing, available capacity, and functioning technology. A systems-engineering view also asks what happens when those assumptions fail.

What happens when a carrier rejects a tender? When a distribution center loses power? When a sortation or robotics layer goes down? When a dock becomes congested? When a routing model receives bad data? When an operator overrides an AI recommendation? When a critical integration is unavailable?

The objective is not to eliminate failure. No realistic logistics system can do that. The objective is to identify failure modes before they become operating surprises and to design recovery into the system. Redundancy, fault tolerance, graceful degradation, verification, validation, and lifecycle management all have direct logistics equivalents.

Logistics transformation has become an engineering problem

The larger implication is organizational. Logistics transformation can no longer be treated primarily as a sequence of TMS, WMS, automation, visibility, and AI projects. Transportation, warehousing, yards, fulfillment, parcel, and last-mile execution are too interconnected, and the technology stack is becoming too consequential.

Leaders need a way to connect business requirements to process architecture, data architecture, decision architecture, technology, human roles, controls, and measurable outcomes. They need to know not only whether individual components work, but whether the entire operating model works as intended.

This is also the bridge to The New Architecture of Logistics. As logistics becomes more connected, observable, intelligent, and increasingly automated, architectural discipline becomes more important rather than less. The same principle applies to the emerging Decision Intelligence market: intelligence has value only when it improves a consequential decision and connects that decision to action.

Logistics already behaves like a complex engineered system. The management discipline now needs to catch up.

Related Logistics Viewpoints research

• Systems Engineering in Logistics
• The New Architecture of Logistics
• 2026 Supply Chain Decision Intelligence Market Map
• Bentley’s MCP Server Shows How AI Can Work in Engineering Without Guessing

The post Why Logistics Needs Systems Engineering appeared first on Logistics Viewpoints.

SAP’s latest transportation management briefing points toward something broader.

The company is no longer presenting transportation simply as a stand-alone planning application. It is increasingly assembling a tiered logistics execution architecture, with SAP Transportation Management handling sophisticated transportation operations, Business Network for Logistics connecting execution to carriers and other external partners, SAP Logistics Management addressing simpler sites and distribution operations, and Joule beginning to coordinate decisions across those layers.

That is a more consequential shift than simply adding another collection of TMS features.

SAP TM remains the advanced transportation engine

SAP Transportation Management remains the center of the portfolio for complex transportation operations. The platform spans order management, transportation planning, execution, charge management, freight settlement, analytics, strategic freight management, and essentially every major transportation mode other than pipeline.

But the interesting part of SAP’s strategy is increasingly what happens around that transportation engine.

A transportation plan does not exist in isolation. It affects warehouse labor, dock capacity, inventory availability, customer commitments, carrier operations, global trade requirements, dangerous-goods restrictions, and ultimately financial settlement.

SAP continues to tighten those connections.

The company highlighted further development of Advanced Shipping and Receiving, which links transportation and warehouse execution more closely, along with capabilities including ad hoc loading, rules-based loading, improved process reversals, requirements grouping, and tighter integration between Transportation Management and Extended Warehouse Management.

The objective is straightforward: an optimal transportation plan is not particularly useful if the warehouse cannot execute it.

That sounds obvious. Architecturally, however, it is one of the more important issues facing logistics technology.

The network is increasingly part of the transportation system

SAP is also treating external collaboration as an integral part of transportation execution.

Business Network for Logistics provides connectivity for carrier tendering, appointments, freight invoices, shipment visibility, fleet information, milestone events, alerts, and emissions information. SAP also continues to support different levels of carrier sophistication, from APIs and EDI to web portals for smaller transportation providers.

This matters because transportation is inherently an inter-enterprise process.

The most sophisticated optimization engine in the world still has limited value if the resulting plan cannot be communicated, accepted, monitored, and adjusted across carriers, suppliers, warehouses, and customers.

For SAP, the carrier network is therefore becoming less of an adjacent capability and more of an execution layer around the TMS.

SAP Logistics Management fills an important gap

The most strategically interesting part of the briefing may have been SAP Logistics Management.

SAP acknowledged a problem that exists across many enterprise logistics environments: not every facility needs a full enterprise TMS.

A multinational organization may operate several highly complex distribution centers that require advanced optimization, international transportation management, and sophisticated freight settlement. That same company may also operate dozens or hundreds of smaller facilities performing relatively straightforward local distribution.

Deploying the same heavyweight architecture everywhere can become unnecessary complexity.

SAP Logistics Management is intended to address those simpler-to-moderate transportation and warehouse scenarios. SAP specifically discussed local distribution sites, regional fulfillment operations, and other facilities where a full TM implementation may be more capability than the operation requires.

This gives SAP the beginnings of a much more interesting portfolio structure:

advanced transportation where complexity requires it, lighter execution where it does not, and a common logistics architecture connecting the two.

For large enterprises with highly uneven operational complexity, that could be a meaningful proposition.

Joule is moving from interface to execution

AI was inevitably a major theme of the briefing, but the more important development is how SAP is changing the role of Joule.

The first generation of generative AI in transportation largely involved conversational access to information. A planner might ask the system to locate certain freight orders, identify unplanned demand, or retrieve transportation information using natural language.

SAP is now moving toward transactional interaction.

One example discussed in the briefing was the ability to tell Joule that a carrier has experienced a truck failure and then instruct the system to change the carrier across the affected freight orders.

The roadmap moves further toward agentic execution.

SAP described agents for predictive logistics insights, consignment-order processing, freight invoice analysis, and tendering and subcontracting optimization. The predictive logistics capability is intended to monitor events, identify potential disruption, recommend responses, and potentially trigger rerouting or other adjustments before service deteriorates.

The operating model begins to look less like:

event → dashboard → planner

and more like:

event → context → decision → recommendation → execution

That is where agentic AI becomes relevant to logistics.

The challenge will be governance. SAP emphasized that its agents operate within underlying application processes and controls, with humans remaining involved when confidence is insufficient or a consequential transaction requires validation.

That is the right boundary to watch as the technology develops.

TMS is becoming part of a larger execution architecture

The broader implication extends beyond SAP.

Transportation management is gradually becoming less of an isolated application category and more of a layer within a connected logistics execution system.

TMS still matters. Optimization still matters. Carrier selection, routing, freight settlement, and execution discipline still matter.

But increasingly the competitive question will be how effectively transportation connects to warehouse operations, carrier networks, enterprise data, visibility, and automated decision-making.

SAP’s emerging architecture reflects that shift. Transportation Management provides the advanced engine. Business Network for Logistics extends execution outside the enterprise. Logistics Management addresses lower-complexity operations. Joule and the emerging agent layer begin to coordinate decisions across the environment.

SAP is also continuing to develop the underlying operational platform rather than treating AI as a substitute for conventional product investment, with further work planned around integrated planning, public-cloud logistics integration, freight settlement, and industry-specific capabilities.

The next generation of transportation management will therefore not be defined simply by who can calculate the lowest-cost load.

It will increasingly be defined by how quickly the logistics system can sense what changed, understand its operational significance, determine the best response, coordinate that response across transportation and warehouse operations, and execute it across the broader logistics network.

SAP is building its transportation portfolio around that much larger definition.

The post SAP Is Expanding the Definition of Transportation Management appeared first on Logistics Viewpoints.

Those numbers understandably dominate the headlines.

But there is another number in NVIDIA’s results that may be even more interesting from a logistics and supply chain perspective: $279 billion.

That is the amount NVIDIA has committed to future supply and capacity, up from $119 billion just three months ago. According to the company’s CFO commentary, the increase is primarily related to securing memory and other critical components needed to meet expected demand over the next several years.

That makes NVIDIA’s earnings more than an AI story.

They are also a case study in what happens when extraordinary demand runs into constrained industrial capacity.

AI Is Becoming Physical Infrastructure

The first phase of generative AI was dominated by model training, experimentation and software.

The next phase looks considerably more physical.

NVIDIA is now talking about AI factories, gigascale computing facilities, large-scale networking, power, memory, data-center capacity, agents and physical AI. Vera Rubin is moving into full production, and the company has announced partnerships intended to mobilize more than $500 billion in third-party capital for additional AI infrastructure.

AWS and NVIDIA also announced an expansion involving 2 million additional GPUs, another indication of the scale at which computing infrastructure is now being deployed.

For logistics executives, this changes how AI should be viewed.

AI may appear virtual when somebody enters a prompt into a browser, but the infrastructure behind that prompt is increasingly industrial. It requires semiconductor fabrication, advanced packaging, high-bandwidth memory, networking equipment, power systems, cooling equipment, servers and enormous data-center construction programs.

All of that has to be sourced, manufactured, transported and installed.

NVIDIA Is Locking Down Its Supply Chain

The scale of NVIDIA’s commitments is striking.

The company had $279 billion in future supply and capacity commitments at the end of the quarter. Approximately $267 billion of that is scheduled within the next three fiscal years. NVIDIA expects about $92 billion of supply commitments during the remainder of the current fiscal year, followed by $87 billion and $88 billion in the following two years.

The principal issue is memory.

High-bandwidth memory has become one of the critical inputs into advanced AI systems, and NVIDIA is effectively reserving capacity well ahead of demand.

This is a familiar supply-chain response to constrained capacity: secure the bottleneck before someone else does.

What is unusual is the scale.

NVIDIA is making commitments measured in hundreds of billions of dollars because the company believes the larger risk is not excess inventory. It is being unable to satisfy demand.

That is an important distinction.

When supply becomes the constraint, procurement stops being primarily a cost-management function. It becomes a growth-enablement function.

The Trade-Off Is Showing Up in Margins

Securing supply does not come free.

NVIDIA reported a 75% gross margin in the quarter but expects approximately 74% in the current quarter. Management has also warned that higher memory costs will create additional margin pressure before pricing and supply conditions begin to catch up.

That is another useful supply-chain lesson.

A company can have enormous demand and still face deteriorating economics if critical inputs become scarce.

In NVIDIA’s case, management appears willing to tolerate some margin pressure to ensure that it can continue shipping systems into a market where demand remains greater than available capacity.

That is not particularly different from what manufacturers, retailers and logistics operators learned during the pandemic.

The difference is that this time the constrained commodity happens to be some of the most advanced technology in the world.

From Compute to Operational AI

The second logistics implication is downstream.

NVIDIA CEO Jensen Huang described AI as having reached an inflection point where it is doing useful work rather than simply being trained. NVIDIA is consequently shifting more attention toward inference, agents, robotics and physical AI.

That matters because logistics is an execution environment.

A transportation operation does not ultimately need an AI system that tells a planner that a shipment will be late. It needs a system capable of understanding the implications, evaluating alternatives and determining what should happen next.

The same is true in a warehouse. Identifying congestion is useful. Changing labor allocations, equipment priorities or order sequences in response is much more valuable.

That requires continuous inference and increasingly tight connections between software intelligence and physical systems.

Physical AI Moves Toward Logistics

NVIDIA is making a major push into what it calls physical AI: systems that perceive, reason about and act within the physical world.

Its recent announcements include robotics platforms, autonomous-vehicle technology, safety systems and agent tools designed for physical AI applications.

Warehouses are an obvious environment for this technology.

Autonomous mobile robots, robotic picking, machine vision, automated storage systems and increasingly sophisticated orchestration platforms are already common. The next stage is making these systems more adaptive.

A robot needs to interpret changing physical conditions. An orchestration layer needs to understand orders, inventory and equipment availability. Transportation systems need to reconcile constantly changing physical conditions with customer commitments.

That requires a great deal of compute.

NVIDIA’s infrastructure buildout is therefore not disconnected from logistics automation. It is one of the upstream enablers.

Agentic AI Raises the Architecture Question

There is also a third implication.

NVIDIA is explicitly positioning new infrastructure around AI agents. Its Vera CPU, for example, is being marketed as a processor designed for agentic workloads.

In logistics, that could eventually mean software agents operating across transportation, warehousing, inventory and order management.

A transportation agent might identify an inbound delay. An inventory agent could calculate the resulting exposure. A warehouse agent could adjust receiving priorities. An order-management system could evaluate customer commitments.

The value comes when these systems can coordinate.

That requires more than GPUs. It requires trusted data, operational context, retrieval, interoperability and an understanding of the relationships among shipments, orders, facilities, products and customers. Those are precisely the architectural issues behind agent-to-agent communication, context management, RAG and graph-based reasoning.

The Bigger Logistics Lesson

NVIDIA’s quarter says something larger than “AI demand remains strong.”

It shows what happens when a software-driven technology transition becomes an infrastructure cycle.

Supply availability becomes strategic. Capacity gets reserved years in advance. Component shortages affect margins. Financing becomes intertwined with infrastructure development. And the physical supply chain becomes as important as the algorithms running on top of it.

NVIDIA’s $279 billion supply commitment may therefore be one of the most revealing numbers in the entire earnings release.

The company is effectively betting that the greater risk is not building too much AI infrastructure.

It is failing to build enough.

For logistics leaders, that is worth watching closely. The AI revolution is beginning to look considerably less virtual.

It increasingly looks like factories, components, power, warehouses, transportation and capacity.

In other words, it looks a lot like a supply chain.

The post NVIDIA’s $96 Billion Quarter Is Also a Supply Chain Story appeared first on Logistics Viewpoints.

The more important question is what happens to the operating model when intelligence becomes inexpensive, agents become capable of action, workflows cross application boundaries, and machines receive bounded decision rights. The preceding ideas in this sequence point toward a supply chain that is not simply more automated, but organized differently around the relationship between people, software, and physical operations.

Intelligence Moves from Scarce Resource to Operating Utility

The starting point is the declining marginal cost of intelligence. For most of supply chain history, analytical attention had to be rationed because people could investigate only a limited number of problems. Organizations built thresholds, exception reports, meetings, and functional teams around that constraint.

AI weakens the constraint without removing the need for judgment. More events can be analyzed continuously, but value depends on the context surrounding the model and on the organization’s ability to convert the result into action. This is why the shift toward an intelligence layer above ERP, TMS, and WMS matters less as a new user interface than as a new operating layer.

Coordination Becomes More Valuable Than Isolated Intelligence

The first argument in this sequence was the coordination premium. As each function gains more capable systems and agents, enterprise performance depends increasingly on how those capabilities are aligned. Procurement, transportation, manufacturing, inventory, and customer service cannot be allowed to optimize independently at machine speed without a shared view of the business outcome.

This is why AI alone will not fix fragmented supply chains. The technology can increase the speed and sophistication of decisions, but organizational fragmentation can simply become software fragmentation unless objectives, data, and authority are coordinated deliberately.

The Workflow Becomes the Unit of Transformation

The execution architecture and the growing importance of the enterprise workflow shift attention away from individual applications. ERP, WMS, TMS, planning, procurement, and visibility systems remain essential, but a disruption does not belong to one application. The operating model has to follow the problem across systems until the physical supply chain changes.

This suggests that transformation programs should increasingly be organized around high-value decision workflows. Instead of asking only which application to modernize, companies can ask which cross-functional decisions create the most cost, delay, and risk, then redesign the entire path from signal to execution. Technology becomes a means of restructuring the operating flow rather than the endpoint of the program.

Time Becomes a Management Variable

The concept of decision-to-action latency makes this operating model measurable. Companies can examine the time required to detect an event, assemble context, choose an action, obtain authority, and execute the change. That gives management a way to identify where organizational delay destroys economic value.

When the long tail of decisions becomes cheap enough to examine continuously, the scale of the opportunity expands. Thousands of small inefficiencies that were previously rational to ignore can become candidates for machine attention, while people move toward decisions where ambiguity and consequence justify human involvement.

Decision Velocity Becomes Productive Capacity

The result is an operating model in which decision velocity behaves like capacity. Faster allocation, earlier intervention, and shorter approval cycles increase the productive use of inventory, transportation, warehouse resources, labor, and manufacturing assets. A company can therefore improve effective capacity without necessarily adding the same amount of physical capacity.

This does not make physical constraints disappear. It means organizational latency becomes a more visible share of the constraint once intelligence and execution become faster. The competitive advantage shifts toward companies that can preserve optionality and act before an operational problem becomes expensive.

Autonomy Becomes Deliberately Allocated

That speed cannot come from indiscriminate automation. The governance framework developed through reversibility and machine decision rights provides a way to allocate authority by decision class. Routine, reversible, well-understood decisions can receive greater autonomy, while high-consequence and ambiguous choices remain under stronger human control.

This is a more useful objective than pursuing a fully autonomous supply chain. The goal is appropriate autonomy: the right entity, human or machine, making the right class of decision with the right context and controls. Over time, authority can expand where performance demonstrates that the system deserves it.

The Human Role Changes, but It Does Not Disappear

In this operating model, people increasingly define objectives, negotiate tradeoffs, handle novel situations, design guardrails, manage relationships, and evaluate system performance. Machines increasingly monitor conditions, assemble context, investigate routine exceptions, prepare actions, execute bounded workflows, and learn from outcomes. The division of labor moves according to comparative advantage rather than a simplistic automation target.

This resembles the operating-model redesign I discussed in Meta and Standard Chartered Signal AI’s Next Phase: Operating Model Redesign. The larger transformation occurs when organizations stop inserting AI into existing work and begin redesigning the work around capabilities that did not previously exist. Supply chain management is approaching that point.

From Software Users to System Designers

Perhaps the biggest change for supply chain leaders is that they increasingly become designers of decision systems. They have to decide what outcomes matter, how competing objectives are reconciled, where machines can act, when people must intervene, and how the entire system learns. Those responsibilities sit above any individual application or AI model.

The emerging supply chain operating model is therefore not defined by one technology. That is why a technology strategy rather than technology noise matters: the value comes from fitting capabilities into a coherent operating design rather than accumulating disconnected AI tools. It is the combination of cheap intelligence, rich context, coordinated objectives, cross-application workflows, execution architecture, reduced decision latency, continuous machine attention, and deliberately governed autonomy. Companies that assemble those pieces coherently will have an advantage that cannot be purchased simply by licensing the same model as everyone else.

The Real Transition

For years, supply chain technology promised better visibility, better planning, better analytics, and better automation. The next stage is to connect those capabilities into an operating system that can move from signal to decision to action with far less friction. That is a change in management architecture as much as technology architecture.

The supply chain after AI will still contain people, software, warehouses, trucks, factories, suppliers, customers, and uncertainty. What changes is the speed and structure through which those elements coordinate. The competitive question will increasingly be not who has the smartest model, but who has built the better operating model around intelligence.

The post The Supply Chain Operating Model After AI appeared first on Logistics Viewpoints.

Ratcliffe traveled to Moscow on August 25 for meetings with senior Russian intelligence officials as relations between Washington and Moscow remain deeply strained. CBS News reported that the United States told Ukrainian officials in advance that a senior delegation would be traveling to Moscow and asked Ukraine to suspend strikes until the delegation had departed Russia. For logistics executives, though, the larger issue is what is happening to the global energy system around these geopolitical events.

Ukraine continues to strike Russian energy infrastructure. Russia is restricting diesel exports. Shipping through the Strait of Hormuz remains disrupted. Refined-product markets are tight. That combination matters because trucks do not run on crude oil. They run on diesel.

Watch Diesel, Not Just Crude

Crude oil prices remain the most visible measure of energy-market stress, but they do not always tell logistics executives what they need to know. Between a barrel of oil and a gallon of diesel sits a large industrial and transportation system: refineries, pipelines, storage terminals, tankers, ports and distribution networks. Problems anywhere along that chain can create a shortage of usable fuel even when crude oil itself remains available.

The U.S. Energy Information Administration reported that the average U.S. on-highway diesel price reached $5.652 per gallon on August 24, up from $5.134 on July 20. That is an increase of nearly 52 cents in five weeks, and for a large trucking fleet it moves quickly from an energy-market story to an operating-cost problem.

Russia Is Part of the Refined-Product Problem

Russia is one of the world’s important suppliers of refined petroleum products, and its refining system has been under pressure from repeated Ukrainian drone attacks. Reuters reported on August 25 that Russia plans to extend its diesel export ban through September as domestic fuel markets remain tight and some refining capacity remains unavailable.

That does not mean the world suddenly runs out of diesel. It means the rest of the market has to adjust. Buyers look elsewhere, refineries in other regions increase runs where possible, cargoes are redirected, tankers travel different routes, and refining margins rise. A refinery problem inside Russia can therefore become a logistics problem thousands of miles away.

Hormuz Adds Another Constraint

At the same time, the Strait of Hormuz remains a major source of uncertainty. Reuters reported this week that vessel movements through the strait remain far below normal levels. The more important issue for logistics, however, may again be refined fuels rather than crude.

Reuters estimated that Asian imports of refined products such as diesel, jet fuel and gasoline have fallen about 21 percent from pre-conflict levels. Refining margins remain exceptionally high, suggesting that the constraint is not simply access to crude. It is the ability to produce and move enough of the fuels transportation networks actually consume.

The world can have oil and still have a diesel problem.

Refineries are not infinitely flexible. Facilities are configured for particular crude grades and product mixes, maintenance cannot always be deferred, and damaged capacity cannot simply be replaced somewhere else. Product specifications also vary across markets, limiting how easily fuel can be shifted from one region to another.

When several disruptions occur at once, the system loses slack. Russian refining is constrained, Middle Eastern energy flows remain disrupted, tankers are being rerouted, buyers are searching for substitute supplies, and other refiners are being asked to make up the difference. That is why logistics companies should be cautious about looking at a softer crude price and concluding that the fuel problem is passing. Crude and diesel are related, but they are not interchangeable signals.

Diesel Moves Directly Into Freight Economics

For trucking, the transmission mechanism is straightforward. Fuel is one of the largest variable expenses in road transportation, so when diesel prices rise, carriers absorb some of the increase and pass some through fuel-surcharge mechanisms. Either way, the cost does not disappear.

Shippers pay more to move freight. Private fleets incur higher distribution costs. Parcel and final-mile operations face higher fuel expenses, while drayage and other diesel-intensive activities become more expensive. Eventually, some portion moves through the broader supply chain.

This is how a refinery outage in Russia or shipping disruption in the Persian Gulf can eventually appear on a transportation invoice in the United States.

Transportation Can Make the Fuel More Expensive

There is another part of the equation that deserves attention: the logistics of moving energy itself. When normal trade flows are disrupted, cargoes often move differently. Tankers travel farther, cargoes are redirected to different ports, insurance costs rise, and alternative vessels have to be found.

In some cases, politically or commercially risky ships may become effectively unavailable even though they physically exist. That creates a familiar logistics problem: nominal capacity may remain on paper while usable capacity declines. When that happens, the remaining capacity becomes more valuable, and transportation itself starts contributing more to the cost of the fuel being moved.

What Logistics Executives Should Watch

For logistics leaders, Brent and West Texas Intermediate are no longer enough. Diesel prices matter. So do distillate inventories, refinery utilization, unplanned refinery outages, Russian refined-product exports, refining margins, Hormuz vessel traffic and tanker rates.

Taken together, those indicators provide a much better view of transportation-cost exposure than the crude price alone. The events in Moscow matter politically, and the confrontation around Ukraine and the Middle East matters strategically, but logistics executives should focus on how those events work through the physical system.

They hit refineries, change product flows, alter tanker routes and available capacity, tighten diesel markets, and eventually reach trucking companies and shippers. That is the part of geopolitics that ultimately matters to logistics.

The post From Moscow to the Diesel Pump: How Geopolitics Is Moving Through Logistics Networks appeared first on Logistics Viewpoints.