Supplier Evidence Desk Review — Illustrative Example
Illustrative example — fictional company and synthetic evidence. No real supplier has been assessed.
This example shows how to record evidence, identify gaps and assign follow-up. It contains no official records, certificates, tax identifiers or testimonials, and claims no official status. AMMEX is not currently offering this review as a public service.
Scope
The hypothetical buyer is considering an order involving customer-owned components. This example uses three synthetic document summaries. The product, plant, legal entity, program status and proposed import route are not established.
Evidence reviewed
- Example prepared: October 7, 2026. This is the editorial preparation date, not a date on which supplier evidence was received or checked.
- Source list: synthetic receiving-process summary; synthetic inventory extract summary; synthetic logistics-question summary. No underlying company documents exist.
- Document dates and versions: not specified in this example.
- Public-record checking: not performed on a real company. No public-source observations or official-status findings are represented.
- Other work: no plant visit, issuer check, customer-reference call, legal review or capacity assessment has been performed.
In an actual evidence register, receipt dates, sources and checks would need their own records. Here, “provided” describes a synthetic summary included in the exercise; “missing” describes an intentionally omitted item. Neither is a conclusion about a supplier.
Evidence register
On a narrow screen, scroll the table sideways to see every column.
| Request and status in the exercise | Synthetic evidence summary | What remains unresolved | Follow-up question and role |
|---|---|---|---|
| Receiving process — provided; needs review | The receiving summary describes a separate bin for customer-owned components. | No dated ownership agreement or link from receipt to inventory is included. | Buyer and receiving owner: how would ownership and receipt be recorded for this order? |
| Inventory relationship — provided; needs review | The inventory summary mentions opening, consumed and remaining quantities. | Cutoff, units, source-document relationship and treatment of other movements are unconfirmed. | Inventory owner: which records and definitions would make the quantities comparable? |
| Logistics plan — provided; needs review | The logistics summary lists questions for pickup and delivery. | No importing party, regime, broker instruction or documented route is established. | Trade and logistics owners: who would confirm those points before pickup? |
| Program information — missing | No authorization document or official record is created for this example. | Entity, site, applicable scope and current status are not assessed. | Responsible trade party: what current evidence would be needed for the proposed operation? |
| Quality and capacity evidence — missing | No certificate, test record, audit report or capacity commitment is created. | Product requirements, process performance and order capacity are not assessed. | Buyer and quality team: which requirements and further assessments would apply? |
Open questions
Keep the questions above open. Assign a responsible role, specify the evidence to request and set a follow-up date. The summaries do not establish a document's authenticity, currency or completeness.
Next steps and limitations
This example establishes no legal standing, customs treatment, origin eligibility, product quality, delivery performance or supplier capacity. It contains no supplier score or recommendation. A desk review would remain limited to its actual scope, evidence and dated checks; the responsible teams would decide what further work their order needs.
Prepare your own evidence requests
Use the checklist to structure your own evidence request.
Does your operation have a case this page does not resolve?
If something here is incomplete, out of date or does not cover your situation, tell us. We read everything and correct what needs correcting.