TL;DR · Direct answer
The buying decision in brief
For each label and manual, record the exact model/configuration scope, source or holder as stated, version/date, language, named market and reviewer. Compare those fields and the buyer’s selected requirement references against the current quotation and product images, then log each match, difference or missing item. Keep document identity/version review separate from a legal compliance decision, which must use applicable official sources and qualified review.
01 / Buying guide
Establish the exact product and market baseline first
Record the baseline model/reference, configuration, documented intended use when relevant, target market, reviewer and review date. Link the current controlled identity record or quote as an input. If the model or configuration is unclear, stop: the reviewer cannot meaningfully decide whether a label or manual belongs to the item under review.
Beauty equipment is not automatically a medical device. Product status and applicable rules depend on the actual product, intended purpose, role and jurisdiction. This guide provides a recordkeeping method, not classification, legal advice, compliance approval or a market-access decision.
02 / Buying guide
Create separate rows for labels and manuals
For every file, record document title or identifier, source/holder as stated, revision/version, date, language, stated model/configuration coverage, target market, reviewer and evidence location. Separate product labels, packaging labels, instructions/manuals and other material when they are distinct controlled items.
A current-looking filename does not prove the version is current. A family manual does not automatically cover every variant. Ask the responsible source to explain the stated scope whenever the model, configuration, language or revision does not line up. Record what the source establishes and what remains unknown.
03 / Buying guide
Compare the label and manual against the project references
Use the same baseline to compare model identifiers, configuration references, issue/revision markers, named language and market, and any product identifiers or instructions present in both documents. Then compare relevant fields with the active quotation, product images and the buyer’s selected market-requirement references. Log each item as match, difference, missing or not assessed and cite the evidence row.
Do not import a rule from another country, model or device class. FDA sources describe U.S. medical-device requirements in their applicable scope. The European Commission’s language tables are a navigation aid for devices under MDR/IVDR; check the latest official table and determine applicability with a qualified reviewer.
04 / Buying guide
Separate file consistency from market-rule assessment
A reviewer may establish that two files share an identifier, revision and language while being unable to decide whether the content satisfies a jurisdiction’s law. Use two distinct review outcomes: (1) identity/version and cross-document consistency, and (2) assessment against named market requirements by the responsible qualified reviewer.
For the second track, record the official source title and section, access/review date, product and role scope, reviewer and written conclusion. If applicability or interpretation is unresolved, mark the item pending and route it to the responsible regulatory professional or competent authority source. Legibility or translation alone does not establish legal adequacy.
05 / Buying guide
Hold discrepancies until the responsible party closes them in writing
Pause the affected review when the model identifier is missing, revisions conflict, a family scope is unexplained, the language or market is unclear, a file cannot be read, or the label/manual differs from the quote or image set. Record the precise mismatch, source pair, activity affected, responsible party, question and written evidence required to close it.
When a corrected file arrives, preserve the prior version, compare the new one against the same baseline and record reviewer/date. Close only the discrepancy that the response resolves. One corrected manual does not approve other configurations, labels, markets or legal requirements.
06 / Buying guide
Keep a versioned audit trail for every review decision
Use one record ID per model/configuration and target market. For each document row, capture the file name, source or holder as presented, date received, document revision, stated language, scope statement, public or controlled source location, reviewer, review date, comparison result and next action. For each market-rule row, additionally capture the official authority, source title and provision, access date, product/role scope, qualified reviewer and written disposition.
Keep “not assessed,” “not available,” “mismatch,” “pending qualified review” and “closed with evidence” as different outcomes. A checked box without a source, reviewer and date is not an audit trail. If the baseline changes, open a new revision and repeat only the dependent checks after documenting which rows were affected. Keep source files in the controlled project repository or buyer system, and publish only this blank template—not private evidence, inquiry records or internal approval notes.
Comparison visual
Two review tracks with separate outcomes
Identity and version
Model/configuration, source, revision/date, language and document scope
Shows what file was reviewed; not legal conformity
Cross-document consistency
Comparison of label/manual/quote/image references
Identifies matches and differences; not market access
Market requirement
Official current source, provision, scope and qualified reviewer
Applicability requires jurisdiction-specific review
Unresolved item
Mismatch, affected step, owner and written closure evidence
Keep on hold until that specific issue is answered
Decision flow
Label and manual review sequence
- 01
Baseline
Identify model, configuration, intended-use context and target market.
- 02
Index
Log each label/manual source, holder, version, date, language and scope.
- 03
Compare
Check relevant fields against each other and the active project references.
- 04
Route
Send legal applicability questions to the qualified market reviewer.
- 05
Close
Keep mismatches on hold until written, versioned evidence resolves them.
Practical table
Reusable label/manual review record
Each checklist row shows every comparison field.
| Review field | Capture | Status / evidence |
|---|---|---|
| Product baseline | Model, configuration, target market and intended-use source | Confirmed / hold / owner |
| File identity | Name, source/holder, version/date, language and stated scope | Matched / different / missing |
| Cross-check | Relevant quote, product image and buyer market-reference fields | Evidence link and discrepancy |
| Market assessment | Official source/section, applicability scope and qualified reviewer | Pending / reviewed / conclusion record |
| Closure | Question, responsible party, corrected file version and review date | Open / closed with written evidence |
Buyer FAQ
Frequently asked questions
Does this checklist determine whether a beauty device is a medical device?
No. Classification depends on the product, intended purpose and jurisdiction. Confirm applicability through the relevant official sources and qualified professionals.
If a label and manual show the same model, are they compliant?
No. Matching identifiers support an identity/version check only. Legal adequacy and market requirements are separate assessments.
Can a manual for a product family be used for a specific configuration?
Only when the responsible source provides a reviewable scope that covers the exact model/configuration. Do not infer coverage from a similar name or appearance.
What should an importer do when the target language is unclear?
Record the named market and source, hold the affected review, then confirm the applicable language rule using current official material and a qualified reviewer.
Source notes
References and further reading
External references provide general regulatory or industry context; they do not establish approval of a listed product. Accessed 17 October 2026.
- FDA: Device Labeling overview ↗
- FDA: Quality System Regulation Labeling Requirements ↗
- FDA: General Device Labeling Requirements ↗
- European Commission: Medical device language requirements ↗
- EU MDR 2017/745, Annex I, section 23 ↗
- AXDCARE: IFU importer review before packaging approval ↗
- TrueMedDevice: U.S. importer, labeler and UDI handoff ↗
Submit a model-scoped document question
Bring the target model and configuration, target market, existing label and manual versions, and the unresolved comparison points. The request starts a project conversation; it is not a promise of regulatory review, certification or market-access advice.
Request a quotation →