Practical perspectives
Direct-Materials Sourcing: Test the RFQ-to-PO Handoff
A buyer pilot for part specifications, supplier quotes, order changes and invoice exceptions across the sourcing-to-ERP handoff.
Direct-materials sourcing rarely ends when a buyer selects a quote. A drawing may change, a supplier may confirm a different delivery date, and the invoice may refer to an earlier purchase-order version. A useful AI pilot has to keep those events connected without silently changing a commercial commitment.
This worksheet narrows the general one-workflow pilot to a manufactured component. It can be used alongside the Fragment vs Mandel AI comparison. The cases are editorial examples; they are not vendor test results.
1. Choose one part and define the system boundary
Pick a repeat component with an approved drawing or specification, known eligible suppliers and a real purchase-order process. Use appropriately redacted records if sharing production data is not approved. Record the source of the drawing revision, target quantity, required date, currency, supplier status and buyer authority before the demonstration.
Map the systems that own the request, supplier master, RFQ, quote, PO, receipt and invoice. Ask which application writes each change and which merely reads it. Mandel AI describes ↗ supplier coordination from RFQ through invoice with ERP updates; Fragment describes ↗ agents acting across existing source-to-pay systems. Those published descriptions make the handoff worth testing, not a reason to assume either implementation already fits yours.
2. Make the case set follow the same order
| Event | Expected control | Evidence to inspect |
|---|---|---|
| RFQ omits a drawing revision | Stop or clarify before supplier release. | Version, requester response and final RFQ attachment. |
| Quote omits tooling cost | Keep the bid comparison open. | Supplier follow-up, original quote and revised landed cost. |
| Lowest bid misses the production date | Show the trade-off to an authorised buyer. | Promise date, qualification and approval record. |
| Supplier confirms a later date after PO issue | Route the proposed change under policy. | PO version, supplier acknowledgement and ERP write-back. |
| Receipt quantity differs from invoice | Assign the exception to the right owner. | PO, receipt, invoice line and resolution trail. |
| Invoice uses the old PO price | Prevent an unexplained payment decision. | Applicable order version, tolerance and final disposition. |
Run the cases in sequence so a correction in one stage reaches the next. Ask the provider to show both the normal path and a case it cannot resolve confidently. A fluent answer to a single RFQ does not demonstrate a maintained order record.
3. Inspect supplier communication and buyer authority
Follow every supplier-facing message. Check the intended recipient, specification version, requested reply, and whether the message is a draft or was actually sent. Fragment publishes ↗ a change-order workflow that contacts suppliers and records confirmations; Mandel publishes ↗ RFQ follow-up and buyer-approved supplier choices. Their controls and thresholds should be demonstrated in the offered configuration.
- RFQ release: who confirms the eligible supplier list and approves the drawing sent?
- Quote clarification: can the system ask for a missing cost without changing the original offer?
- Supplier selection: who accepts a cost-versus-date trade-off and where is it recorded?
- Order amendment: what can be sent automatically, and what needs approval because value, volume or date changed?
A buyer should be able to pause an unsuitable action and see the evidence behind the recommendation. The NIST AI RMF Core ↗ calls for human oversight roles to be defined for the intended context. Apply your own approval policy rather than accepting a generic “human in the loop” label.
4. Follow changes into the ERP and invoice queue
After the supplier confirms the new date, compare the supplier message, current PO and ERP record. Simulate a failed write-back or duplicated confirmation. The product should show the failed state and a safe correction path; two conflicting orders should not be presented as a completed handoff.
Then introduce the price and quantity mismatches. Ask whether the system identifies the correct PO version and receipt, who owns the difference, whether a credit or PO correction is needed, and what the invoice approver sees. Fragment documents ↗ cross-checking PO, receipt and invoice records; Mandel describes invoice discrepancy work on its product page. The invoice-to-contract vs three-way-match guide helps keep those control questions separate.
5. Score control and completion, then decide the next scope
For each event, record whether the correct source version was used, the supplier or buyer was contacted appropriately, approvals worked, the ERP received the intended change and an exception was resolved with evidence. Count hands-on corrections and unresolved cases as well as elapsed time. Keep an unapproved commitment, wrong drawing or duplicate PO visible outside an average score.
Choose a narrow next step: deploy one controlled supplier-follow-up path, retest a failed handoff, or stop because a mandatory control is missing. State the product version, integrations, supplier channels and approval settings tested. Do not translate a vendor-published automation or savings figure into your own expected outcome without a measured baseline.