Can CeylanVienna-based, globally curious.
Articles/Tech & AI

AI and the Logistics Layer Nobody Talks About

Every AI demo shows the glamorous output. Nobody shows the warehouse chaos underneath it.

21.4.2026·2 min read

Every AI demo I watch starts the same way: a slick interface, a prompt, a magical result. What nobody shows you is the logistics layer underneath — the movement of physical goods, the last-mile chaos, the warehouse that had to be completely redesigned just to support the algorithm that makes the demo look seamless.

I spent years at Foodora running logistics operations. We had machine learning optimizing delivery routes before it was fashionable to say "AI-powered." And what I can tell you is this: the technology was the easy part.

The unglamorous truth

When you optimize a delivery route, you're not just solving a math problem. You're negotiating with traffic, weather, human behavior, restaurant kitchen speeds, and the rider who decided today was the day to quit. No algorithm accounts for all of that perfectly.

Continue reading?

The next essay lands in your inbox first. The thinking behind the decisions.

What AI does well is reduce the variance. It narrows the band of bad outcomes. It makes the average better. But the tail risks — the really bad days — those still require humans who understand the system deeply.

The most dangerous place to be is confidently wrong. AI systems can be confidently wrong at scale.

Where it's actually going

The logistics companies that will win in the next decade aren't the ones deploying the most AI. They're the ones building the feedback loops that make their AI smarter than anyone else's. Data moats are real, and they're being built right now in fulfillment centers most people have never heard of.

What I watch closely: autonomous middle-mile (trucks between warehouses), dynamic slotting in warehouses (AI deciding where to place goods in real time), and demand forecasting that actually accounts for social signals, not just historical sales.

The last one is underrated. If you know a product is going viral on TikTok 48 hours before it spikes, you can pre-position inventory. That's not science fiction — it's happening now, and it's a genuine competitive advantage.

What this means for founders and investors

If you're building in logistics-adjacent AI, the question to ask is: who owns the feedback loop? If your model improves every time it runs and your competitor's doesn't, time is on your side. If you're just a thin layer on top of an API, you're a feature, not a company.

The physical world is slow to change. That's not a bug — it's a moat for the people who understand it.

Share

If you read this far, the next one is for you.

The thinking behind the decisions — on Tech & AI and everything adjacent to it. No schedule, no filler. You get it before anyone else does.

More on Tech & AI

I Hired Two AI Developers. One Is a Rocket. The Other One Checks the Wiring.

Managing Claude and Codex as a solo founder felt uncomfortably familiar — turns out scaling AI agents has the same team dynamics as scaling a real operations team.

You Don't Need to Code Like a Developer — You Need to Think Like a Product Owner

I didn't become a developer. I became the one-man product owner, scrum master, and stakeholder who finally had an AI team that could actually build what I was describing.

The Intern Who Outworked the Veteran: Why Codex Fixed in 10 Minutes What Claude Couldn't in 2 Hours

I gave up on a bug, handed it to OpenAI's Codex almost as a joke — and watched the new kid solve it in 10 minutes with evidence, logic, and a slightly annoying smirk.

Learn the underlying concept

Learn

How to split work across two AI agents without merge conflicts

When two AI agents work on the same codebase in parallel, file-level collisions are inevitable without a deliberate coordination pattern. Protected lanes and explicit ownership boundaries solve this without requiring real-time communication.

Learn

Default-first fallback orchestration for AI generation pipelines

AI generation routes that call a single provider are brittle. Default-first fallback orchestration makes them resilient: try the configured primary, fall back automatically on failure, record what actually ran, and let users override for one run without changing the default.

If this resonated, I'd be happy to talk about it.

Find me →
← Back to articles