Foodhelm

Supplier compliance for food plants

Supplier documents that chase themselves.

Foodhelm builds your ingredient-supplier matrix from what you actually buy, shows every certificate, specification and statement that is missing or about to expire, and files what suppliers send for your QA team to approve. Audit day becomes an ordinary day.

Built inside a working food plant, by the people who run it.

Food safetySpecKosherOrganicNon-GMO
Rolled oatsPrairie MillsJun 2027On fileDue 12 dN/AOn file
HoneyBee Co-opExpiredOn fileMar 2027N/AMissing
Organic almondsValley GrowersJan 2028In reviewSep 2027Nov 2027On file
Sea saltCoast MineralsAug 2027MissingFeb 2028N/AOn file
4 of 312 ingredient lines37 documents outstanding

The first plant, in its first month (15 October – 14 November 2026)

726ingredient lines across 172 vendors, built from purchasing — not typed in
223document requests sent to 131 suppliers, with follow-ups
70%of requests answered
−39%outstanding supplier documents, from 2,167 to 1,317

How it works

  1. 1

    Start from what you buy

    Load your ingredient and supplier list from a spreadsheet today; from your ledger next. Each ingredient from each supplier becomes a line, and your rules decide which documents that line needs: a food safety certificate for every supplier, an organic certificate where the name says organic, a specification reviewed every year.

  2. 2

    See exactly what is outstanding

    Every required cell is on file, due, expired, missing or not applicable — worked out from the document's own dates each time you look. A supplier's certificate is held once and covers every ingredient that supplier sells you.

  3. 3

    Documents are read, then approved by a person

    When a document arrives, the system reads it: which document it is, who holds it, when it expires. It then waits in a Review queue. Nothing is filed until someone on your team accepts it, and every acceptance and rejection is logged with their name.

  4. 4

    Stay current without the spreadsheet

    Expiries are watched for you, the outstanding count is measured the same way every day, and the audit trail is there when the auditor asks who approved what, and when.

In the product today

  • Your matrix from a spreadsheet of ingredients and suppliers (.xlsx or .csv)
  • Twelve document types with rules you set per type: every line, by ingredient name, or never
  • Expiry and review dates tracked per document, with lead days you choose
  • Upload a document; it is read and proposed for the right line and type
  • A Review queue: accept or reject, with a reason, by name
  • Supplier-level certificates that cover every line of that supplier
  • Team roles: owner, admin, member, read-only
  • Sign in with a password, Microsoft or Google
  • A full log of who changed what

Arriving next

  • Requests to suppliers sent for you each morning from your own QA mailbox, with two follow-ups and escalation to a person
  • Supplier replies read and filed straight into the Review queue
  • A daily digest: what expired, what is due, what came in
  • Your matrix built from Business Central or JustFood receipts and open purchase orders
  • Checks against public certification registries
  • An assistant that answers questions over your own records, citing each one

All of this already runs at the first plant. It reaches early-access plants in stages over the coming weeks.

Your data stays yours

Separate by design

Each company's lines, suppliers, documents and logs are kept in a database schema of their own. There is no shared table for a query to filter wrongly.

A person approves

The system proposes; your team decides. It makes no release, approval or recall decision, and nothing it reads is filed without a named person accepting it.

No training on your documents

Your data is not used to train models, build benchmarks or feed any index unless you opt in, in writing, with a name and a date.

Request early access

We are working with a small group of food plants as design partners. Tell us a little about yours and we will reply personally.

We use what you send only to reply to you.