Late customer returns in a supplier scorecard

Add a returns view to your existing scorecard

Keep the measures and weights in your existing supplier scorecard. Add a batch returns view alongside them, with a reporting cut-off, observation period and maturity status. Record returns received during the reporting period separately from the production batches responsible for them.

Preserve each published snapshot. When a late return changes an older batch's result, show the revised cumulative result and an amendment note explaining the change. This keeps the original purchasing decision visible while allowing later evidence to affect the next order.

Trace the returned unit before assigning responsibility

Use the factory-to-customer traceability guide for the underlying records. In the returns log, connect the customer order, product variant, unit or batch mark, production batch, factory and specification revision. Keep customer delivery, fault report and physical return dates as separate fields.

Record the reported fault, inspection findings and attribution status. Separate confirmed manufacturing defects from transport damage, fulfilment mistakes, change-of-mind returns and unresolved cases. Keep unmatched returns visible in an unallocated queue rather than guessing their batch. Link repeated contacts, refunds and replacement records to the same returned unit so they do not inflate the defect count.

Compare equal time in customer use

Choose a common observation period suited to the product's use and failure pattern, and document it before reviewing supplier results. Start the clock at customer delivery where that date is available. Warehouse arrival alone does not show how long goods have been in customer use. If you use a proxy, label it and avoid mixing it with confirmed customer delivery dates.

For each batch, include in the comparable rate only units that have completed the agreed follow-up period by the reporting cut-off. Divide confirmed supplier-attributable defective units reported within that period by the eligible delivered units. Apply the same rule to every batch, including batches sold gradually; exclude unsold stock from this denominator.

Keep younger units and faults reported after the common period in a separate cumulative view. Show eligible volume, excluded volume and pending investigations beside the rate. If no units have completed follow-up, display 'not yet comparable'. A quiet new batch is provisional evidence, not proof that quality has improved.

Make the comparison visible at each review

Use the following fields alongside the existing score. Keep product variants and specification revisions separate where their failure patterns differ. Compare suppliers using the same definitions, observation period and reporting cut-off.

Allow for delays between a customer reporting a fault and the team recording it. Save both dates and agree a consistent reporting allowance before publishing comparisons. When evidence arrives later, restate the affected comparison with an amendment note. Do not silently change the observation period or denominator to improve a supplier's position.

Use late returns to test corrective action

Ask the factory to connect the returned-unit evidence to production records, material changes and the agreed corrective action. Distinguish faults from production before the change from faults in batches made after it. Use the corrective-action closure guide for closure evidence, and keep the effectiveness judgement provisional until affected customer deliveries have comparable follow-up.

Escalate suspected safety faults immediately rather than waiting for a mature score. UK businesses selling consumer products must not sell goods they know, or should have known, are unsafe. As a practical precaution, hold potentially affected stock while the safety concern is assessed; a favourable average score should never dismiss a serious fault.