Reorder Data Guide

Wig SKU Specification: From Approved Sample to Reorder

By LEV Wigs Manufacturing 7 min read

Reorders drift for a boring reason: the specification lives in an email thread, the approved sample lives in a drawer, and nobody can say which version of either the last order actually used. A wig SKU specification fixes that by giving every reorderable product one record — the SKU master — that ties the approved sample, the color references, the version number, and the change history together.

A wig SKU specification ties one SKU to the approved sample, the confirmed measurements, and the version the supplier should use on a reorder. This guide shows brand product managers and distributors what that record must name, how the approved sample attaches to it, and how to identify which version an old order used after a change. It is an order-data tool. Batch-production quality control — inspection sampling, defect grading, escalation — is a separate discipline covered in the site’s sheitel QC guide; this article stops at the data layer that tells production what to make.

Why Reorders Drift: The Specification Lives in an Email Thread

Three scenes account for most reorder disputes:

  • The color lived in a name. “Warm blonde” meant one thing in March and another in September.
  • The reference was an old sample. Production matched a sample that had already been superseded by two revisions.
  • The change had no number. Everyone agreed to “the improvement” — and two orders later, nobody could say which units included it.

None of these is a factory failure; all three are a missing record. A supplier spec-sheet checklist names the same cure from the other side: product name, internal SKU, a version number, an order reference, and a date on every specification (Honsen Source spec-sheet checklist, accessed 2026-11-11). The SKU master below is the buyer-side version of that record.

The SKU Field List: What a Reorderable Wig Record Must Name

This is the core deliverable — a field list for the SKU master. It is a blank template: the exact values come from your supplier’s written confirmation, and the field names below are a recommended set, not an industry standard.

Field groupWhat it must name
Product identitySKU code, product name, current spec version number, spec date
Cap constructionCap type, base materials, cap sizes offered, construction version if it changes
Hair specificationHair description as disclosed by the maker, length and how it is measured
Color referenceColor code on the agreed color reference system + approved swatch ID
Density descriptionDensity in words both sides define — not a bare cross-maker percentage
Cap dimension setThe measured cap dimensions and their agreed tolerance status (blank until agreed in writing)
FinishingHairline treatment, parting, styling defaults as approved on the sample
Packaging & labelsPackaging route (neutral or branded), label fields, artwork version

Two rules make the list work. First, every field names a written answer — if the supplier has not confirmed it in writing, the field stays blank, not guessed. Second, the record references the sample; it never replaces it (next section).

Tying the Approved Sample to the SKU Record

The approved sample is the physical truth the SKU master points to. Supplier guidance on approved samples makes the same link: keep the approved physical reference, and record who approved it and when (Honsen Source, accessed 2026-11-11). Your record should carry:

  • Sample ID — the identifier written on the sample and used in every document that references it.
  • Approval date and approver — who signed off, in what role.
  • “Reference, not replacement” — the record describes the sample; if the sample and the record disagree, production stops until the difference is resolved in writing.

How to request changes to that sample — with photos, targets, and priorities — is the revision-request workflow that comes before approval; this article handles what happens after a change is agreed.

Specifying Color Codes and Approved Swatches, Not by Name

Color is the field most likely to drift, because color names are not specifications. Your SKU master should carry:

  • Reference system — which color ring or swatch set both sides quote against (maker-specific by nature).
  • Color code — the position or number on that system.
  • Approved swatch ID — the physical swatch the sample was matched against, which later orders are checked against.

The color order workflow — reference ranking, named light sources, and the approval sheet — has its own color spec guide; the SKU master stores its output (code + swatch ID + version) as fields.

Spec Versions and Change Sign-Off: One Change, One New Version

When anything in the record changes, the change produces a new version number — the old version is never overwritten. Supplier agreement templates express the same rule: references are named by number and date, and changes take effect through a sign-off, not a conversation. A minimal version log:

VersionWhat changedRaised byConfirmed byEffective date
v1(initial approved spec)—(both parties)(date)
v2(example: base color changed; new swatch approved)(buyer)(supplier, in writing)(date)

The log answers the only question that matters at reorder time: which version is this order following? If an order document does not name a version, that is the first gap to close — before production, not after.

Worked Example: A Color Change and an Old Order

(Illustrative walkthrough; IDs and dates are examples.) Six months ago you ordered SKU WB-104, color swatch CB-12, spec v1. Last month the base color changed and the spec became v2 with swatch CB-19. Today a reorder arrives for WB-104. Which color does it get?

  1. Read the order document. It says: “WB-104 per spec v1, color per CB-12” — version named. If it named nothing, stop and get the version confirmed in writing first.
  2. Pull spec v1 from the version log. The log shows v1 was effective until the v2 sign-off date and names CB-12 as its color swatch.
  3. Verify the swatch still exists. Confirm that the supplier can still use swatch CB-12. If it is unavailable, agree on a replacement in writing before production.
  4. Check the approved sample ID. v1’s sample (SMP-0142, approved March 7) is the physical reference this order is checked against.
  5. Conclusion, written back into the order: “WB-104 reorder follows spec v1: swatch CB-12, sample SMP-0142. v2/CB-19 does not apply to this order.”

Five steps, zero memory. The same walk works for any changed field — cap construction, length, packaging — which is why the version log names what changed, not just that something changed.

Allowed Deviations: Blank Until Agreed in Writing

Tolerances deserve their own warning, because buyers routinely assume defaults that were never agreed:

  • Length tolerance — blank until the supplier confirms in writing how length is measured and what variation is normal.
  • Density description — blank until both sides define the words.
  • Cap dimensions — blank until measured and agreed with a tolerance.
  • Color difference — blank until the swatch and light sources define “matching.”

An empty tolerance field is not an oversight; it is the correct state until a written answer exists. The QC guide’s tolerance discipline applies at batch level; at the record level, the discipline is simply: no written agreement, no number.

The Reorder Archive: What Changes Hands and What Stays on File

When a reorder is placed, both sides should be able to answer from records, not recollection:

  • Buyer holds: the current SKU master, the version log, the approved sample ID and its location, the swatch IDs, and every sign-off.
  • Supplier holds: their production copy of the same references, their batch records, and the sample they check against.
  • Reorder documents must name: SKU, spec version, swatch ID, and sample ID.

If a new buyer inherits the account, this archive is the difference between a smooth handover and starting over. Ask for it to be complete before the second order, while filling the gaps is still cheap.

Wig SKU Specifications: Common Questions

The one the order document names. If the order names no version, stop and confirm it in writing before production — the version log exists so this question always has an answer.

Check the original order for its specification version and swatch ID. If either is missing, use the version log to find the likely match and confirm it with the supplier before ordering.

No. An empty tolerance field means nothing was agreed — which is the correct state until the supplier confirms a measurement method and a variation in writing.

The SKU master, the version log, the approved sample ID with its approval record, the swatch IDs, and every written sign-off. Both sides hold matching copies.

Next Step

A reorderable product is a record, not a memory. Name the fields, tie the sample, number the versions, and leave every unagreed tolerance honestly blank. The next order should be a lookup — and after this guide, it is.

Building Your SKU Master?

Take the field list to your supplier, get every value in writing, and open the version log at v1. A record that survives staff changes is the cheapest reorder insurance there is.

Contact LEV Wigs