For the ingredient supplier

Every customer asks for the same statements. Answer once, and keep answering with the same link.

Allergen. GMO. Kosher. Halal. Heavy metals. Residual solvents. The list barely changes from buyer to buyer. What changes is who's asking, on what schedule, and whether you can still find last quarter's version when they ask again.

No card, no account, and no call to book. Tell us what you make and where you sell it, and we will come back to you.

The shape of it

The supplier's shape

The same twelve statements, asked twelve different ways. Answer once and keep answering from one place.

In

What arrives

  • Your specification and your own written statements
  • Your certificates, and the dates they run out on
  • A customer questionnaire, again

The middle

What the department does

  • Read it and place it, or say plainly it could not be placed
  • Match it against the rules that apply, with the citation on every line
  • Keep it current, and name what is missing before somebody asks for it

The same engine, whichever door you came in through

Out

What you hand back

  • One statement library, answered once and reused
  • A link that stays current when the document behind it changes
  • The questionnaire returned in the asker's own file, with anything missing named

Who is asking: Every brand and manufacturer who buys from you

The mechanism

Meet the team that holds every statement once

13 standing document kinds, allergen through novel-food status, held the same way any document is: with the file it came from, a validity window, and a status that never quietly goes stale.

Intake

Reads every document on arrival

Reads any document a supplier sends, in whatever layout it arrives, and files it against the right product and lot.

Automatic
Classification, extraction and filing run on arrival. No folder structure, no data entry, no template per manufacturer.
Needs you
Anything read with low confidence, or in a unit that could be two things, waits in your review queue instead of entering the ledger. “We could not read this” is always an available answer.

How a document travels

Verify

Checks every value against the rules

Checks every extracted value against the requirements resolved for that product and against your own specification, stricter limit applied, each line carrying its citation.

Automatic
Resolution and the comparison. Where two authorities bound the same analyte, the stricter limit is applied and the other is recorded, not discarded.
Needs you
Rows where no public authoritative number exists are shown as advisory and can never be reported as a failure. Verify checks the values, the specification leg, and the label leg: a label version's artwork against the required elements for its market, with an element it could not read held for a person rather than passed.

The requirements library, with its citations

Keep

Holds the record and hands it back

Holds every document traceable back to the original bytes, answers questions from the file with citations, and hands the whole thing back whenever you ask.

Automatic
Filing, indexing, and the append-only history. Every change is written; nothing is overwritten and nothing is hard-deleted.
Needs you
Nothing. Keep does not decide anything. It is the record the deciding is done against, which is why it is append-only.

Collect

Asks your partners for what is still owed

Turns every document a partner still owes you into a request that is already written: a no-login upload link and a message you can paste straight into your own thread.

Automatic
Drafting the request, minting the upload link, and filing whatever arrives. The manufacturer never makes an account and never sets a password.
Needs you
Sending is yours. Follow-ups on day 5 and 12 exist, but they are off until you turn them on, per manufacturer or per request. Most brands would rather run their own factory relationships.

Assemble

Builds the pack a reviewer asks for

Builds the outbound pack a reviewer accepts, from templates, complete, ordered the way the recipient expects, and pre-flighted before it goes.

Automatic
Staging, ordering and the pre-flight. A pack missing a document the recipient requires is refused before it is generated, with the reason.
Needs you
The signature is always a named person at your company. Nothing leaves without it. The three templates are there, and so is a fourth way to build one: a buyer’s own layout, learned from what they send you, checked once by somebody here, and reused every time.

The proof

See answer-once end to end

Short recordings of the real product. Where the recording doesn't exist yet, the slot says so and stays empty, never a staged screenshot.

KeepRecording coming

Answer once, standing

File your allergen statement, your kosher certificate, your heavy-metals declaration, each held with its own validity window. When one lapses, renew it once; every link pointing at it is current again by itself.

Recording slot: empty on purpose

Recording coming. The capability ships today; the screen recording of it does not exist yet, and we would rather leave the slot empty than stage one.

Where this ingredient is permitted

A real projection over the requirements graph, read honestly, including when it's thin

Where the compiled rule graph names an ingredient by predicate, this reads that graph from the ingredient's own angle instead of a market's. It runs no new sweep and invents nothing: it shows what the graph already says, which today is not much.

The compiled dataset today carries no rule that references an ingredient by name. That is the honest state of a dataset built around contaminant limits and structural requirements, not an ingredient registry. This grows the moment ingredient-scoped rule content lands, with no code change here.

Their format

Shipped

Fill in a buyer’s own questionnaire

Upload the spreadsheet, Word file or PDF a buyer sent you. Every question is read out of their own file and answered from the statements you already hold, and the file goes back in the shape it arrived in, cell for cell. Their layout is learned once, checked by somebody at your company, and reused the next time that form lands.

The boundary

Nothing is guessed and nothing is left blank. A question you hold nothing for comes back naming the document that would answer it, and a statement past its renewal is treated as missing rather than quietly reused. A Word form comes back as a new file in their question order rather than edited in place.

Where it starts

Free

1 product, forever

Free, forever

Your first product, free

Not a trial and not a sample: the whole product on one catalog item, in as many markets as you like, with every agent, every document and full export. It never expires.

No card, no account, and no call to book. Tell us what you make and where you sell it, and we will come back to you.

The questions people ask

What counts as a "statement" here?
Any standing declaration a buyer asks for that isn't a lot-specific test result: allergen, GMO, BSE/TSE, residual solvents, heavy metals, pesticide, kosher, halal, vegan, country of origin, food-grade, and novel-food/NDI status. Each is registered as its own kind, with its own typical validity window where one exists, and a plain "no standard window, review annually" where it doesn't, never treated the same as a missing date.
Do I have to re-answer every buyer's own questionnaire format?
No. Upload the file they sent and it comes back in the same shape, with the answers written into their own cells from the statements you already hold. Their layout is learned once, checked by somebody at your company before it is used, and reused every time they send that form again. Anything you do not hold comes back naming the document that would answer it.
Does a buyer need an account to see what I publish?
No. A published link opens on any phone, no login, no password. It shows only what you chose: a pinned document, or a standing selection like "current allergen statement" that resolves to whatever is current when they open it.
What about ingredient-specific rules: is that mapped?
There's a real projection over the compiled requirements graph asking exactly that question, and we'd rather show you its honest current answer than a promise: read on below.
Can I chase my own upstream suppliers with the same tool?
Yes. The request mechanism that publishes downstream is the same one that chases upstream: a no-login upload link and a written request either way, direction set per relationship.

Answer the statement zoo once.

One statement, published once, behind a standing link that answers a customer for you. Get in touch and we will take you through it on the ingredients you actually supply.

No card, no account, and no call to book. Tell us what you make and where you sell it, and we will come back to you.