Canton Fair Sample Follow-Up Checklist: Specs and Ownership

Use one post-Canton-Fair record for each sample. Link the contact, requested specification, revision history, custody, payment status, supporting files, and next action. First verify that the lead is associated with the Canton Fair rather than another event. Then compare what was requested, confirmed, dispatched, and received. This log reveals missing evidence and supports an internal decision; it does not establish legal ownership, validate a supplier, or prove product compliance.

Define the verification decision

The decision is whether the available records are sufficient to proceed, request a revision, return or retain the sample, or stop work on that specific sample.

Treat every sample as a distinct verification task:

• Assign one unique internal sample ID.
• Link the sample to one event-origin record.
• Create separate entries for materially different versions or specification revisions.
• Do not combine several samples into one status line merely because they came from the same contact.
• Link replacement samples to the earlier sample ID without overwriting the earlier record.

The log must distinguish four stages:

Stage	Meaning
Requested	What the buyer asked the contact to provide after the event
Confirmed	What the contact explicitly agreed in writing to provide
Dispatched	What the available shipment records say was sent
Received and checked	What the buyer physically received and compared with the active specification

For this workflow, use “ownership” narrowly. Record who currently holds the physical sample, who paid any documented sample or delivery charge, whether return or disposal instructions exist, who supplied drawings or packaging references, and who has internal approval authority.

These entries document statements and evidence. They do not establish legal title, intellectual-property rights, supplier legitimacy, or product conformity.

Confirm the event origin before logging the sample

Check event identity before entering supplier or sample details. Otherwise, contacts from the Canton Fair, CIFF Guangzhou, Yiwu Fair, or another event may be mixed into the same follow-up queue.

Use the relevant official event page only to classify the stated event origin. The Canton Fair official site, CIFF Guangzhou official fair-information page, and Yiwu Fair official introduction identify their respective events. They do not verify that a particular contact, company, or product participated.

Event-origin field	Verification action	Acceptable log evidence	Do not infer
Canton Fair	Compare the recorded event name and URL with the Canton Fair official site	Official URL plus the buyer’s badge scan, meeting note, email, or contact record	That the official site validates a contact, supplier, or product
CIFF Guangzhou	Check the CIFF Guangzhou official fair-information page when the record may relate to that event	Official event URL and matching internal contact evidence	That a CIFF Guangzhou contact was met at the Canton Fair
Yiwu Fair	Check the Yiwu Fair official introduction when the record may relate to that event	Official event URL and matching internal contact evidence	That a Yiwu Fair contact was met at the Canton Fair
Unclear or conflicting origin	Mark event origin unresolved and assign a verification action	Notes showing the conflicting event names, URLs, or internal records	A best-guess event classification

Add an event-origin confidence field:

• Verified: Internal evidence and the named official event identity agree.
• Unresolved: Evidence is missing or contradictory.
• Corrected: The original label was changed; the reason, date, and person making the correction are recorded.

Event classification is only the first control. Continue to the practical verification checklist rather than treating an event match as supplier verification.

Build one record for each sample and specification revision

Core identification fields

Log field	What to record	Entry rule
Internal sample ID	A unique buyer-created identifier	Never reuse the ID for a different sample
Event origin	Canton Fair, another verified event, or unresolved	Include the official event reference used for classification
Event-origin confidence	Verified, unresolved, or corrected	Record the evidence and correction history
Contact record	Name and contact details as received	Preserve the original form; record corrections separately
Meeting reference	Buyer note, scanned card, booth note, or follow-up email reference	Leave blank rather than reconstructing missing information
Product/sample label	A neutral description sufficient to distinguish the item	Avoid unverified quality, certification, or performance claims
Stated sample owner	The person or entity described as owner in the available record	Use unresolved when there is no documented statement
Current custodian	The person or organization physically holding the sample	Do not treat custody as proof of legal ownership
Current physical location	Contact, carrier, receiving area, reviewer, or another known location	Add the date on which the location was last confirmed
Record owner	Internal person responsible for the next update	Keep this separate from the sample owner and custodian
Current status	One controlled status label	Update without deleting the previous status history

Specification-control fields

Record specifications as discrete, checkable fields rather than one narrative paragraph:

• Dimensions or size.
• Material as requested or declared.
• Color, finish, or appearance reference.
• Components and included accessories.
• Packaging or labeling instructions.
• Quantity.
• Drawing, image, or reference-file name.
• Revision number or date.
• Required check or acceptance criterion.

Use a comparison table for the active revision:

Specification item	Requested	Contact-confirmed	Received observation	Status
Finish reference	File or code requested by buyer	Exact confirmation or “not confirmed”	Observation after receipt	Match, variance, or unchecked
Dimensions	Buyer’s stated dimensions	Confirmed values or “not confirmed”	Measured values or “not measured”	Match, variance, or unchecked
Included component	Named component and quantity	Confirmed component and quantity	Component found in received package	Match, variance, or unchecked
Packaging reference	File name and revision	Confirmed file and revision	Packaging observed on receipt	Match, variance, or unchecked

These rows are illustrative workflow entries, not facts about products or suppliers associated with the Canton Fair.

Create a new revision when:

• A specification changes after confirmation.
• A replacement sample is requested.
• The received item differs and the contact proposes a revised sample.
• A drawing, image, packaging reference, or acceptance criterion changes materially.

Preserve the original request and every superseded revision. Do not edit the first request to make it match a later confirmation or received item.

Ownership, custody, and evidence fields

Do not collapse all ownership-related information into one column. Keep these fields separate:

Field	Required entry
Stated physical-sample owner	The recorded ownership statement and its source, or unresolved
Current custodian	The person or organization physically holding the sample
Payer shown in records	Who paid a documented sample, delivery, or related charge
Return or disposal instruction	The written instruction, source, date, and any deadline
Design or file source	Who supplied each drawing, image, packaging file, or reference
Internal approval authority	The person or role authorized to make the sample decision
Legal ownership status	Confirmed by appropriate documentation, unresolved, or outside the log’s scope

Attach or reference available evidence:

• Email or written message.
• Invoice or payment record, if one exists.
• Dispatch document.
• Carrier or delivery record.
• Photograph showing the date and sample ID.
• Specification file and revision.
• Internal receiving or inspection note.
• Return, retention, or disposal instruction.

A detailed log improves traceability but requires more maintenance. A short log is easier to update but can hide revision, custody, and evidence gaps. Make identification, active specification revision, custody, evidence, status, and next action mandatory. Keep event-specific narrative notes optional.

Practical verification checklist

Complete this checklist for each sample or materially different revision.

Stage	Verification check	Evidence to attach or reference	Pass condition	Exception action
Event classification	Label the record Canton Fair only when internal evidence supports that origin	Official Canton Fair URL plus meeting or contact record	Event identity is consistent	Mark origin unresolved; do not substitute CIFF Guangzhou or Yiwu Fair
Record creation	Assign a unique sample ID	Log timestamp and record owner	One sample or distinct revision has one traceable record	Split combined entries
Contact preservation	Retain the original contact details	Card scan, note, or original message	Original and corrected details remain distinguishable	Record the discrepancy and correction source
Request baseline	Enter the complete requested specification	Dated request and referenced files	Every required attribute has a value or “not specified”	Return the record to the internal requester for clarification
Confirmation	Record what the contact actually confirmed	Dated written confirmation	Confirmation matches the active revision	Create a variance and follow-up task
File control	Check that drawings, images, and references have identifiable versions	File name, revision, date, and storage reference	Active files can be distinguished from superseded files	Freeze approval until the active version is identified
Ownership statement	Record stated sample ownership, payer, and return instruction separately	Message, invoice, or internal instruction	Each statement has a source or is marked unresolved	Do not infer legal ownership
Custody	Record who physically holds the sample and when this was last confirmed	Dispatch, carrier, delivery, or receiving record	Current location and custodian are traceable	Open a custody exception
Dispatch	Compare the dispatch description with the confirmed sample	Dispatch record, quantity, and sample ID	Description, quantity, and revision align	Request clarification before treating it as the expected sample
Receipt	Log the receipt date, condition, identifiers, and photographs	Receiving note and dated images	The received item can be tied to the dispatch record	Mark the record unmatched and separate the item from approved samples
Specification check	Compare every received attribute with the active request and confirmation	Inspection note or measurement record	Every criterion is marked match, variance, or unchecked	Assign an owner and deadline for each variance
Decision	Record proceed, revise, return, retain, or stop	Dated internal decision	Decision references the reviewed revision and evidence	Keep the status open
Closure	Confirm final custody and unresolved issues	Final log entry	No required action lacks an owner	Escalate instead of closing an incomplete record

Use compact, controlled status labels:

• Open—awaiting evidence
• Open—awaiting sample
• Received—unchecked
• Checked—variance
• Checked—ready for internal decision
• Closed—proceed
• Closed—revise
• Closed—return or retain
• Stopped

Every open item must contain:

• Next action.
• Responsible person.
• Target date.
• Evidence still required.
• Last-updated date.

A compact record header can follow this structure:

Sample ID	Event origin	Active revision	Current custodian	Status	Next action	Owner	Target date
Buyer-created ID	Verified or unresolved origin	Revision and date	Holder and last-confirmed date	Controlled status label	Specific action	Responsible person	Due date

Review exceptions and close the record

Run a final exception review in this order:

1. Confirm the event-origin classification.
2. Confirm the active specification revision.
3. Match the request, confirmation, dispatch, and receipt records.
4. Identify every specification variance or unchecked criterion.
5. Confirm the current custodian and physical location.
6. Check whether ownership-related statements have supporting evidence.
7. Assign unresolved items instead of converting them into assumptions.

Close the record only when:

• A decision has been recorded.
• The active revision is identifiable.
• Current custody is known.
• Every variance is resolved or deliberately accepted by the authorized internal reviewer.
• Return, retention, or disposal instructions are recorded where applicable.
• No required action remains without an owner.

Maintain an audit trail. Preserve previous values, identify who made each change and when, state why a correction was necessary, and link replacement samples to earlier sample IDs.

The final operational action must be explicit: proceed, request a revision, return or retain the sample under documented instructions, or stop the task.

Sources

Official source	URL	Permitted use in this article	Publication freshness record
Canton Fair official site	https://www.cantonfair.org.cn/en-US?m=0	Confirm the official event identity and destination URL	Recheck immediately before publication; record any displayed page date or “no page date displayed,” plus the access date
CIFF Guangzhou official fair information	https://www.ciff-gz.com/en/fair/about	Distinguish CIFF Guangzhou from the Canton Fair when classifying event origin	Recheck immediately before publication; retain any displayed source date and the access date
Yiwu Fair official introduction	https://en.yiwufair.com/aboutfair/intro/	Distinguish Yiwu Fair from the Canton Fair when classifying event origin	Recheck immediately before publication; retain any displayed source date and the access date

These official pages support event identification and event-page references only. Before publication, verify that each URL still resolves and that the event naming has not changed. Do not add dates, venues, attendance figures, exhibitor claims, or event statistics unless they appear on the rechecked source and are recorded with the source date and scope.

Scope and limits

This workflow covers a buyer-controlled post-event log for sample specifications, revisions, evidence, custody, payments shown in available records, and stated ownership information.

It does not verify:

• Supplier identity, capability, authorization, or reliability.
• Product quality, safety, compliance, certification, or performance.
• Prices, payment norms, shipping terms, or commercial practices.
• Legal ownership, intellectual-property rights, contract terms, or entitlement to retain, copy, use, return, or dispose of a sample.
• Whether a specific contact or exhibitor participated in an event.

The three official sources identify their respective events; they do not support broader supplier, product, legal, or market conclusions. If ownership evidence conflicts or legal rights matter, leave the status unresolved and refer the issue for appropriate contractual or legal review rather than inferring an answer.