How to Stop Chasing Suppliers After the PO: Why Updates Fade
It is Monday, the hoodie PO went out three weeks ago, and the only way to find out whether the fleece has been booked is to forward the same email for the third time. Nobody has said anything is wrong, which is exactly the problem: silence in the weeks after booking is where small slippages grow into late shipments. To stop chasing suppliers after the PO, you need a reporting system that works without you asking, and that system has to be agreed before the order is confirmed, not improvised once you are worried.
This guide is written for buyers, product developers and sourcing leads at established UK and European retailers and brands who already run production calendars. The commercial constraint is simple. Once a PO is placed you carry the cost of delay (markdown exposure, missed launch windows, air freight) while the supplier carries the day-to-day information. Closing that information gap is cheaper than managing the consequences of it.
The method has four parts: weekly milestone reports, named owners with escalation thresholds, documentary evidence for fabric and trim bookings, and early risk reports that arrive with recovery plans. A worked illustration later in the guide builds the dashboard, and the KPI section defines each measure so you can track whether the system is working.
Why Supplier Communication Deteriorates After Booking
Supplier communication usually does not fail because anyone is hiding things. It fails because the order moves from the people who negotiated it to the people who execute it, and nobody defines what execution reporting looks like. Before designing a fix, it helps to name the specific causes, because each one has a different remedy.
Why updates fade, and what fixes each cause
| Cause | What it looks like | Fix |
|---|---|---|
| No agreed report format | Updates arrive as free-text emails; each one covers different things | Agree a fixed milestone list and one report template before the PO |
| No named owner | Questions are answered by whoever is free, or not at all | Name one owner per side for each milestone group |
| Status is a feeling | "On track" with no date, quantity or document behind it | Require evidence with every green status on a booking milestone |
| Bad news is delayed | A problem is mentioned only when it can no longer be absorbed | Define amber and red triggers, and agree that early red is not penalised |
| Attention moves on | The factory team is already working on the next season | Fix a reporting day and time so the report is a routine, not a favour |
| Buyer chases in different channels | Chat, email and calls each hold part of the picture | One dashboard is the record; other channels only point to it |
General patterns in order management. Which cause dominates depends on the supplier, the programme and how the PO was handed over.
Notice that most fixes are agreements, not tools. A spreadsheet will not help if nobody has agreed who updates it. That is why the first step happens before the PO.
Step 1: Agree Weekly Milestone Reports Before the PO
If you want to stop chasing suppliers after the PO, the best moment to agree reporting is during quotation and pre-production discussions, when the supplier wants the order and the buyer has most leverage. After the PO is confirmed, a request for a weekly report can feel like extra work added to a finished deal. Written into the order terms or the pre-production meeting notes, it is simply part of the job.
What the milestone list should contain
Start from the milestones in your production calendar. If you have not built one, our guides to clothing production lead times and the garment production process describe the stages. A hoodie programme typically needs fabric booking, trim booking, lab dip or shade approval, fabric in-house, pre-production sample approval, cutting, sewing, wash or finishing, final inspection and shipping booking. Re-time the list for your own product.
Pre-PO reporting agreement: items to settle in writing
- Milestone list with a planned date for each, counted from PO confirmation
- Reporting day and cut-off time each week, in the supplier time zone and yours
- Report format: one shared sheet or page, not a new email each week
- Status definitions for green, amber and red, with the trigger for each
- Named owner on each side for each group of milestones, plus a deputy
- Evidence required with each milestone, such as booking confirmation or inspection report
- Escalation ladder and expected response times
- Rule that an early amber or red report must include a recovery plan, and carries no penalty for being early
A checklist for agreement before the PO, not a contract clause. Ask your own legal and commercial teams how to record it in your order terms.
Keep the list short enough to maintain. A report with thirty rows is abandoned by week three; a report with ten to fourteen milestones is usually read every week. If you want a fuller view of how the dates connect, our hoodie critical path guide shows the dependencies behind them.
Step 2: Use Named Owners and Escalation Thresholds
A milestone without an owner is a hope, and it is the commonest reason buyers cannot stop chasing suppliers after the PO. Each row of the dashboard should carry one name on the supplier side and one on yours, and the supplier name should be someone with the authority to change the schedule, not only to report it. Where a role changes hands, the replacement and the date should be stated in the next report.
Escalation thresholds turn chasing into a rule. Instead of deciding each week whether a delay is worth raising, you agree in advance what triggers a step up. The thresholds below are examples to agree with your supplier for your programme; they are not industry standards, and the right trigger for a four-week fleece booking is different from the right trigger for a one-day packing step.
Example escalation ladder (illustrative; agree your own)
| Level | Example trigger | Who is involved | Expected response |
|---|---|---|---|
| Level 1: working level | Milestone is amber: forecast to slip by one to two working days, or evidence is missing | Supplier merchandiser and buyer or technologist | Revised date and cause in the next weekly report |
| Level 2: management | Milestone is red: forecast to slip by more than two working days on a critical-path step, or no recovery plan within one working day | Supplier production or merchandising manager and the buyer | Written recovery plan with dates and trade-offs within one working day |
| Level 3: senior | Two red milestones at once, or a red milestone that threatens the agreed ship date | Supplier director and your sourcing lead | Decision on recovery option (split ship, extra shifts, freight change) agreed in a call |
Triggers and response times are examples for discussion. They vary by product, calendar and relationship, and should be recorded with the supplier before the PO.
Two details make the ladder work. First, the clock starts when the forecast changes, not when the date is missed. Second, the supplier is told in advance that raising an amber early is the behaviour you want, so the ladder is not read as a punishment scheme.
Step 3: Request Evidence for Fabric and Trim Bookings
Fabric and trim bookings are the most common source of silent delay, because everything downstream (cutting, sewing, wash, shipment) depends on them, and the first sign of trouble is often a missing delivery rather than a message. Asking for evidence is not an accusation. It is the same discipline your own team applies to any commitment that other work depends on.
Evidence to request for each booking milestone
| Milestone | Evidence to request | What it supports | What it does not prove |
|---|---|---|---|
| Fabric booking | Mill or supplier order confirmation showing construction, composition, weight, colour, quantity and delivery date | The material has been committed, to the specification you approved | That it will arrive on time; it needs a later in-house check |
| Lab dip or shade approval | Approved lab dip record with reference, date and signed approval | The colour target is fixed and agreed | That bulk dyeing will match; that needs lot-by-lot checks |
| Trim booking (zips, drawcords, labels, rib, packaging) | Order confirmations or delivery notes for each trim, with quantity and delivery date | Every trim item on the bill of materials has a source and a date | That trims meet specification; request approved trim cards or samples |
| Fabric in-house | Receiving note with roll or lot numbers, quantity received and photographs; inspection report if you require one | The material physically exists and matches the booked lot | That the fabric passes your required tests; check those separately |
| Pre-production sample approval | Signed PP sample comments and the approved sample reference | Bulk can be released against a fixed reference | That bulk will equal the sample; inspection during production covers that |
Which documents exist depends on how the supplier buys material. Ask what is available, and agree to receive redacted copies if prices are commercially sensitive.
If a supplier cannot produce any document for a fabric booking, treat the milestone as unconfirmed, whatever the status column says. For inspection standards on arriving goods and finished garments, see our guide to AQL inspection, and remember that AQL is a sampling standard, not a guarantee of zero defects.
Step 4: Report Risks Early With Recovery Plans
The goal of the whole system, and the reason you can stop chasing suppliers after the PO, is to find out about problems while there is still room to act. A late fabric delivery reported in week four may be absorbed by overtime in cutting; the same delivery reported in week eight may need air freight. The rule that makes the difference is simple: every amber or red report arrives with a recovery plan, even a provisional one.
A recovery plan should be specific enough to decide on. It names the cause, the revised date for the affected milestone, the downstream dates that move, the options available, and the cost or quality trade-off of each. Options usually include splitting shipments, adding sewing capacity, changing the transport mode, or re-sequencing colours. None of them is free, and the supplier should say so rather than offering a single option as if it were the only one.
The weekly reporting rhythm (illustrative; set your own days and times)
- MondaySupplier owner updates milestone dates, statuses and evidence links for the previous week.
- Tuesday by agreed cut-offReport is final. Any amber or red items carry a cause and a recovery plan.
- Tuesday or WednesdayShort review call only if there is an amber or red item; otherwise written acknowledgement from the buyer.
- Within one working day of a redLevel 2 escalation: recovery plan with trade-offs, decision requested from the buyer.
- FridayBuyer owner confirms any decisions made and updates the internal launch or intake plan.
The days are an example of a rhythm. What matters is that the day, the cut-off and the owners are fixed and written down before the PO.
Agree with the supplier that an early red report is never a mark against them, while a late one is judged on how long the buyer was left uninformed. That single rule changes what people are willing to put in the report.
Worked Illustration: From Email Chain to One-Page Production Dashboard
The illustration below is hypothetical. It follows an assumed order of 3,000 hoodies in six lines of 500 units (style and colour), a production calendar of about twelve weeks from PO to ex-factory, and a snapshot taken at the end of week six. The supplier, the dates and the statuses are invented to show the method; they are not benchmarks and do not describe any real order.
In the reactive version, status lived in a long email chain. Over six weeks the buyer sent 18 chase messages, covering nine milestones that fell due in that period, and answers arrived in fragments: a photograph of fabric, a one-line "booked", a late reply about trims. To find out whether the wash slot was confirmed, the buyer had to read back through thirty messages. The dashboard below holds the same information on one page.
Mock one-page production dashboard at the end of week 6 (illustrative)
| Milestone | Planned | Owner (supplier / buyer) | Status | Evidence on file |
|---|---|---|---|---|
| PO and spec sign-off | Week 0 | Merchandiser / Buyer | GREEN – complete | Signed PO and approved spec sheet |
| Fleece fabric booking | Week 1 | Merchandiser / Technologist | GREEN – complete | Mill confirmation: construction, weight, colours, quantity, delivery week |
| Rib and trims booking | Week 2 | Sourcing lead / Technologist | AMBER – drawcord delivery one week later than planned | Order confirmations for rib and labels; drawcord note pending, recovery plan received |
| Lab dip approval, all colours | Week 2 | Merchandiser / Buyer | GREEN – complete | Signed lab dip record, five of six colours; sixth approved in week 3 |
| Fabric in-house | Week 5 | Production manager / Buyer | GREEN – received | Receiving note, roll numbers, photographs, inspection report |
| PP sample approval | Week 5 | Sample room / Technologist | AMBER – one comment outstanding on cuff length | PP comments sheet; resubmission due week 7 |
| Cutting start | Week 6 | Production manager / Buyer | RED – blocked by PP approval and late drawcords | Revised start forecast with recovery plan: split lines 1 to 3 first |
| Sewing complete | Week 9 | Production manager / Buyer | AMBER – forecast tight | Capacity plan received; checked at next report |
| Wash or finishing slot | Week 9 | Merchandiser / Buyer | GREEN – slot confirmed | Booking confirmation from wash unit |
| Final inspection | Week 10 | QA lead / Buyer | NOT STARTED | Inspection date to be confirmed once cutting restarts |
| Shipping booking | Week 11 | Logistics / Buyer | NOT STARTED | Booking request after final inspection date is fixed |
Illustrative only. Status is written in words as well as colour so the page reads correctly in black and white. Dates, owners and findings are hypothetical.
Read the table from the bottom of the colour column up. One red item (cutting) is blocked by two ambers (drawcords and PP comments), and both ambers arrived with plans. The buyer can decide in a single glance whether to approve the split start. In the email-chain version, the same decision would have waited for someone to notice that three messages, spread over a fortnight, were describing one problem.
Email Chain, Shared Tracker or Weekly Report: Which Works Best?
Buyers often ask whether a shared spreadsheet is enough or whether a dedicated platform is needed. The answer depends on the number of suppliers and orders you manage, but the channels differ in a predictable way. The table rates three common approaches on the qualities that decide whether you still have to chase.
Indicative comparison of post-PO communication approaches
1 dot = low, 5 dots = high
| Email chain | Shared tracker | Weekly report with evidence | |
|---|---|---|---|
| Visibility of overall status | ●●●●● | ●●●●● | ●●●●● |
| Clear ownership per milestone | ●●●●● | ●●●●● | ●●●●● |
| Evidence attached to status | ●●●●● | ●●●●● | ●●●●● |
| Early warning of risk | ●●●●● | ●●●●● | ●●●●● |
| Effort for the supplier | ●●●●● | ●●●●● | ●●●●● |
| Effort to set up | ●●●●● | ●●●●● | ●●●●● |
Indicative ratings based on how these approaches typically behave, not measured results. A shared tracker becomes a weekly report with evidence once the rhythm and owners are agreed.
A shared tracker is a good start, and many buyers never need more. The weekly report with evidence adds the discipline: a fixed cut-off, a named owner and a document behind every green. Supplier effort is higher than with email because the work is more complete, which is a reason to agree it before the PO and to keep the milestone list short.
The KPIs: Update Timeliness, Chase Rate and OTIF
A system you cannot measure drifts back to old habits. Three measures are enough to tell you whether the reporting rhythm is working. Define them in the pre-PO meeting so both sides calculate them the same way, because definitions vary between retailers and suppliers and an unspoken difference is a common source of argument.
KPI definitions for post-PO communication
| KPI | Formula | How to measure | Where definitions vary |
|---|---|---|---|
| Update timeliness | Reports received by the agreed cut-off divided by reports due, expressed as a percentage | Count weekly reports against the calendar; note the number of reports containing evidence for every green booking milestone | Some buyers count a report only if complete; others count any report. State which you use. |
| Chase rate | Buyer-initiated status requests divided by milestones due in the period (or per week) | Log each time the buyer asks for information that should have been in the report | Choose milestones or weeks as the denominator and keep it constant; do not count agreed review calls. |
| OTIF (on time, in full) | Order lines (or units) delivered by the agreed date in the agreed quantity, divided by order lines (or units) due | Compare each line to the confirmed ex-factory or delivery date and PO quantity | Lines versus units, tolerance on quantity, and whether the date is ex-factory or delivered. State all three. |
Definitions are standard formulas, but each retailer applies its own tolerances. Agree the version your programme uses before the PO.
Update timeliness tells you whether the supplier is meeting the reporting agreement. Chase rate tells you whether you still have to ask. OTIF is the outcome that the other two are meant to protect, and it shows whether better communication turned into better delivery. Watch them together: a supplier with perfect update timeliness and weak OTIF is reporting accurately that something is going wrong.
Worked KPI Example: Reading the Numbers
The figures below continue the hypothetical order from the dashboard illustration. All inputs are assumed. The aim is to show how the three KPIs are calculated and how a second order, run with the reporting system in place, might read differently; it is not a claim that any system produces a particular result.
Chase rate: buyer-initiated chases per milestone due (illustrative)
Lower is better
Illustrative arithmetic: 18 chases over 9 milestones is 2.00; 5 chases over 9 milestones is 0.56. Assumed inputs, not a benchmark or an expected result.
Chase rate is useful as a trend within one supplier relationship, not as a comparison between suppliers. A low chase rate can also mean the buyer has stopped asking, so read it alongside update timeliness. In the illustration, eight of ten weekly reports arrived by the cut-off, which is an update timeliness of 80 per cent, a figure that tells you the rhythm is largely holding with two exceptions worth discussing.
Weekly reports received by the cut-off (illustrative: 10 due)
Update timeliness
Illustrative: 8 of 10 reports by cut-off equals 80 per cent. Assumed inputs.
Now OTIF. Suppose line 3 shipped two days after the confirmed date, in full, and line 5 shipped on time but 40 units short at 460 of 500. The table shows how the same delivery reads differently depending on whether you measure order lines or units.
OTIF for six order lines of 500 units (illustrative)
| Line | Agreed qty | Delivered qty | On time? | In full? | Counts as OTIF? |
|---|---|---|---|---|---|
| 1 | 500 | 500 | Yes | Yes | Yes |
| 2 | 500 | 500 | Yes | Yes | Yes |
| 3 | 500 | 500 | No (two days late) | Yes | No |
| 4 | 500 | 500 | Yes | Yes | Yes |
| 5 | 500 | 460 | Yes | No (40 short) | No |
| 6 | 500 | 500 | Yes | Yes | Yes |
| Total | 3,000 | 2,960 | 5 of 6 lines | 5 of 6 lines | 4 of 6 lines |
Illustrative. OTIF by lines: 4 of 6 is 66.7 per cent. OTIF by units, counting only units from lines that were both on time and in full: 2,000 of 3,000 is 66.7 per cent. Units delivered against units ordered: 2,960 of 3,000 is 98.7 per cent, which is a fill rate, not OTIF.
Always say which version you are quoting. The 98.7 per cent fill rate looks healthy but hides a late line and a short line, and either one could mean a missed store launch or a lost size run. OTIF is deliberately strict, which is why it is worth tracking. For how OTIF fits into a broader view of supplier performance, see our guide to the supplier scorecard.
The Decision: How to Stop Chasing Suppliers After the PO, and What Would Change It
If your last two or three orders needed repeated chasing, the decision to stop chasing suppliers after the PO is to change the process before the next PO rather than to change the supplier. Agree the milestone list, owners, thresholds and evidence rules in the pre-production meeting; run one order with the weekly report; then review update timeliness, chase rate and OTIF at the end. If you have already placed the PO, you can still introduce the dashboard, but frame it as a shared tool and agree the cut-off before the next week begins.
Some evidence should change the decision. If a supplier consistently misses the reporting cut-off after the rhythm is agreed, cannot supply any document for booking milestones, or reports green until a milestone is missed, the issue is capability or commitment, not communication, and you should reconsider the allocation. If, on the other hand, reports are on time, evidence is attached and ambers appear early with plans, a missed delivery is more likely to be a capacity or material problem, and you should look at the critical path and lead-time assumptions instead; our guide to preventing garment production delays covers that side.
Mistakes that bring the chasing back
- Building a report with too many milestones, so nobody maintains it.
- Agreeing the rhythm verbally, so it is forgotten within three weeks.
- Accepting a green status without evidence on a booking milestone.
- Treating an early amber as a complaint, which teaches the supplier to wait.
- Having the buyer answer in four channels, so the dashboard stops being the record.
The KPI to monitor first is update timeliness, because everything else depends on the report arriving. When it holds above the level you agreed for several consecutive orders, move attention to OTIF. Which milestone on your current open orders would you most struggle to evidence today, and who is the named person who should be telling you about it?
How Ruhrose Approaches Post-PO Communication
Ruhrose develops hoodies, jersey, denim and woven casualwear for UK buyers, with production in Bangladesh and UK buyer support. Buyers who want to stop chasing suppliers after the PO need the reporting agreed early. We sample before bulk, and we are happy to discuss a milestone list and a weekly update format during sample and pre-production conversations, before an order is placed. If you are considering a smaller first order, the test and scale approach is a risk-reduction model, not a risk-free one, and it works best when the reporting rules are set at the start.