Proposed workflow · Procurement and purchasing
Confirm supplier orders and recover missing acknowledgments
Keep an order's transmission, receipt and supplier acceptance distinct, then give the buyer evidence for recovering an unconfirmed delivery.
The workflow is grounded in published practitioner accounts. The plan below sets out proposed tasks, outputs and human review points. Its checks are designed, not executed; no operating result or ready-made environment is claimed.
Verification concerns the actual work, its inputs, tasks and exceptions. AI adoption is not a prerequisite. Source support verifies attribution to the account; an enterprise owner must confirm the process for their own systems and rules.
What practitioners report
A buyer describes placing an order, requesting acknowledgment and repeatedly chasing it. The supplier later said it had not received the order. The poster attributes the failure to attachments being quarantined despite messages appearing sent, and reports a potential project-threatening delay.
Tasks described in the accounts
- Place the quoted parts on a purchase order and ask the supplier to acknowledge it.
- Chase missing confirmation and request delivery information or expedition.
- Contact the supplier after discovering the missing order, tell the senior buyer and prepare a project update.
Reported friction and exceptions
- Sent messages and repeated chasers do not establish supplier receipt.
- The poster reports attachment-size quarantine without an internal failure notification.
- The supplier's production team had not yet confirmed the revised delivery date in the visible follow-up.
- The poster says the OEM owns the design IP and the drawings specify this supplier, limiting alternate sourcing.
Original post and visible replies read. This verifies the published account and its attribution, not the company's mail logs, supplier records, asserted cause or final delivery. Author identity is unverified; collapsed replies and attachments were not inspected. AI use is not a prerequisite for documenting this real work.
Inputs for the proposed workflow
Agree the records, access and business rules with the people responsible for the work. Use approved test records before any operating use.
- Purchase order and supplier quote
- Line identifiers, quantities, requested dates and the quotation or lead-time record. The source account mentions an RFQ, PO and long-lead parts; the detailed field set is proposed.
- Transmission and supplier correspondence
- Sent messages, attachments, supplier acknowledgments and follow-up records. Keep apparent sending separate from supplier confirmation.
- Project requirements and authority
- For the proposed design, the buyer supplies required dates, responsible contacts and agreed follow-up/escalation rules. No universal time threshold is assumed.
Tasks and responsibilities
Proposed work plan
The order and responsibilities below are a proposed design. They are separate from the reported practitioner tasks above.
Step 1 · Buyer and project owner
Agree the order record and confirmation rules
Identify the in-scope PO lines, requested dates, supplier contacts, design/supplier restrictions and what evidence constitutes acceptance. Agree follow-up timing and project-impact escalation before using the process.
Output: Reviewed line register and owner-approved confirmation rules.
Step 2 · Buyer or assigned coordinator
Assemble transmission and acknowledgment evidence
Link each message and supplier response to the relevant PO version and lines. Record sent, receipt reported, accepted, rejected or unresolved separately; do not infer acceptance from a sent folder or delivery receipt.
Output: Line-level evidence register with unresolved states preserved.
Step 3 · Buyer
Investigate missing or conflicting confirmation
Check whether the supplier received the current documents, use an approved alternate contact or transmission method where needed, and obtain explicit quantity/date responses. Prepare follow-up rather than sending messages or replacing an order without permission.
Output: Supplier-confirmation request and documented open questions.
Step 4 · Buyer and project owner
Prepare a recovery decision
Compare confirmed supply with required dates. Present verified dates, unknowns and permitted options; the accountable owner decides expedition, permitted partial supply or plan revision. Consider alternate supply only after the design/purchasing owner confirms it is allowed.
Output: Owner-reviewed recovery note and unresolved obligations.
Step 5 · Independent reviewer, then buyer/project owner
Check independently and accept or repair
Reconcile the register to the original PO and supplier evidence. Return omissions or rejected recovery assumptions for repair, repeat the independent checks and obtain owner acceptance of the revised result.
Output: Accepted confirmation/recovery record, or an explicit held exception with owner and next action.
Independent checks → accountable owner review
Check the proposed output against the agreed reference records and rules. A failed check or owner rejection withholds acceptance. Return the affected work for repair, rerun independent checks, then return it to the owner for review. A corrected draft cannot bypass either review.
Exceptions and human review points
These are proposed cases to rehearse, including extensions of the reported problems. The enterprise owner sets escalation contacts, response times and decision authority.
Exception
No acknowledgment despite apparent email success or a quarantined attachment
Proposed response
Retain the unconfirmed state, ask the supplier to check receipt and attachment quarantine, and obtain evidence through an approved channel. Do not assume that every missing reply has the same cause.
Human review
Buyer
Exception
Acknowledgment omits a line or changes quantity/date
Proposed response
Keep affected lines unresolved and request clarification; do not treat a partial reply as acceptance of the whole order.
Human review
Buyer and project owner
Exception
Design IP or drawings require the original supplier
Proposed response
Do not propose an unauthorized substitute. Verify design and sourcing restrictions, then assess permitted expedition, partial delivery or project-plan changes.
Human review
Buyer, engineering/design owner and project owner
Exception
Revised supply threatens a project requirement
Proposed response
Prepare the impact and recovery options for the owner; no automatic expedite, substitute purchase or delivery promise.
Human review
Buyer/project owner with relevant purchasing authority
Checks and owner acceptance
Designed checks, not executed acceptance results.
- Each accepted line traces to the current PO version and explicit supplier evidence; a sent email alone cannot pass.
- Independently compare quantities and dates with source documents and retain all missing or conflicting lines.
- Test missing acknowledgments, partial replies, revised dates and repeat messages without creating duplicate obligations.
- Check design/IP and mandated-supplier restrictions before presenting recovery options; unavailable alternate supply must not appear as an approved remedy.
- A rejected check or owner decision returns to repair, independent rechecking and renewed owner review.
Owner acceptance
The buyer accepts the confirmation record and the project owner accepts the recovery decision. Unresolved commitments remain visible with an owner and next action. Timing and escalation thresholds must be agreed locally; none are invented here.
Review the workflow representation, human capability and any agent performance separately. Accepting practice evidence does not authorize production actions.
Sources and verification limits
Source review: . Source dates and the scope of the reviewed material are recorded separately below.
- PO never received by supplier - PLEASE HELP
17 December 2025, search-index date; older baseline
Opening account describing the PO, chasers and attachment quarantine; poster's replies that processing has begun but a delivery date remains pending, and that OEM-owned IP and drawings require this supplier.
- The detailed register, states, review process and test cases are a proposed design, not controls reported by the Reddit poster.
- This page does not execute a purchase, contact suppliers or alter project commitments. No AI adoption or demonstrated automation benefit is required to include the underlying workflow.
- The design and acceptance checks have not been executed against company records. Source dates are index-reported and can differ from cached relative ages.
Shape this around your enterprise
Bring the records, systems and people responsible for this work. Agree the current process, proposed changes, permissions and acceptance criteria before scoping a bespoke environment or preparation.