A drafted RFQ, a drafted sample request — and a human click before either one sends.
Tamats keeps a record of manufacturer contacts, generates a structured RFQ email listing every formulation ingredient with its INCI, target percentage, quality grade and MOQ ask, and drafts sample-request or general outreach the same human-in-the-loop way — every draft is exactly that, a draft, and nothing sends until a person clicks send. Sending itself needs a mailbox the organisation has connected (Google or Microsoft); without one, a draft still gets written and simply waits, and it never falls back to a shared platform sender that would put a reply in the wrong inbox. Inbox search reaches threads already linked to a manufacturer or influencer contact — mail outside that scope is invisible to it, not absent.
Sourcing is a relationship run over email, and most of the actual work is drafting the same information — the ingredient list, the target percentages, the quality grade — into a form a manufacturer can quote against, then keeping track of who replied. Tamats writes the first draft from the formula itself so the ingredient list is never re-typed by hand, and treats sending as a decision only a person gets to make.
What you do with it
Structured RFQ generation
Every ingredient in a formula — INCI name, target percentage, function — drops straight into an RFQ template with a quality grade and MOQ ask, so the manufacturer gets exactly what's in the formula, not a paraphrase of it.
Manufacturer contacts, held in one place
Contacts carry name, country, email, specialties and a note field, so evaluating several manufacturers side by side doesn't depend on a separate spreadsheet.
Draft outreach, human-confirmed
An RFQ or sample-request draft is written and queued with a status badge; it only sends once a person approves it, and only through a mailbox the organisation has actually connected — never a shared fallback sender.
Inbox search over linked threads
Search the organisation's own connected mailbox for a keyword and get back matching manufacturer- or influencer-linked threads with snippets — scoped honestly, so a miss is reported as outside what this can see, never as proof no such mail exists.
What it computes over
—The formula's own ingredients, percentages and functions
—The organisation's own manufacturer contact records
—The organisation's own connected mailbox threads, where one is connected
Where it stops
Nothing sends without a human clicking send — every RFQ, sample request or outreach draft is confirm-before-send, with no exception.
Sending needs a connected mailbox (Google or Microsoft). Without one, a draft is still written and waits — it never sends through a shared platform address instead.
Inbox search reaches only threads already linked to a manufacturer or influencer contact; mail outside that scope is not searched, and a miss there is not evidence the mail doesn't exist.
Who picks it up from here
The manufacturer contacted, once a human on your side reviews and confirms the draft — the reply, the quote and the relationship from there are between the two of you.
Questions
Will an RFQ or sample request actually send to the manufacturer on its own?
No — every draft is exactly that, a draft. It's written and queued with a status badge, and only sends once a person on your team reviews it and clicks send, through a mailbox your organisation has connected. There is no automatic-send path.
What happens if my organisation hasn't connected a mailbox?
The draft still gets written and waits in the queue — it simply can't send yet. Tamats never falls back to a shared platform address to send on your behalf, because a manufacturer's reply would land somewhere you can't see it.
Can I search for an email I sent a manufacturer a while back?
Yes, if it's in a thread already linked to that manufacturer contact — search reaches those threads with a keyword and returns matching snippets. Mail that was never linked to a manufacturer or influencer contact is outside what this search can see.