Why supplier data requests turn into endless follow-up

Supplier follow-up becomes repetitive when the request is treated as a message instead of a process. The supplier receives an email or spreadsheet, but neither side has one reliable view of the required fields, accepted evidence, due date, open questions, corrections, and final review.

The problem is not always a supplier who refuses to respond. The request may be unclear, sent to the wrong contact, split across files, missing product identifiers, or changed after work began. Internally, different teams may ask for overlapping information without sharing status or ownership.

Why supplier data requests stall

• The request says “send packaging data” without naming components, fields, units, or evidence.
• The supplier cannot tell which products or part numbers are in scope.
• Questions and corrections are scattered across email threads.
• The requesting team cannot distinguish not started, in progress, submitted, returned, and accepted.
• A reminder goes to every supplier even when only one field remains open.
• Submitted information reaches the business but has no assigned reviewer.
• A supplier changes a material or specification after the original request is complete.

A better supplier data request process

1. Define the scope. Identify the supplier, products, components, source identifiers, and business purpose.
2. Define each requirement. Name the field, expected unit or format, acceptable evidence, and whether it is required or conditional.
3. Assign responsibility. Identify the supplier contact, internal request owner, specialist reviewer, and escalation owner.
4. Track the request by state. Separate requested, in progress, submitted, returned for correction, accepted, and unavailable.
5. Send targeted follow-up. Remind the responsible party about the specific open requirement rather than resending the entire request.
6. Review before promotion. Confirm completeness, meaning, evidence, and downstream readiness before using the response in another system.
7. Retain the operating record. Keep the source, reviewer, decision, effective date, and unresolved assumptions connected to the accepted information.

Automation should follow the state of the work

A scheduled reminder is useful only when the system knows what remains incomplete and who is responsible. Follow-up can then reflect the actual state: the initial request has not been opened, three fields are missing, evidence needs correction, or an internal review is waiting.

This allows leadership to see the operating condition without asking the team to assemble another status report. The workflow can continue sending appropriate reminders and exposing blockers while the team focuses on review and decisions.

Give external partners a controlled way to contribute

Suppliers should not need direct access to a company’s authoritative PLM or ERP records simply to provide information. A controlled contribution path can accept structured entries and supporting files while keeping internal review and promotion separate.

Where integration is appropriate, information can move between the partner’s environment and the receiving process. Where it is not, the supplier can respond through a bounded request without learning every internal system or receiving broad access.

What to measure

• Requests waiting for the supplier versus waiting for internal review.
• Fields returned for clarification or correction.
• Elapsed time between submission and acceptance.
• Repeated requests for information already provided elsewhere.
• Requests completed with explicit unknown or unavailable values.
• Changes that require previously accepted data to be reviewed again.

Related guidance

• Supplier packaging data request template
• Supplier and vendor operations use case
• Vendor data support
• Packaging data management guide
• EPR guide for packaging producers