
Yiwu Supplier Comparison Checklist Across Product Categories
Build category-level Yiwu supplier records, normalize offers, retain Yiwugo evidence, and plan one focused city verification task.
Record Yiwu supplier comparisons in a category-by-category workbook instead of assigning each candidate one overall rank. Give every candidate a stable supplier ID, retain dated Yiwugo shop and product URLs, and normalize offers against the same buyer-defined requirements. Keep unresolved fields visible so one decision-critical gap can become a focused Yiwu verification task. These records support pre-sourcing decisions; they do not prove supplier identity, capability, certification, product conformity, price validity, or contract terms.
Define the comparison boundary
The workbook should answer one decision question: Which supplier-category combinations contain enough comparable information to advance to a focused verification task in Yiwu?
Use three record levels:
- Supplier record: The name and other details displayed by the source, relevant shop URL, capture date, and buyer-assigned supplier ID.
- Category record: The product category, current buyer requirements, category-specific evidence, unresolved questions, and decision status.
- Offer record: The exact product or quotation reviewed, including its source, date, specification basis, quantity basis, and inclusions or exclusions.
Keep the following terms consistent:
- Candidate: A supplier or shop under review. The term does not mean confirmed manufacturer, authorized seller, or approved supplier.
- Comparable: Two offers expressed against the same buyer-defined specification, quantity, unit, currency, and inclusion basis.
- Evidence item: A retained URL, dated page capture, document, note, or other record supporting a particular field.
- Checked field: One data point reviewed through a stated method. It does not mean the supplier as a whole has been verified.
- Unknown: Information that has not been established. Do not substitute “no,” “failed,” or “not offered” unless the evidence supports that result.
Assign one supplier ID to a candidate throughout the workbook, but create a separate row for every supplier-category combination. A positive finding for one category must not be copied into another category without relevant evidence. For example, a documented packaging detail for stationery provides no evidence about the same candidate’s electrical product specifications.
Build the supplier comparison worksheet
The core matrix should make every decisive entry traceable to its source and comparison basis.
| Field | What to record | Comparison rule |
|---|---|---|
| Supplier ID | Stable buyer-assigned identifier | Use the same ID wherever the candidate appears |
| Displayed supplier or shop name | Name exactly as displayed by the source | Preserve conflicting names instead of silently standardizing them |
| Product category | Buyer-defined category label | Use one controlled category list |
| Product or offer ID | Buyer-assigned offer reference | Separate materially different products or terms |
| Yiwugo shop URL | Direct shop page, when available | Treat it as platform-displayed information, not proof of capability |
| Yiwugo product URL | Direct page for the reviewed item | Link it to the relevant category and offer |
| Capture date | Date the page was reviewed or saved | Recheck information that may have changed |
| Requirement version | Version or date of buyer requirements | Compare candidates against the same version |
| Displayed product details | Relevant page text or a precise summary | Record omitted details as unknown |
| Offer basis | Quantity, currency, unit, specifications, and inclusions | Do not compare headline figures with different bases |
| Evidence reference | URL, file name, capture, note, or document ID | Make every decision-relevant entry traceable |
| Review method | Platform review, written clarification, or planned in-person check | State exactly what was checked |
| Conflict or gap | Missing, inconsistent, or unclear information | Retain conflicting versions |
| Category status | Controlled status from the defined list | Apply the same definitions throughout |
| Next action | One specific question or check | Assign an owner and target date |
| Recheck trigger | Date, page change, new offer, or requirement change | Reopen the record when the trigger occurs |
Yiwugo shop and product pages can supply discovery and comparison records, but their content should be labeled as platform-displayed information. A listing alone does not establish identity, manufacturing status, certification, capacity, conformity, or commercial terms. Record the access date and retain the exact relevant URL from the Yiwugo official market platform.
Normalize offers before comparing them
Two prices are not comparable merely because they use the same currency. Record enough information to determine whether they share:
- The same product specification and requirement version
- The same unit of measure
- The same quantity or quantity tier
- The same packaging basis
- The same included accessories or components
- The same treatment of samples, tooling, labeling, testing, freight, tax, or other stated items
- A sufficiently similar validity period
If the basis cannot be reconciled, use Not comparable rather than estimating unsupported adjustments.
Control changes to the workbook
The ISO guidance on documented information provides useful principles for identifying, formatting, reviewing, protecting, preserving, revising, retaining, and disposing of records. These principles can be adapted to a sourcing workbook by assigning record IDs and versions, controlling access, retaining prior evidence, and defining recheck or archive rules. Applying them is a recordkeeping method; it does not demonstrate ISO certification or conformity with ISO 9001. See the ISO guidance on documented information.
Maintain a short change log rather than overwriting earlier entries:
| Record ID | Date | Field changed | Previous entry | New entry | Reason | Reviewer |
|---|
Use a practical verification checklist
Before reviewing candidates
- Define each product category independently.
- Write the minimum requirements for each category.
- Separate mandatory conditions from preferences.
- Fix the specification, quantity, unit, currency, and inclusion basis.
- Assign a version and date to each requirement set.
- Decide which missing fields will block advancement.
- Create controlled status labels before entering candidate data.
While collecting Yiwugo records
- Record the exact supplier or shop name displayed.
- Save the direct shop URL where available.
- Save the relevant product-page URL.
- Record the capture or review date.
- Copy only details relevant to the category decision.
- Separate displayed information from buyer interpretation.
- Mark absent information as unknown.
- Create separate offer records for materially different products or terms.
- Preserve conflicts between pages rather than choosing an unsupported version.
- Avoid treating a listing as proof of identity, manufacturing status, certification, capacity, or conformity.
When one candidate appears in several categories
- Use one supplier ID but separate category rows.
- Confirm that every URL and evidence item applies to the stated category.
- Record category-specific requirements, exclusions, and gaps.
- Do not reuse one product result as evidence for another category.
- Keep shared supplier-level details separate from product-level findings.
- Assign a separate status to every category before considering any overall decision.
Before planning the Yiwu verification task
- Select an unresolved question that could change the next decision.
- Convert the question into an observable check.
- Define the evidence that must be retained.
- Set the pass, hold, conflict, or not-comparable outcome in advance.
- Identify the candidate, category, and offer covered by the check.
- Assign a responsible person and target date.
- Set a recheck trigger.
- Confirm that current URLs and time-sensitive event information remain available.
- Remove tasks that cannot resolve a defined comparison gap.
After completing the task
- Date and identify every new record.
- Link each finding to the correct supplier-category row.
- Retain the previous entry when information changes.
- Record the method used instead of labeling the entire supplier “verified.”
- Update the category status using predefined rules.
- Document unresolved conflicts.
- Record the next action or stop decision.
- Check that findings have not been generalized to unrelated categories.
Turn one evidence gap into a Yiwu verification task
A useful city task should address one candidate, one category, and one decision-critical uncertainty. Combining unrelated gaps into a broad “verify supplier” instruction makes the result difficult to evaluate or connect to the workbook.
Use this planning card:
| Planning field | Required entry |
|---|---|
| Task ID | Stable buyer-assigned reference |
| Candidate | Supplier ID and displayed name |
| Category | One defined product category |
| Decision to unlock | Exact pre-sourcing choice affected |
| Current evidence | Relevant URLs, captures, and record IDs |
| Unresolved point | One specific missing or conflicting fact |
| Verification action | What the reviewer will inspect, request, or reconcile |
| Required output | Dated note, capture, document reference, or other retained record |
| Acceptance condition | Predefined result required to advance |
| Stop condition | Conflict, absence, or non-comparability that prevents advancement |
| Responsible person | Named record owner |
| Date and location | Planned check details |
| Follow-up | Required status update and next decision |
For example:
- Candidate: Supplier A
- Category: Category 2
- Gap: The product page and recorded offer use different specification descriptions.
- Task: Reconcile both descriptions against the current buyer requirement version and retain the supporting records.
- Acceptance condition: The offer can be expressed on the same specification and offer basis as the other candidates.
- Stop condition: The discrepancy remains unresolved or prevents a comparable record.
- Resulting status: Advance to the next defined step, mark Needs clarification, or mark Not comparable.
If an event-based visit is relevant, consult the official Yiwu Fair introduction and recheck current dates, venue details, page descriptions, and URLs before travel. A general fair introduction does not establish that a particular candidate will participate or that any exhibitor is qualified or suitable. Keep fair-planning records separate from Yiwugo platform evidence.
Apply category-level decision rules
Review each supplier-category row in this order:
- Confirm that the candidate, category, and offer are identifiable.
- Confirm that the offer uses the current buyer requirement version.
- Determine whether the offer basis is comparable.
- Review missing fields and conflicting evidence.
- Decide whether one focused Yiwu task could resolve the decision-critical gap.
- Advance, hold, or stop at the category level.
Use controlled status definitions:
| Status | Meaning |
|---|---|
| Not reviewed | No structured review has been completed |
| Documented | Relevant information and its source have been recorded, without implying independent verification |
| Needs clarification | A specific missing point prevents a decision |
| Conflict | Retained sources or records disagree |
| Not comparable | Available offers lack a sufficient common comparison basis |
| Ready for verification | The remaining uncertainty has been converted into a defined verification task |
A single overall score is easy to scan, but it can conceal a mandatory failure in one category. Separate category records require more maintenance, yet they preserve the evidence behind each decision. Additional fields improve traceability only when they support the comparison or follow-up; unrelated data adds maintenance without improving the decision.
Older records should remain available as history, but they may no longer describe the current page or offer. Preserve them with a clear recheck status rather than replacing them. Do not average away a mandatory category gap: advance a candidate only for categories whose evidence and comparison basis meet the buyer’s predefined conditions.
Sources
-
Yiwugo official market platform
Used for relevant shop and product URLs as discovery and comparison evidence. Its pages represent platform-displayed information and do not independently establish capability, conformity, certification, or commercial terms. Record the access date and recheck page availability. -
Yiwu Fair official introduction
Used only to decide whether fair-related information belongs in a planned Yiwu task. It is a general event reference, not supplier-specific verification evidence. Recheck current event details and the URL before publication or travel. -
ISO, Guidance on the Requirements for Documented Information of ISO 9001:2015
Used as the basis for record identification, format, review, access, preservation, change control, retention, and disposition principles. Applying these ideas does not establish certification or full conformity with ISO 9001.
Scope and limits
This method supports pre-sourcing comparison records and verification-task planning, not final supplier approval. It does not establish supplier identity, ownership, authority, manufacturing status, capacity, certification, legal compliance, product quality, price validity, or contract suitability.
Treat Yiwugo content as platform-displayed information and the Yiwu Fair introduction as general visit-planning material. Do not generalize evidence from one product category to another. Before acting, recheck time-sensitive facts and URLs, retain each source’s date and scope, and convert the remaining decision-critical uncertainty into one clearly documented Yiwu verification task.
Sourcing information earns its value when it is verified, compared and turned into a decision.