Buyer says sent, supplier says unseen? Order collaboration starts on one effective PO

Four 'orders', a whole afternoon spent confronting them

The material shortage weekly meeting went into the third hour, still arguing over ‘which version of the delivery date counts.’ The purchasing officer said the email was sent last week; the supplier said they never confirmed it; the planner noted ‘next Wednesday’ in their notebook; the ERP system still shows the original date. Each of the four people clings to their own piece of the truth, and the meeting’s outcome is ‘follow up’—after following up, there are still four pieces.

The core of order collaboration is not about sending out the PO, but about both parties reaching an agreement on the same valid order. Missing confirmations, changes without versions, and feedback not being recorded—any one of these breaks will distort the delivery schedule board, shortage analysis, and reconciliation. The pain point is often said to be 'supplier non-cooperation,' but if you break it down, it is often because the main factory itself does not have a single source of truth.

Sending does not equal confirmation: mutual recognition requires a timestamp

POs are issued via email, PDF, or verbally, without a 'pending confirmation' status; it is unclear who within the supplier has the authority to confirm; if confirmation is overdue, no one escalates it, and the order is not discovered to be stuck until a shortage occurs—before confirmation, the main factory has already driven production scheduling based on 'order placed,' and the plan is built on a non-consensus basis.

Minimum rule:

• After publishing, enter 'Pending Confirmation'; the portal can confirm or reject with one click (reasons can be attached).
• Confirm the timestamp is written into the order line, becoming the default reference starting point for delivery commitments and subsequent delivery performance assessments.
• Automatically upgrade if not confirmed after the deadline, and restrict downstream material preparation from calculating the full information;
• Only confirmed orders enter the shipping schedule and reconciliation scope.

Judgment criteria: Take any strategic material PO at random and see if you can view the release date, confirmer, confirmation time, and confirmed version delivery date within thirty seconds. When the purchasing agent marks the supplier's confirmation to boost the completion rate, it is the most dangerous pseudo-collaboration—the completion rate looks good, but it cannot be evidenced in case of disputes.

Changes have no version, screenshots can never be fully taken

Directly modifying the original order fields overwrites the history; verbal rush requests, inserting orders, or changing quantities are not supplemented; price and delivery dates are mixed in the same chat with unclear approval authority—the supplier still produces according to the old version, while the main factory receives goods according to the new version, and both sides think they are right.

Oral urgent requests also count as changes: instructions affecting fulfillment must be supplemented with orders within 24 hours, otherwise both performance and claims will lack documentation. Changes without a reason code cannot be explained at the end of the period as to 'who exactly is changing the plan'.

Reply saying it's paused in the chat, the planner's notebook is the second set of ERP

The supplier replies on WeChat with 'next Wednesday or Thursday,' the planner notes it in a small notebook, and the system delivery date remains unchanged; the feedback is then confused with the 'promised delivery date accepted by procurement'—whatever the supplier says goes, or even if procurement changes it, they don't inform the other party; partial shipments have no planned lines, and 'made up' at the end of the month is treated as full compliance throughout.

Separate into two fields:

• Report back: Supplier input, keep history;
• Promised delivery dateThe internal plan visible value is updated only after the purchase is accepted or rejected.

Feedback is input, commitment is decision-making. Feedback deviations affect performance; short deliveries must be closed with a reason code, and it must be clear whether a supplementary line will be generated. If order collaboration stops at 'delivery date confirmed' but does not enter the shipping plan and actual receipt back-writing, the bottleneck just moves from procurement to the platform — see the delivery topic for that chain.

Both parties' interfaces must see the same set of statuses

Any parallel status of 'Procurement ERP shows confirmed, supplier Excel is still a draft' will turn into shirking responsibility at the material shortage weekly meeting. The value of the portal is first consistency of status, and only then a good-looking interface.

Light portal precedes 'the other party completing the ERP'

When the supplier's digital maturity is weak, it is sufficient to lightly integrate using a confirmation link and feedback form; do not require the other party to access the full ERP system in the first step. The key is that the status falls into your collaborative system, not in chat records. The main factory can enter non-critical fields on behalf of the supplier, but the confirmation action must be completed by the supplier.

When advancing, do not fill all three items at the same time: first, only confirm strategic suppliers and high-frequency materials; after the confirmation rate rises, then add change versions and reason codes; finally, expand delivery feedback, accept/reject, and deviations into performance. The effectiveness signals are respectively: unconfirmed orders are visible; "WeChat order changes" can be counted and decrease; planned delivery dates match those on the portal.

Order and delivery coordination in the supply plan usually operates according to a release—confirmation—effectiveness state machine, with changes versioned and confirmed a second time, separating reply and commitment. After JEDP-SRM coordinates with the portal, the value lies in 'the same effective version at the same moment,' not in the order list interface. Integration failures must be visible to the business, and silent drift between the portal and ERP two sets of statuses is prohibited.

The scene that hasn't been set up yet

• Multiple codes for one item not managed: Even if confirmed, it cannot guarantee that execution points to the correct material;
• The special approval path is not made explicit: with just one word from the leadership to skip confirmation, the system becomes virtually ineffective;
• The supplier has not implemented strategic segmentation: long-tail and strategic items follow the same complex processes, resulting in excessively high promotion costs;
• Pure spot goods, pay on the spot and pick up: only minimal confirmation is required;
• The internal plan itself swings on a weekly basis: first, converge on the main factory's planning discipline.

Useful indicators: order confirmation rate and confirmation timeliness, secondary confirmation rate for changes, rate of oral change orders, response rate and deviation distribution of feedback, random checks for uniqueness of effective versions, completeness rate of short delivery closure reason codes. False confirmations, directly modifying the original order to erase history, and recording feedback only in a small notebook—all are anti-patterns.

Prices come from sourcing and benchmarking; order lines should reference the effective price version, rather than verbally negotiating a new price at the time of placing the order. Changes in delivery dates and prices being mixed in the same WeChat message make it unclear who is responsible during end-of-period reconciliation and delivery performance assessment. Overseas suppliers should prioritize ensuring that confirmation, rejection, and acceptance feedback buttons are usable; when translations are missing, these actions are more important to translate first than the promotional materials. When there are multiple organizations in the group, order permissions are isolated by organization to prevent a purchaser from Company A from mistakenly modifying the effective version of Company B.

After the confirmation rate improves, the first item in the weekly meeting should become the 'List of Unconfirmed and Changing Items' instead of reviewing material shortages. The list should be drillable down to the order line so that disputes shift from impressions to evidence. When the confirmation rate of strategic materials is below the agreed threshold for two consecutive weeks, first suspend the expansion change and feedback functions, make the confirmation actions solid, and then build on that.

What to do next

This week, first measure the confirmation rate of strategic material orders; if the confirmation rate does not improve, discussing the delivery ranking is meaningless. Then pick ten more orders that are 'said to have revised delivery dates' and check whether the system has versions and secondary confirmation—if not, the stories in the material shortage meetings are not credible. For categories that meet the confirmation rate standard, then check whether the reply/promise fields are separated.

• SRM Supply Solution: Order and Delivery Collaboration
• Sourcing: Request for Quotation, Bidding, and Tendering
• How to have the delivery schedule received by the warehouse
• Outsourced processing reconciliation breakpoint
• Reconciliation, Invoicing, Payment, and Order Activation Version