Glossary
What is purchase order collaboration? A practical guide
Purchase order collaboration: Purchase order collaboration is the way a buyer and a supplier keep each open purchase order line accurate: confirmation, date changes, partial shipments and exceptions, shared and acted on quickly.
By Roufaida Bouchamha, founder
The definition
Purchase order collaboration (PO collaboration) covers everything that happens between sending a purchase order and receiving the goods: the supplier confirms the order, commits to a date, warns when the date moves, and the buyer updates the ERP and reacts. Some companies do it by email and phone; others use a supplier portal or EDI messages.
What good PO collaboration looks like
- Every line is confirmed with a quantity and a promised date within a few days of sending the order.
- Date changes are reported as soon as the supplier knows, not on the day the goods were due.
- The ERP is updated, so the promised date in the system is the supplier's latest word.
- Exceptions are prioritized: buyers spend their time on the lines that matter, not on every late line.
The step most teams skip: deciding which lines matter
Better collaboration produces more information: more confirmations, more date changes, more late lines visible earlier. Without a way to rank them, buyers still chase by supplier or by days late. The useful question for each line is whether the part will run out before the order arrives. Rank late and undated lines by days of cover and you get a chase list that puts the lines that can stop production first.
A simple routine
- Daily: review new confirmations and date changes; update promised dates in the ERP.
- Daily: rank late and unconfirmed lines by cover and follow up the top of the list (see past-due purchase order).
- Weekly: list the lines that were never confirmed and the suppliers that moved dates most often.
- Monthly: review supplier on-time delivery and lead-time drift with the suppliers concerned.
Illustrative example, not a customer result
A buyer has 120 open lines with one supplier. 15 are past due and 8 were never confirmed. Ranked by cover, only 3 of those 23 lines are for parts that run out before the next delivery. Those 3 get a call today with the numbers; the rest go into the weekly confirmation request.
Portals, EDI or email?
The channel matters less than the discipline. A portal or EDI makes confirmations faster and keeps dates in sync; email works if promised dates are entered in the ERP the same day. In every case, the ERP date is what planning uses, so it must reflect the supplier's latest commitment.
How WERISCO fits
WERISCO is not a supplier portal and sends nothing to suppliers. It reads your stock, usage and open purchase orders, from your ERP or your exports, and shows which late or undated supplier orders will leave a part short before they arrive, ranked by severity, with each part's days of cover shown as evidence. Your buyers use that list to decide which lines to raise with the supplier.
Questions people ask
- What is the difference between PO collaboration and supplier collaboration?
- Supplier collaboration is broader: forecasts, quality, capacity and new products. PO collaboration is the day-to-day work on open order lines.
- Do I need a supplier portal for PO collaboration?
- No. A portal or EDI helps at scale, but the core is a confirmed date on every line, updated in the ERP, and a ranked list of the lines that matter.
- What should I measure?
- The share of lines confirmed within a few days, the share of lines whose date moved, and on-time delivery against both the first and the latest promised date.
