Integrations
Works with the systems your plant already runs
The status of each connection, stated plainly: what runs every day at Stephano, what is built and switched on with you, and what comes next.
Your ERP: the matrix built from what you buy
Foodhelm reads which ingredient is bought from which supplier — receipts and open purchase orders — and turns each pair into a line of the matrix. Lines are added and kept, never removed by a read; a line you no longer buy is proposed for archiving to a person. Nothing is written to your ERP, and you see a dry run before the first read is applied.
| System | How it connects | Status |
|---|---|---|
| JustFood / bcFood (Aptean) | Business Central OData web services | Building Stephano's matrix daily since October 2026 |
| Microsoft Dynamics 365 Business Central (online) | Business Central API v2.0 | Ready — first live connection with you |
| Oracle NetSuite | SuiteQL, token-based authentication | Ready — first live connection with you |
| Odoo | JSON-RPC | Ready — first live connection with you |
| SAP Business One | Service Layer | Ready — first live connection with you |
| Any other system | An .xlsx or .csv export of ingredients and suppliers | Ready |
Each connector is built from its vendor's published API and tested; the first plant on each system proves it live with us before it relies on it. Asked for next: QuickBooks, Sage, Dynamics GP and F&SCM, Acumatica, Infor, Epicor, SYSPRO, Deacom, Plex, Xero and Fishbowl — tell us yours when you request access; demand decides the order.
Your mailbox: requests that come from your QA team
| Mailbox | How it connects | Status |
|---|---|---|
| Microsoft 365 / Outlook | Microsoft Graph, with your administrator's consent | Running at Stephano since 15 October 2026 In Foodhelm: connected with you |
| Google Workspace / Gmail | Gmail API | Ready — connected with you |
| A mailbox Foodhelm provides | Requests go from an address on our domain, replies come back to it | Ready — set up with you |
Requests go out each business morning, in your time zone, with two follow-ups and then escalation to a person on your team. Replies that answer a request are read and filed into Review; mail from unknown senders is not read.
Certifier directories: certificates checked at the source
Each week Foodhelm looks every kosher, organic, non-GMO and food-safety certificate on file up in its certifier's own public directory, by the identifier printed on the certificate, and sets what the directory says against the date on file. Where they differ — another date, another holder, not valid, not listed — it is flagged for a person and shows in the supplier's risk flag. A newer certificate the directory offers is downloaded and waits on Review; nothing is filed by itself. Stephano's installation has run these checks weekly since November 2026 and they have flagged 27 differences; in Foodhelm the first live run is with the first plant.
| Directory | For | Status |
|---|---|---|
| OU Kosher | Kosher — the letter of certification, with its file | Ready — first live run with you |
| Star-K | Kosher — the account's current letter | Ready — first live run with you |
| USDA Organic INTEGRITY | Organic — the operation's status | Ready — first live run with you |
| SQF certified site directory | Food safety — certificate, expiry, status | Ready — first live run with you |
| Non-GMO Project | Non-GMO — verified or not | Ready — first live run with you |
| COR (Kashruth Council of Canada) · FSSC 22000 public register | Kosher · food safety | Built; the sites currently refuse automated look-ups |
| Kof-K · BRCGS Directory | Kosher · food safety | Answer only to a signed-in account — not looked up yet |
A certificate from a certifier with no public directory is said so, and stays on its expiry date alone.
Signing in
A password, your Microsoft account or your Google account. Microsoft and Google sign-in are switched on with you during onboarding.
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.