Logistics and supply chain
What happens when an agent gets it wrong at 2am?
Shipments, carriers and warehouses run around the clock, and so do your agents. LeafCraft makes failures stop safely and sends work to a backup when a person does not act in time.










What's changing in logistics and supply chain
Exceptions happen at 2am
A delayed shipment, a rejected freight invoice, a reroute. Agents handle them when nobody is awake.
Freight invoices are a leak
An agent that approves a freight invoice with no checker is a cost you find at audit.
Carriers and 3PLs bring their own agents
Your operation now includes agents from partners you do not control.
Two risks the layer removes
The agents you can't see, and the model that gets retired.
Agents you don't know about
In logistics and supply chain, agents arrive through vendor updates and team pilots. LeafCraft finds all of them, gives each an owner, and brings it under your rules or removes it.
A model that gets retired
An agent built straight on one model has to be rebuilt and re-approved when that model is retired or repriced. On LeafCraft you switch the model for that agent in config and keep everything else. Months and a budget, saved.
- The model is retired or repriced
- Prompts, tests and sign-offs rebuilt
- Months of work, a new approval cycle
- The history stays with the old tool
- Pick another model for that agent
- Switching is a config change
- Test it against your own record first
- Rules, limits, owner and memory stay
Why it matters now
In logistics and supply chain, the agents arrived before the rules did.
Logistics never stops, and the agents that keep it moving make decisions while your people sleep. The layer defines what an agent may do alone at night, what must wait for a named person, and what happens when nobody replies. It records every exception and every reroute, so the morning starts with a record, not a surprise.
The core infrastructure
What LeafCraft runs for logistics and supply chain.
One team
Exceptions go by complexity and impact to named people on duty: the ops lead, the backup, then the regional head.
How it works02Your rules
You decide what rerouting, invoice and update agents may do alone, what needs an ops lead, and what they may never change, such as a contracted rate.
How it works03Your memory
Every reroute, invoice and exception decision is kept with the reasons of the agent and the person, on your side for customers and auditors.
How it works04Your budget
Every shipment task, agent and agent type has a cost limit set before the work runs, so an overnight failure cannot run up the bill.
How it worksAI and people, one team
Your logistics and supply chain team, with AI on the org chart.
The agent prepares the case. Your person makes the call and writes why. A separate audit agent checks the decision against your rules.
What changes for you
Port delay detected. Proposed reroute via Nhava Sheva.
Passed to the night control tower.
Approved.
Checked the decision against the rules. Passed.
How it helps your people
Who it helps in logistics and supply chain.
Leaders who ask first
Questions teams ask
What if something goes badly wrong overnight?
A step that keeps failing is stopped and handed to a person, not retried all night. One switch pauses the whole operation across every server, work in progress included, until you resume.
Can our ops team approve from their phones?
Yes. Requests reach the people you name on Slack, Microsoft Teams, WhatsApp (coming soon), Telegram or email, and their reply moves the work on. Replies over email or Teams are checked to come from the right sender.
Can agents react to events from our TMS and WMS?
Yes. Work can start from webhooks, Kafka, Amazon SQS, MQTT, Redis Streams, an email inbox or a schedule you set.
Bring one logistics and supply chain process.
We'll map it with you: which roles are AI and which are people, who decides, who checks, what it costs and what gets recorded.