Case study · Stephano Group Ltd.
Outstanding supplier documents down 39% in the first weeks
Stephano Group Ltd. makes granola, bars and other snacks, including for co-manufacturing customers, at two facilities in Ontario. Its QA team kept supplier documents in two Excel matrices. Since 15 October 2026 the system that became Foodhelm has kept them instead.
Disclosure: Foodhelm was built inside Stephano by its operations team, and Stephano is its first user. Every figure here is from Stephano's own records, as of 14 November 2026, published with the permission of Stephano's owners. Stephano runs the same code as Foodhelm in its own installation (its Production Hub), connected to its ERP, JustFood.
At a glance
| Company | Stephano Group Ltd., Etobicoke, Ontario · two facilities · food manufacturer and co-manufacturer |
| Before | Two hand-kept Excel supplier matrices, one per facility; requests to suppliers by hand |
| ERP | JustFood (Aptean, on Microsoft Dynamics 365 Business Central) |
| Live | Matrix built from purchasing in October 2026; automated supplier requests since 15 October 2026 |
| Scope | 726 ingredient lines · 172 vendors · 166 manufacturing sites |
The problem: a matrix nobody could trust
When the old spreadsheets were reconciled against the documents actually on file, they claimed 1,583 documents that had no file behind them, and 699 whose date differed from the file's own. 115 lines turned out never to have been real requirements. Requests went out by hand, so whether a supplier was asked, and asked again, depended on who had time that week.
What changed
- The matrix was built from purchasing. Every ingredient bought from each vendor in JustFood's receipts and open purchase orders became a line; a new ingredient appears by itself at the next morning's read of the ERP.
- Suppliers are asked every morning. One e-mail per supplier lists everything outstanding for them, from the QA mailbox; two follow-ups two days apart; then escalation to a person.
- Replies are read and filed. Each document is matched to its lines and type and its dates are read. At Stephano a document is filed directly when the reading is certain, and goes to the Review queue otherwise; in Foodhelm every document goes to Review.
- Certificates are checked at the source. Each week Stephano's installation looks its kosher, organic, non-GMO and food-safety certificates up in their certifiers' public directories. The same check is now in Foodhelm.
The results
| Measure | Figure |
|---|---|
| Outstanding supplier documents | 2,167 (30 October 2026) → 1,317 (14 November 2026), −39% |
| Ingredient lines with every required document on file | 20 → 137 |
| QA time spent chasing supplier documents (Stephano's own estimate, not a time study) | about 20 hours a week → about 5 — 780 hours a year back |
| Requests sent | 223 to 131 suppliers, asking for 2,663 documents |
| Requests answered | 157 (70%) |
| Requests escalated to a person after two follow-ups | 146 |
| Supplier replies, 6 November 2026 to 14 November 2026 | 265 replies · 404 documents filed · 61 rejected on review · 4 left in the queue |
| Certificates whose certifier's directory disagreed with the file (status or expiry) | 27 |
How the figures are counted
A document is outstanding when an active ingredient line needs it under Stephano's rules and it is missing, expired, or due within the lead days. A supplier-level certificate is counted once, not once per ingredient. Archived lines are not counted. The count is the one in the matrix's daily status e-mail, worked out the same way every day.
The baseline is 30 October 2026, not the first day: until 28–30 October, requests to 69 suppliers had been going to a test mailbox during development, and the first fortnight was also held back by a cap of 40 requests a day. Stephano's target was 25% fewer outstanding documents, 1,625, as a four-week average by 31 January 2027; the daily count passed it on 9 November.
What is still outstanding, and why
Of the 1,317 documents still outstanding on 14 November 2026:
- 579 (44%) are for ingredients that Stephano's co-manufacturing customers supply. Closing them is a policy step, not a chase: a letter from each customer confirming that its own supplier-approval program covers what it ships.
- 394 are with suppliers who did not answer two follow-ups and are now with a person at Stephano.
- 233 had not been requested yet: requests are sent at a daily pace Stephano sets.
- 69 are in requests still open.
In other words, sending, following up and filing are no longer what holds the count up — which is where the QA team's 15 hours a week came back from. What is left is a customer policy and a list of suppliers for a person to call.
Talk to Stephano
Plants considering Foodhelm can ask for a reference call with Stephano's team. Say so when you request early access.
Try it on your own suppliers
Early-access plants start with a 30-day pilot, measured the way Stephano's results were.
- Week 1. Your matrix is built from your ingredient and supplier list or your ERP, your document rules are set with you, and your QA mailbox is connected.
- Weeks 2–4. Requests and follow-ups go to your suppliers each morning; what they send waits in Review for your QA team.
- Day 30. Your outstanding documents are counted again by the same rule as on day 1, and you decide whether to continue.