For the contract manufacturer

Every customer asks for the same paperwork, in a different format. Answer all of them in an hour.

You run the tests once. Then five customers each want the result their own way: one by email, one through a portal, one on a schedule nobody wrote down. The lab result never changes. Only the retyping does.

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 manufacturer's shape

You run the test once. The retyping is the only part that repeats, and it is the part that goes.

In

What arrives

  • Your own lab results, lot by lot
  • Your certificates and audit reports
  • A customer asking for the same result in their own shape

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

  • A certificate composed from measurements you already recorded, signed by a named person
  • A standing link per customer that shows the current document, with nothing to reissue
  • The same answer written back into a buyer's own form, in their file

Who is asking: Every customer who buys from you

The mechanism

Meet the same team, pointed the other way

Nothing here is a manufacturer edition of the product. It's the same substrate a brand customer uses, with direction set per relationship (10 §6). What a brand runs to chase you, you run to answer everyone else.

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 the two moves that end the retyping

Short recordings of the real product, one narrow job at a time. Where the recording doesn't exist yet, the slot says so and stays empty.

AssembleRecording coming

Compose and sign an outgoing COA

Pick a lot. Its recorded measurements fill the certificate; anything never measured is named as missing, never blank. A named person signs it, and until then it's a watermarked draft with no ledger document at all.

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.

CollectRecording coming

One upload, every customer's view updates

Publish a standing link once per customer: "current COAs for Product X." The next time you file a newer one, every link that resolves to it shows the new document. No reissuing, no re-sending, no customer ever emailed again for something already on the link.

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.

Their format

Shipped

Hand a customer back their own questionnaire, filled in

Upload the spreadsheet, Word file or PDF a customer sent you. Their questions are read out of their own file, each one answered from what you already hold, and the same file comes back with the answers in the cells they left for them. Their layout is learned once, checked by somebody at your company, and reused the next time they send it.

The boundary

Nothing is guessed. A question you have nothing on file for comes back naming the document that would answer it, never blank and never filled in with something plausible. A Word form comes back as a new file in their question order rather than edited in place, and nothing leaves until a named person here signs it.

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

Does this replace my LIMS or my lab's own report?
No. The certificate is composed from measurements you've already recorded against the lot, your lab's own results, filed once. Nothing is estimated, defaulted, or carried over from a similar lot: an analyte with no recorded measurement is named as missing on the document, never left blank and never filled with a typical value.
Do my customers get a login?
No. A published link opens on any phone with no account and no password. It is the same no-login page a customer already gets today when you send a document by email, except this one updates itself. There is no upload path on it either: it only ever shows what you chose to publish.
What happens when I update a document?
Depends what you published. A standing selection ("current certificates of analysis for this product") resolves fresh every time the link is opened, so a newer document replaces the old one on every customer's view with no new link and no re-send. A pinned document stays exactly what you pinned until you change the selection yourself.
Who actually signs the outgoing certificate?
A named person at your company, every time. A draft is watermarked and cannot be published until someone with the signing right signs it. The system prepares the document; a human puts their name on it before it leaves.
Can I chase my own ingredient suppliers with this too?
Yes. The same request mechanism runs both directions. Upstream, it drafts the ask and mints your supplier a no-login upload link; downstream, it publishes what you choose to your customers. One substrate, direction set per relationship.
Can you fill in my customer's own questionnaire?
Yes, if they sent it as a spreadsheet, a Word file or a PDF. Their questions are read out of their own file, each one answered from what you already hold, and the same file comes back with the answers in it. Anything you do not hold on the day comes back saying so, and saying which document would answer it, rather than blank or guessed. A portal somebody has to log into is a different job and is not this one.

Stop re-typing the same result.

A certificate that builds itself from the measurements you already recorded, signed and sent, market by market. Get in touch and we will take you through it on the documents you actually issue.

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.