datawebotMade-in-China: supplier reports and orders
Separate Made-in-China.com supplier reports from product certificates, quote revisions and secured-order events; compare MOQ and delivery terms on the same basis.
Separate supplier assessment from product and order evidence
Made-in-China.com describes its Audited Supplier reports at the supplier level and says the process includes on-site verification. That describes the scope of the report; it does not make the report a certificate for a particular model, an inspection result for a shipment lot, or evidence of the terms accepted in an STS order. Keep each evidence record at its own grain.
Scroll to compare →
| Record grain | Buyer-held fields | What it can answer |
|---|---|---|
| Audited Supplier report | Supplier entity/site reference; report issuer; report version/date; stated scope; findings or follow-up reference | What the particular supplier assessment says about its stated subject and scope. |
| Product certificate | Issuer; standard or regulation; exact model/material; certificate identifier; validity and covered market | Whether the certificate identifies the product and scope being evaluated. |
| Lot inspection | Buyer order/lot reference; sampled quantity; method; inspection date; result and limitations | What was inspected for the identified lot or sample; not every later production run. |
| STS order | Buyer transaction reference; order-start type; accepted quote revision; agreed specification, quantity and terms; dated event references | What the parties recorded for one order and its own payment, shipment, receipt or issue events. |
Preserve the three STS order starts
The current Made-in-China.com Buyer’s Guide distinguishes three Secured Trading Service order starts by who initiates the record. These labels help explain why a buyer-owned quote trail may begin differently; they do not replace the accepted order terms or the event documents for a transaction.
Scroll to compare →
| Guide’s order type | Guide’s described starting point | Buyer-owned record to connect |
|---|---|---|
| Negotiated Order | Buyer-initiated; the guide describes supplier quotation and negotiation before payment. | Request reference, each dated quote revision, accepted revision and resulting order reference. |
| Rush Order | Buyer-initiated fixed order; the guide says it can proceed to payment without supplier negotiation. | Fixed specification and quantity, displayed terms as retained by the buyer, acceptance/payment evidence and later events. |
| Supplier Drafted Order | The guide describes an order created by the supplier for the buyer to review through the buyer’s account. | Buyer-controlled order reference, reviewed terms, acceptance evidence and subsequent payment/shipment events; exclude account credentials and personal contact fields. |
Follow a hypothetical buyer-owned quote into an order
Hypothetical buyer-owned example: the references and quantities below are hypothetical buyer records, not MIC listings, live orders, or retrieved output. The useful join is the quote revision accepted into one order, followed by dated evidence about that order.
Scroll to compare →
| Hypothetical event | Buyer-owned fields to preserve | Keep it separate from |
|---|---|---|
| Request REQ-17 asks for 480 units | Buyer specification R1; unit; required market/destination; requested quantity; buyer record date | Any supplier listing, profile or contact record. |
| Quote Q-17 revision A states MOQ 500 | Quote revision; MOQ and tier; quantity basis; currency/unit; issue and expiry dates; configuration; stated delivery basis | A confirmed order or a price for a different configuration. |
| Buyer requests revision B and accepts 500 units | Changed specification fields; revision date; approval role; accepted revision; buyer order reference ORD-17 | The superseded quote or an unaccepted draft. |
| Inspection, dispatch and receipt are recorded | Order/lot link; sample scope and result; dispatch document/date; quantity shipped and received; event source/date | The supplier assessment or an unlabeled order status. |
| A hypothetical receipt issue is opened | Issue date; affected quantity; evidence reference; agreed response and closure date | A general claim about protection, refund eligibility or transaction outcome. |
Compare MOQ and delivery terms on the same basis
A unit amount is not comparable by itself. Match the requested configuration, quantity tier, unit, currency and validity first. When an Incoterms® rule is used, retain the rule, edition and named place; record freight, insurance, duties, packaging, customization and other charges separately when the quote does not include them. The ICC overview supplies trade-term context; the actual quote and contract remain the transaction records.
Scroll to compare →
| Comparison check | Record with each buyer quote | Why it matters |
|---|---|---|
| MOQ and quantity tier | Minimum, quoted tier, requested quantity and unit | A quote for a different quantity tier may have a different basis even when it describes the same specification. |
| Configuration and revision | Buyer specification/version; material, dimensions, packaging or customization fields relevant to the request | The accepted order must point to the revision that was actually approved. |
| Price basis | Currency; per-piece, per-set or other unit; included and excluded charges; issue/expiry dates | Normalizing only the displayed unit amount can omit material charges or compare expired terms. |
| Delivery basis | Incoterms® rule and edition; exact named place; destination; separately billed freight/insurance/duties | The named rule and place shape the quote’s cost and delivery allocation; they are not interchangeable labels. |
| Order connection | Order type; quote revision accepted; order reference and acceptance date | The MIC guide’s different order starts do not remove the need to retain the buyer’s agreed terms. |
Separate MIC source documents from buyer event fields
The buyer-owned example tracks quote and order references without turning account, contact or service-use data into procurement fields.
Scroll to compare →
| Evidence | Version or date shown | Scope described on the source page |
|---|---|---|
| Buyer User Agreement | Buyers Version updated 14 October 2025; effective 21 October 2025 | §II.3(5) addresses collecting other users’ information, including email addresses and user IDs, without prior consent of MIC and those users. §II.3(7) lists copying, translation and reverse-engineering acts involving MIC. §V.3 identifies MIC-published and compiled content and states restrictions on copying, citing, linking or other use without Focus Tech’s written consent, except as mandatorily provided by law. |
| Buyer Privacy Policy | Buyers Version updated 3 September 2026; effective 10 September 2026 | Distinguishes personal information actively provided for product or service functions from information about service use, including service logs. The example leaves account identifiers, contact details, messages and activity logs out of the buyer-owned event model. |
Content reviewed 2026-10-07.