Foodhelm

Platform

Know which suppliers are approved, and why

Every supplier carries an approval status that a named person decides, beside a risk flag worked out from the records.

Coast Minerals3 ingredient linesConditional
High risk
  • Food safety certificate expired
  • Certifier's directory shows another date
  • Request unanswered after two follow-ups

A decision with a name on it

Approved, conditional or not approved. The status is a person's decision, kept with who made it and when, and its history stays.

  • Conditions and refusals need a note, so the reason is on the record.
  • A date to look again can be set with each approval.
  • Approving against a high flag needs a note too.
The Suppliers page of the product: each supplier with its approval status, its risk flag and the reason
Suppliers in the product, with a demo company's data.

A risk flag that explains itself

Low, medium or high. It is never typed in. It is worked out from what Foodhelm already holds, and it lists its reasons.

  • High: a required food-safety certificate is expired or missing, or a certifier's directory says a certificate is not valid.
  • Medium: a directory disagrees or does not list the certificate, a request was escalated, another required document expired, or there is no contact to ask.
  • Low: none of these.
  • HighFood safety certificate expired
  • MediumRequest escalated after two follow-ups
  • LowEvery required document on file

The annual specification review

Once a year the state of every specification is captured as it stands, with a summary, follow-up actions and an administrator's approval.

  • Findings are a snapshot. Later changes to the matrix do not move them.
  • Actions carry an owner and a date.
  • An approved review is kept exactly as approved, and prints cleanly for an auditor.
The annual specifications review in the product: findings, a summary and follow-up actions with owners and dates
The annual specification review in the product, with a demo company's data.
172

vendors and 166 manufacturing sites sit on Stephano Group's matrix, each with its documents, requests and decisions in one place.

See it on your own suppliers in 30 days

Every plant starts with a pilot on its own supplier list, measured the same way Stephano's results were.

  1. Week 1

    Your matrix, live

    Built from your ingredient and supplier list or your ERP. Your document rules are set with you and your QA mailbox is connected.

  2. Weeks 2 to 4

    Suppliers answer

    Requests and follow-ups go out each morning. What suppliers send is read and waits in Review for your QA team.

  3. Day 30

    The count, again

    Outstanding documents are counted by the same rule as on day one. You see the difference and decide.