Answer the RFQ first.
An RFQ arrives — email, EDI, a buyer's system. Corin prices it against live SAP or Infor state and stages the reply; your salesperson sends it.
RFQ automation software for SAP S/4HANA and Infor M3
One loop reads the request, checks credit, stock, and contract price in the live ERP, and stages the reply. Every step files into the ledger — a record of every decision: what changed, who approved it, when.
One request in. One priced draft out.
A pass through the pipeline, replayed: the inbound RFQ, the extracted lines, the live-ERP checks, the staged draft.
The machine that answers the machines.
Buyer-side systems already send RFQs automatically and rank whoever answers first. Corin answers in kind — extracted, priced from the ERP, staged in minutes — with a person reviewing every send.
Three ways a quote starts.
New RFQs arrive; aging quotes already sit inside SAP or Infor. Corin picks both up — and answers when you ask.
An RFQ lands
Email with a PDF, an EDI 850, a buyer's system — Corin reads the request and the loop starts.
A quote ages in the ERP
A quote aging past its follow-up window is swept up on schedule — Corin subscribes to ION Data Fabric events and SAP Event Mesh. A stalling quote is work exactly like a new RFQ.
You ask
"@corin which quotes expire this week?" — a grounded answer from live ERP state, with the follow-up drafts staged behind your gate.
Five stages. No hand-offs.
01The work lands
RFQs and POs arrive in the shared mailbox, over EDI, or from a buyer's system. Corin picks them up where they land — threads, PDFs, and spreadsheets included.
02Classification
Each message is typed: RFQ, PO, status chase, or noise. Every classification carries its confidence score.
03Extraction
Line items, part numbers, quantities, and need-by dates become structured data — with field-level provenance recorded for every value.
04ERP price check
Lines match against the item master. Prices come from the live ERP — price lists, contract terms, stock — not last night's export.
05Draft, never send
The quote reply is drafted in Outlook and waits. A person reads it, edits if needed, and sends. Corin never sends on its own.
Running at a top-5 aviation MRO distributor.
This loop runs today on a live sales inbox where a wrong part number or a missing cert date loses the order. Its measured accuracy — against the manual turnaround it replaces.
RFQ is where it starts. Not where it ends.
The loop on this page is the first stage of the full Quotes & Orders loop. Every stage runs under the same gate.
- RFQ
- The loop on this page: the request read from the inbox, lines extracted, prices checked against live ERP state, the reply drafted.
- Quote
- The priced answer becomes a governed quote — the dry run weighs the options, the margin floor holds, terms and validity attach, a person releases it.
- Order
- The accepted quote — or the emailed PO — becomes a validated, priced, posted sales order in SAP or Infor.
- Fulfillment
- The buyer asks where the order is; Corin drafts the answer from live ERP state and waits for your review before anything goes out.
- Change
- Cancels, expedites, date and quantity changes — including AOG, where minutes matter — validated against the order and routed to the right gate.
Request in. Draft out.
The inbox stays the front door. What changes is who does the reading.
Please quote the attached — 14 line items, quantities and need-by dates in the PDF.
Full trace documentation required with delivery.
The inbox is still the order channel.
8:42 — the RFQ. 8:49 — the approval.
8:42
a buyer at Alberth Aviation Parts emails RFQ-2308 — a PDF, 14 line items, two short lines of text.
8:43
Corin has the lines extracted and matched to the item master; credit, stock, and contract price are read from the live ERP.
8:44
three quoting options get a dry run — accept as-is, split across two DCs, counter on terms.
8:46
the decision card waits for Maria: partial shipment from two DCs at contract price, margin 26.2%, fill 96%.
8:49
Maria approves. The quote draft sits in Outlook at ERP prices — and the decision, her approval, and the draft are in the ledger.
An illustrative morning, recreated from the live loop — representative, not a customer record.
Built for the desk and the ERP team.
- Quotes drafted in Outlook — review, edit, send. Nothing is re-keyed, ever.
- Approvals arrive in Outlook or Teams, not in another queue to check.
- The buyer's decision window stops closing while someone looks up a price.
- Reads and writes run through released interfaces — Microsoft Graph, the ION API, released SAP APIs.
- Scoped permissions per mailbox and per ERP role; every decision and approval lands in the ledger.
- Your ERP stays the system of record — clean core preserved, no modifications.
Corin never moves money, signs, or sends without your confirmation — until you tell it to.