Run a restaurant's back office through an OpenClaw agent: supplier price-change alerts, invoice uploads and a fairer tip split

Posted

Apr 22, 2026 by Christopher Thépot (LinkedIn)

·

Last checked

Oct 19, 2026

·

Method:

How we verify

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Outcome

Christopher Thépot runs restaurant operations in Madrid and spent a month using OpenClaw. The agent answers point-of-sale questions over WhatsApp and combines supplier invoices, sales data, recipes and inventory counts to track waste and what's missing. It flags supplier price spikes; two pricing mistakes caught so far directly affected the P&L. It also pulls supplier invoices from their inbox into the accounting software's scanner, saving one to two hours a week, though they're still fine-tuning that. They used it to design and test a new tip policy in under an hour: 80% stays with the shift and 20% goes to a pool split by hours worked.

Agent

OpenClaw

The source didn't share its exact prompt, so we wrote this from what it describes.

Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points.

Goal: Catch supplier price changes and invoice mistakes for my restaurant before they hit my margins.

What I can give you (ask for whatever's missing):
- Supplier invoices (PDF or email): [UPLOAD]
- My agreed prices or last month's prices per item: [PRICE LIST]
- How big a change should alert me: [THRESHOLD]

Check any change to staff pay or tips against local labour rules.

Rules:
- Read every line: item, unit, quantity, unit price.
- Compare with the last price paid for the same item and unit, and flag changes over my threshold.
- Flag maths errors, duplicate invoices and items I don't remember ordering.
- Draft a short, polite query to the supplier for each problem; don't send it.
- If a site asks me to sign in, pause and let me do it myself (including any CAPTCHA or two-step code); never guess or store passwords.
- Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify.

Output: A weekly table of price changes and errors, with the cost impact and a draft supplier message for each.

You'll know it worked when: No price change or invoice mistake goes unnoticed for more than a week.

Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points.

Goal: Catch supplier price changes and invoice mistakes for my restaurant before they hit my margins.

What I can give you (ask for whatever's missing):
- Supplier invoices (PDF or email): [UPLOAD]
- My agreed prices or last month's prices per item: [PRICE LIST]
- How big a change should alert me: [THRESHOLD]

Check any change to staff pay or tips against local labour rules.

Rules:
- Read every line: item, unit, quantity, unit price.
- Compare with the last price paid for the same item and unit, and flag changes over my threshold.
- Flag maths errors, duplicate invoices and items I don't remember ordering.
- Draft a short, polite query to the supplier for each problem; don't send it.
- If a site asks me to sign in, pause and let me do it myself (including any CAPTCHA or two-step code); never guess or store passwords.
- Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify.

Output: A weekly table of price changes and errors, with the cost impact and a draft supplier message for each.

You'll know it worked when: No price change or invoice mistake goes unnoticed for more than a week.

Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points.

Goal: Catch supplier price changes and invoice mistakes for my restaurant before they hit my margins.

What I can give you (ask for whatever's missing):
- Supplier invoices (PDF or email): [UPLOAD]
- My agreed prices or last month's prices per item: [PRICE LIST]
- How big a change should alert me: [THRESHOLD]

Check any change to staff pay or tips against local labour rules.

Rules:
- Read every line: item, unit, quantity, unit price.
- Compare with the last price paid for the same item and unit, and flag changes over my threshold.
- Flag maths errors, duplicate invoices and items I don't remember ordering.
- Draft a short, polite query to the supplier for each problem; don't send it.
- If a site asks me to sign in, pause and let me do it myself (including any CAPTCHA or two-step code); never guess or store passwords.
- Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify.

Output: A weekly table of price changes and errors, with the cost impact and a draft supplier message for each.

You'll know it worked when: No price change or invoice mistake goes unnoticed for more than a week.

Before you finish: re-read my goal and constraints, check your answer against each one, and list anything you assumed or couldn't confirm.

Source

https://www.linkedin.com/posts/christopher-th%C3%A9pot-03217391_openclaw-activity-7452697032458334209-S_6n