Purchasing
Recognise the part behind the quote.
ADAM checks vendor references against your catalogue and keeps unresolved lines visible for review.
Your catalogue. The right part in context.
From vendor quotes to a draft you can approve.
ADAM reads incoming quotes, resolves lines against your catalogue and brings purchase history into the pricing decision.
Check vendor quotes against your catalogue.
Document → check → resultIllustrative workflow
- DocumentVendor quoteParts & quoted prices
- Part reference
- P-1042
- Source
- Supplier attachment
- ADAM checksCatalogue matchHistory informs pricing; you decide.CataloguePart reference resolvedPurchase historyPrevious price context
- ResultPurchase orderCatalogue context travels with the draft.Draft for approval
Start with the vendor quote. ADAM reads the parts and prices from the attachment. Bring your own records alongside it. Catalogue resolution and purchase history support the pricing decision. A clear draft for a person to approve. This matched example is ready for review. A person decides when to send.
What gets checked?Catalogue resolution, price context and human approval
Catalogue results
ADAM distinguishes matched, multiple candidates, absent, unreadable and blank. An unreadable lookup is held for review.
Price context
Purchase-history benchmarks inform the reviewer. They do not automatically reprice or block a draft.
Your decision
A person marks the draft to send. A failed lookup is not treated as evidence that a new part should be created.
From supplier quote to a confident decision.
Catalogue context, price history and a draft your team controls.
Purchasing
Recognise the part behind the quote.
ADAM checks vendor references against your catalogue and keeps unresolved lines visible for review.
Your catalogue. The right part in context.
Commercial team
Put the quoted price in context.
Your purchase history travels with the quoted line, so the approver can assess it without a second lookup.
Price history beside the supplier quote.
Approver
Review the draft before it leaves.
A person marks the purchase order or proposal to send. Catalogue and price context stay with the draft.
A prepared draft. A person decides.
Showing Purchasing, 1 of 3.
Checked results. Connected to your systems.
The result goes where your team works.
One result. Connected where you need it.
Connect one system or several, around the way your team works.
Your team stays in controlRequired reviews and approvals still apply.
Your questions, answered.
What happens to a forwarded email ADAM cannot attribute?
It is held as an open intake exception rather than attached to a best guess. A person assigns it from a queue, so an unattributed message stays a visible task instead of becoming a mail that quietly went nowhere.
How does ADAM know whether a quoted price is reasonable?
It compares the line against what your organisation has paid for the same part before, and carries that benchmark onto the draft. The benchmark is advisory: it informs the person approving the draft rather than blocking the quote or rewriting the price.
Part numbers in a quote rarely match our catalogue exactly. Does that break the match?
No. Quotes often write a part number with punctuation or a trailing character the catalogue does not store. ADAM queries the catalogue with the number as written, then again with a normalised form, and calls a part absent only when both queries miss. That order stops a naming difference from being mistaken for a missing part.
Can ADAM write a purchase order into our system without a person approving it?
No. ADAM reads, resolves and drafts, but a draft is pushed only after a person marks it to send. The final write is deliberately a human action, because a posted purchase order in a system of record cannot simply be unposted.
Does ADAM produce a purchase order or a sales proposal?
Either, depending on the direction of the transaction. Both are prepared in your own system of record with the resolved lines and pricing already filled in. A sales proposal additionally cannot be sent while any line on it is still unpriced.
What stops the same draft reaching our system twice?
A draft carries a reference once it has been pushed, and a draft that already has one is no longer eligible to push. A duplicate click, a retried job or a second scheduled run therefore cannot create a second purchase order from the same draft.
Start with a document you already have.
Try the extracted result, then talk to us about the checks and connections your team needs.
Bring ADAM into your document flow.
Start with the channels you already use. We map the documents, define the modules and connect the outputs to your existing team.