Interactive demo. A Seaton Labs automation, shown with sample orders.Read the case study ↗

Order Intake · automation

The order arrives by email. Nobody types it in.

Each restaurant’s purchasing system emails its order to the central kitchen as a PDF. This pipeline catches it, reads every line, matches it to a real item and puts it on tomorrow’s prep list, usually within a few minutes and with no one at a keyboard.

Email arrives

A dedicated inbox receives the PO and its PDF.

Queued safely

The PDF is saved to cloud storage, so nothing is lost.

Read

Every line, quantity and unit is pulled out of the PDF.

Matched

Each line is matched to a real item, including names it has learned.

On the prep list

The kitchen sees the order on tomorrow’s list.

Run log
  1. Press “Send a sample order” to watch a run.

What the kitchen gets

No order yet


Lines from the PDF land here, already matched.

Daily watchdog

Silence means everything ran.

Automations fail quietly, so a second job checks the first. Every afternoon it confirms each scheduled job actually ran today, and emails the owner only when one didn’t. On Mondays it sends an all-clear, so you know the watchdog itself is alive.

Owner’s inbox

In the real build

The same pattern, four times over.

The client project behind this demo automates several of the emails and reports a busy kitchen used to handle by hand.

Purchase orders

Orders from each restaurant go straight onto the central kitchen’s prep list.

Reservations

Daily booking digests become tonight’s cover counts on the dashboard.

Payroll punches

Short punches and forgotten clock-outs get flagged before they throw off tip pooling.

Watchdog

One daily check that every job above actually ran.

Sample orders for a fictional restaurant group. A client build connects to your own inboxes and systems.← Back to Automation