Aesthetic Equipment Distributor Product Naming and SKU Mapping Checklist

Direct answer: A distributor should map each aesthetic-equipment listing to one exact model or documented variant, preserve the supplier name and configuration reference, separate optional accessories from included scope, and assign an internal SKU only after the evidence record is complete. The SKU is an internal control; it is not proof of a certification, clinical result, inventory position, price, warranty, delivery promise, or destination-market eligibility.

Product naming looks like a merchandising task, but inconsistent names can create procurement and support errors. A channel team may use a short commercial label, while a supplier uses a model family, a catalogue row, or a configuration description. If those references are merged without a traceable mapping, a distributor can quote or document the wrong variant. A controlled naming and SKU process keeps the public description, internal record, supplier evidence and open questions connected.

Define the record before choosing the name

Start with a product identity record rather than a creative title. Capture the supplier or catalogue name exactly as received, the source date, model or configuration reference, product family, and the evidence location. Then record the proposed customer-facing name separately. This lets a reviewer see whether a polished listing name is a faithful label or an unsupported expansion.

• Supplier or catalogue name, with source and review date
• Model, variant, or configuration reference when supplied
• Product family and intended B2B channel
• Included hardware, heads, handpieces, accessories, and consumable dependencies
• Available manuals, specification overviews, training material, and support documents
• Open questions, evidence owner, and next review date

RayskinTech’s catalogue covers directions including 448K RF body sculpting, professional dual RF, 7D HIFU, microneedle RF, skin analysis, fractional CO2, diode laser and DPL. These category directions can guide a buyer’s question set, but a category name should not be treated as confirmation of a particular unit’s complete specification.

Use a naming hierarchy that survives channel handoffs

A useful naming hierarchy has three layers. The first is the source identity: the exact name and model reference supplied for review. The second is the internal catalogue label used by procurement, service and content teams. The third is the customer-facing title written in plain language for a distributor or professional buyer. Keep the source identity visible in the internal record even when the public title is shortened.

For example, a catalogue direction can be stored internally as “448K RF Body Sculpting System — configuration under review,” while the public title can use a clear category description only when the underlying record supports it. Do not add words such as “medical-grade,” “certified,” “permanent,” “guaranteed,” or “clinically proven” merely to make a name sound stronger. Those terms require separate evidence and approval, and they can change the meaning of the record.

Map variants without flattening the evidence

One product family may contain different bodies, screens, heads, interfaces, power configurations, accessory packages, or branding options. Create a parent family record only for grouping. Create a child mapping for each distinct documented variant. If the supplier has not provided a variant identifier, mark the field as open instead of generating one that looks authoritative.

This structure prevents a distributor from treating an optional handpiece as included, or from using one SKU for two configurations that require different training or support documents. The internal SKU should point to the evidence record; it should not replace it.

Separate SKU governance from commercial fields

A SKU map should not silently become a price or inventory table. Keep purchase cost, selling price, discount, quotation, stock commitment, freight, payment, warranty, and delivery fields in their appropriate approval-controlled records. A naming review can identify where those decisions are still needed, but it cannot approve them.

Likewise, a product title should not imply certification, market eligibility, treatment suitability, guaranteed performance, or a clinical outcome. Destination-market review and qualified professional decisions remain separate workstreams. For a broader evidence workflow, see the aesthetic equipment procurement evidence glossary. For a model-level reconciliation process, see the model and variant reconciliation worksheet.

Build a practical internal SKU format

Choose a format that is stable, readable and independent of changing marketing language. A distributor might use a family abbreviation, a sequence number and a controlled variant suffix. The exact convention is an internal governance decision. Avoid encoding a temporary price, an unverified technical claim, a supplier promise, or a destination market into the SKU itself.

Document who can create a new SKU, who approves a merge or retirement, and what happens when a source configuration changes. Do not reuse a retired code for a materially different configuration. Keep a change history with the old label, new label, reason, evidence reference and effective date. This is especially important when content, sales, service and procurement teams use different systems.

Test the mapping at three handoff points

Before a record is used externally, test it at the procurement, content and service handoffs. Procurement should be able to locate the exact supplier evidence from the SKU. Content should be able to distinguish supported category language from unresolved fields. Service or training teams should be able to identify the configuration and the documents available for review.

1. Procurement handoff: Can the buyer match the SKU to one documented model or an explicitly open question?
2. Content handoff: Does the public title avoid claims not supported by the source record?
3. Support handoff: Can the operator-support owner find the relevant configuration and document versions?

Record failures as mapping issues, not as reasons to guess. A clear “not provided” status is safer than a plausible but unverified variant code.

FAQ

Should a distributor create a SKU when the supplier has not supplied a model number?

An internal draft SKU may be created for workflow tracking, but it should be clearly marked as provisional and linked to an open evidence item. It should not be presented as a supplier model number or used to imply that the configuration is fully verified.

Can one SKU cover a whole RF, HIFU or laser product family?

Only when the distributor has confirmed that the commercial and operational scope is genuinely identical for the intended use. If bodies, heads, accessories, documents or support requirements differ, use separate child mappings or keep the distinction explicitly open.

Does SKU mapping verify price, stock or certification?

No. SKU mapping improves traceability. Price, inventory, commercial terms, certifications, destination-market eligibility, clinical suitability and performance claims require their own current evidence and approval path.

Request a model-specific mapping review

Building a professional aesthetic-equipment catalogue or distributor product line? Contact RayskinTech to request a specification overview, configuration options, private-label discussion and available documentation for review. Include the product category, intended channel, target market and the naming or variant questions that need to be reconciled.