Buyer guides
Build a Procurement Dispute Evidence Pack Before the Documents Scatter
Organize a supplier quality dispute with a neutral issue statement, dated chronology, requirement-to-evidence index and submission checklist.
When a supplied product differs from what you expected, assemble a short issue statement, a dated chronology and an index connecting each disputed requirement to the relevant evidence. Preserve the original records separately. Check the actual order's submission procedure and deadlines before sending anything or closing a case step.
The immediate goal is to make the facts reviewable: what was agreed, what was supplied, how the difference was observed and what remains uncertain. A large collection of screenshots can still leave those questions unanswered. Clear organization helps the supplier, platform reviewer, inspector or professional adviser understand the issue without reconstructing your inbox.
This is a document-preparation method. It does not determine liability, establish legal admissibility or guarantee a refund.
Start with the difference you can demonstrate
Write a short statement for each issue. Identify the order and affected line, the characteristic under discussion, the requirement source and the observed result. Keep the explanation narrow enough to support with records.
For example, in an illustrative equipment order, the buyer might record: “The connector shown on the delivered unit differs from the connector identified in the approved drawing. We need confirmation of the supplied configuration and its compatibility with the receiving equipment.” This identifies a question without assuming why the difference occurred.
Avoid combining several concerns into “the whole shipment is unacceptable.” Packaging damage, dimensional variation and a missing document may require different evidence and responses. Give each a separate issue ID, even if they eventually form part of one submission.
Record the clarification or assessment you are seeking. Any demand, settlement proposal or statement about legal remedies needs its own review and authority; an evidence summary should not create those commitments by accident.
Reconstruct the agreement before evaluating the result
Collect the offer, purchase order, specifications, accepted drawings, agreed samples and recorded changes. Identify which version applied to the affected goods. Keep disputed or unclear document status visible instead of deciding it through a convenient filename.
A quotation attachment may describe an option that was never ordered. A later message may discuss a possible change without confirming it. Mark such records as context until the relevant parties or qualified adviser establish their significance.
NASA's configuration-management guidance explains the value of identifiable baselines, retained histories and recorded change status. That record discipline is useful here, although NASA's process is not a dispute rule for commercial purchases.
Create a chronology with one row per meaningful event:
| Date and time zone | Event | Source reference | Why it matters | Uncertainty |
|---|---|---|---|---|
| ___ | Offer or order issued | ___ | Requirement basis | ___ |
| ___ | Change discussed or agreed | ___ | Affected feature | ___ |
| ___ | Shipment or receipt | ___ | Goods identification | ___ |
| ___ | Inspection or test | ___ | Observed condition | ___ |
| ___ | Supplier response | ___ | Explanation or next step | ___ |
Use the event date and document date separately when they differ. Preserve full conversation context around important statements. If a date is inferred, say so and identify the basis.
Build an evidence index a reviewer can follow
Make each issue traceable through a compact record. Repeat this card for every issue, then list the records on a one-page contents sheet.
| Evidence field | What to record |
|---|---|
| Issue ID | Stable reference used throughout the pack |
| Agreed requirement | Exact document, revision, page or relevant message |
| Observed result | Factual description without assigning intent |
| Affected goods | Order line, quantity, lot, serial or piece identity |
| Evidence files | Report, photograph, video or correspondence IDs |
| Date and author | When recorded and who produced it |
| Method | How the observation or test was made |
| Limitation | Missing context, sample coverage or uncertainty |
| Open response | Supplier explanation or clarification still needed |
A photograph can show a visible condition while leaving measurement or material identity unresolved. A test report can be technically useful but difficult to apply if it does not identify the sampled goods. State those limits plainly. Do not describe a sample result as proof about the entire shipment unless a competent assessment supports that conclusion.
For technical differences, ask the responsible specialist to check the criterion, test method, sample identity and interpretation. For potentially unsafe goods, follow the site's approved safety procedures and competent technical advice. Collecting evidence does not justify using or dismantling an unsafe item.
Protect originals and label every working copy
Keep unedited originals in a controlled folder with their original filenames where practical. Work from copies when adding arrows, combining PDFs, translating text or redacting information. Keep a simple link from each working copy back to its original.
Use descriptive evidence IDs such as “E014, receiving photograph, unit identifier visible.” The ID should remain stable when the summary changes. Record who supplied third-party documents and when they were received; do not present them as independently verified merely because they arrived as PDFs.
A useful package has four parts:
- A concise issue summary and evidence index
- The dated chronology
- Clearly labeled working copies for review
- Separately retained originals available through an appropriate channel
Redact unrelated personal or commercially sensitive information from shared copies without removing context needed to understand the issue. Check every attachment and access permission against the intended recipient. Preserve the unredacted original under appropriate access controls.
Check the submission step before pressing send
On a marketplace, follow the procedure shown for the actual order and case. Alibaba's public Trade Assurance refund information describes a refund-request and resolution process and directs buyers to eligibility conditions. It is not a substitute for checking your order's coverage, current case instructions or remaining submission opportunities.
Before submission, confirm:
- The correct order, case and recipient
- Applicable deadlines and their time zones
- Accepted file types, sizes and attachment limits
- Whether translations or particular evidence formats are requested
- What submitting or closing the current step will do
- How receipt and the submitted version will be recorded
If the next step is unclear or a submission window appears closed, use the platform's official support route for clarification. Do not assume you can reopen a step later. Obtain qualified professional advice promptly where legal rights, contractual notices or consequential deadlines are involved; this checklist does not establish a time limit or remedy.
Leave a clear record of what was actually sent
Save the final submitted package, its index version, submission time and receipt or case confirmation. Log subsequent requests and responses against the same issue IDs. If new evidence changes the picture, update the summary transparently and preserve the earlier version.
For help organizing the technical purchasing records, contact SourceRating with the product, order context, disputed requirement and available documents. Share the questions you need clarified and the deadlines already stated in your order or case instructions. Technical evidence preparation should support the appropriate commercial or professional review, without promising its outcome.