The order that could not be filled, saved before anyone noticed.

Triggered by an order event. Ends with a customer who was offered a choice instead of an apology.

A short-shipment is usually discovered twice: once by your warehouse, and again by an angry customer a week later. This recipe closes that gap. The order event wakes an agent, it checks what is actually available, it calls the supplier for a date, and it comes back to the customer with real options while the order is still recoverable.

What the agent does, in order

One trigger, one chain, one job ID from start to finish.

Availability check

Reads live stock and commitments out of Business One rather than the number somebody exported this morning.

Supplier call

Phones or messages the supplier for a real date, and parks the run while it waits for the answer.

Customer options

Comes back with the choices that actually exist: part-ship now, wait for the date, substitute, or cancel.

Write it back

Whatever the customer chose is written into Business One, so the warehouse and the ledger agree.

Why it pays

Short-shipments are expensive in ways that never make it onto an invoice.

The customer keeps the order

Offered a choice, most customers take one. Told nothing, they cancel and call a competitor.

Nobody had to notice

The recipe runs on the event, not on somebody checking. It works at two in the morning.

The record is clean

One job ID ties the check, the supplier call, the customer conversation and the write-back together.

Outcome it is built to move: short-shipments prevented. The orders that would have gone out incomplete, saved before the customer ever knew.

If short-shipments are costing you customers rather than just margin, this is the recipe to start with.