Skip to content

Know what every batch yielded, gave away and cost

Connect your production and ERP data and ask in plain English: yield against the recipe, giveaway by filler, batch cost against standard, stock close to its date. Then keep the morning line report and the QA hold watch on a schedule.

For food processors, bakeries, dairies and beverage producers, and the plant, QA and finance teams that run their lines.

Free plan. No credit card required.

Try a question

All 10 questions

ChatPlant agent

Giveaway % by filler yesterday, against the 1% target

AI Analyst

F2 gave away 1.9% yesterday: 9.5 g on every 500 g pot, or 391 kg across 41,200 pots. The other fillers stayed under the 1% target.

F1 Greek 500 g0.7%
F2 Greek 500 g1.9%
F3 Fruit 125 g0.8%
F4 Milk 1 L0.6%

1% target

Readcheckweigher_readingsfillersproductsSQL

Keep itPin to dashboardEmail it weeklyAlert me

Sample data

Ask this on your own data

Every question, by who asks it

Taken from what teams in this industry ask Supaboard. Each one opens a free account with the question waiting.

01 · Lines and yield

02 · Quality and traceability

03 · Stock, shelf life and waste

Keep it running

What teams keep on a schedule once they've asked the question once.

Report · Daily 06:00

Yesterday, line by line

Yield, giveaway and QA rejections for every line and shift, summarised in the plant manager's inbox before the morning meeting.

  1. Timed Start
  2. Query Your Data
  3. Summarize Insights
  4. Send Email

Alert · Every 5 minutes

QA holds past 48 hours

A SQL check finds lots on QA hold for more than 48 hours and emails the QA manager with the reason and the quantity held.

  1. Alerts
  2. Send Email

Datasite · Every morning

The plant datasite

Today's holds, short-dated stock and yesterday's yield by line, on a private datasite the plant, QA and sales teams sign in to with Google or Microsoft.

The numbers it keeps watch on

Standard definitions, and where each one lives in Supaboard once you've asked for it.

MeasureDefinitionSourceIn Supaboard
YieldGood output ÷ the recipe's theoretical output for the ingredients usedCommon practiceDaily report, by line
Giveaway(Average filled weight − declared weight) ÷ declared weightCommon practiceDaily report, by filler
Packs short of the limitPacks below their declared quantity by more than the limit for their size: the TNE in UK average-quantity rules, the MAV in NIST Handbook 133UK Packaged Goods Regs 2006; NIST Handbook 133A rule, then the daily report
Batch cost varianceActual batch cost − standard cost for the actual output, split into price, usage, labour and packagingCommon practiceMonthly report
Short-dated stockStock within N days of its use-by or best-before date, by warehouse and lotCommon practiceMorning report
QA hold timeHours from hold to release or rejection, by reasonCommon practiceAlert at 48 hours
WasteKilograms written off by reason, valued at standard costCommon practiceMonthly question
Lot traceIngredient lot to finished lots to customers, linked by lot code at receiving, production and shippingFDA 21 CFR 1 Subpart S, for listed foods; not enforced before 20 Jul 2028Ask it when a supplier calls

Where your data lives

Or attach an export to a conversation, as CSV or Excel:

  • XLSCheckweigher exportsUpload

The tables these questions read:

  • Production batches and lots, with expiry dates and line hours
  • Recipes and bills of materials, with standard yields and costs
  • Checkweigher readings: filled against declared weight, by filler
  • QA holds, releases and rejections, with reasons
  • Ingredient receipts by supplier lot, and lot consumption by batch
  • Sales, dispatches and stock by lot and warehouse

Teach it your definitions once

Rules are read with every question, so a term means the same thing in Chat, in Slack and in the Monday report.

  • Rule“Yield is good output ÷ the recipe's theoretical output for the ingredients used, in kg.”
  • Rule“Giveaway is the average filled weight over the declared weight; underfills are counted apart.”
  • Rule“Short-dated means within 14 days of the use-by or best-before date.”
How rules work

Security

Read-only by construction

Database and warehouse queries are read-only. We give you the SQL for a read-only user too.

Credentials stay in the workspace

Scoped to the one workspace that connected them, never logged and never sent back to a browser.

SOC 2 Type II

An organisation-wide audit of the platform, covering every plan.

Frequently asked questions

Can it read our checkweigher data?

Yes. If the readings land in a table in a database you connect, giveaway by filler is one question and can go in the morning report. For a one-off look, attach a CSV export to a conversation and ask about it.

Can it trace a supplier lot to the customers who received it?

Yes, when your records link ingredient lots to batches and batches to dispatches. Ask for the lot, and the answer lists every finished lot made from it, where each one shipped and what is still in stock.

How does it learn our definition of yield?

Write it once as a rule, such as "yield is good output ÷ the recipe's theoretical output". The agent reads its rules with every question, and you can save reviewed SQL as examples.

Can the plant get yesterday's numbers every morning?

Yes. An automation runs at 06:00 in the plant's timezone, queries yesterday's batches, summarises them and emails the plant manager.

Can it change anything in our ERP or production records?

No. Database and warehouse queries are read-only. We give you the SQL to create a read-only user.

Ask your first question on your own data

Connect a source, ask in plain English, and keep what you find.

Start FreeBook a 30-minute demo

Free plan. No credit card required.