SKU Planning for Scrub Collections: A Clear 7-Step Variant Map
SKU planning for scrub collections gives each stockable garment variant a clear internal identity. A product name such as classic scrub trousers is not enough to distinguish colour, waist size, length and other options that affect an order. Without a consistent map, buyers can create duplicate records, combine different garments in one stock line or send the wrong variant to a customer. This guide explains seven steps for medical uniform brands, distributors and programme buyers preparing their product data. It focuses on internal stock codes and their connection to the approved garment specification.
1. Define what SKU planning for scrub collections must identify
Decide what the business treats as a separate stock keeping unit. SKU planning for scrub collections should distinguish the garment variants that are stored, ordered, picked or replenished separately. Our scrub tops and scrub pants manufacturing pages support specifying those product families. A top in medium navy and the same top in large navy normally need separate inventory records when they are supplied as separate variants. The product family can still share a customer-facing listing or collection name.
Keep the internal code’s purpose clear. GS1 US product field definitions describe the SKU as an internal product identifier. SKU planning for scrub collections should therefore distinguish that code from a supplier reference, a barcode field or an external trade-item identifier. The same garment can have several legitimate references serving different systems, but their relationship needs to be recorded. Do not invent a number and present it as a licensed GTIN simply because the inventory software has a field for one.
SKU planning for scrub collections should separate product identity from stock location and individual garment history. Moving a box from one warehouse to another does not change the garment’s size or colour. An individual returned item may also need its own condition or movement record, while remaining part of the same product variant. Our issue and return tracking guide explains those operational distinctions. Keep the variant map focused on what the item is, then use the appropriate records to show where it is and whether it is available.
2. Build the variant matrix before assigning codes
List the attributes that create a product variant in the actual collection. SKU planning for scrub collections commonly needs a style code, colour code, size code and length option, with other attributes included when they define separately supplied stock. Our collection expansion guide supports reviewing the range before it grows. Do not generate every mathematically possible combination if some are not offered. Mark which colours and lengths are available for each style so the catalogue does not advertise or order variants that have never been approved.
Calculate the scale of the variant matrix explicitly. In an illustrative range, two top styles offered in three colours and six sizes create thirty-six top variants. Two trouser styles in three colours, six sizes and three lengths create one hundred and eight trouser variants if every combination is offered. SKU planning for scrub collections would therefore need one hundred and forty-four stock records for those garments. This is a product-data example, not a recommended range size or order quantity; each variant can have a different purchasing and stock plan.
Check whether a proposed option is permanent stock or a customer-specific instruction. Name embroidery, a one-off adjustment or an approved client logo may require a separate order reference rather than adding every possible name to the standard catalogue. The appropriate structure depends on how the business stocks and fulfils those items. Our multiple logo guide supports separating approved decoration versions. Preserve enough detail for accurate fulfilment without turning an unlimited set of personalisation requests into an uncontrolled list of inventory variants.
3. Choose a code format the team can use consistently
Create a short, documented format that fits the systems involved. SKU planning for scrub collections should use consistent abbreviations and a clear way to distinguish variants. Shopify’s SKU guidance recommends unique, simple and consistent codes and warns about characters that can be confused. Those principles are useful when designing the internal map, but the business should verify the requirements of its own inventory and sales systems. Avoid embedding changeable details such as a retail price or warehouse shelf in the permanent product code.
Use a worked example to test whether the format is understandable. SKU planning for scrub collections might use ST21-NV-M for a particular top style in navy and medium, and SP41-NV-M-T for a particular trouser style in navy, medium and tall length. These are illustrative internal codes, not product identifiers assigned by GS1 or actual stock offered on this website. Keep the meaning of each segment in a reference list. If NV represents navy in one style, it should not represent a different colour elsewhere in the same system.
Test SKU planning for scrub collections with the people who receive and pick garments. Ask whether two similar records can be distinguished quickly and whether the printed label remains readable in the intended format. Keep the product description visible alongside the code so staff do not need to memorise every abbreviation. A system that looks elegant in a spreadsheet may still create mistakes when a picking list truncates part of the code or a label uses a small type size. Resolve those practical issues before assigning the format across the full collection.
4. Keep the master inventory record complete
Link each code to the approved garment information. SKU planning for scrub collections should preserve the style description, colour reference, size chart version, length, material and relevant decoration details in the master inventory record. Our tech pack checklist supports maintaining the technical reference. The code is a pointer to that information, not a replacement for it. A supplier should be able to confirm which approved specification belongs to a code without guessing from a short abbreviation or a customer-facing product title.
Store the supplier reference and any external identifier in separate fields. SKU planning for scrub collections should make the mapping explicit when the factory, distributor and retailer use different references for the same approved garment. Do not overwrite an internal code with a vendor code without checking the effect on open orders, stock records and integrations. A mapping table allows each party to retain its own reference while confirming the same variant. Keep ownership of updates clear so a change in one system does not silently point an existing SKU to a different product.
The following field structure is a practical starting point for the product catalogue. Adapt it to the business’s systems and keep the technical details in the approved specification. Check a small group of records through ordering, receipt, picking and a return before importing the whole range. That exercise can reveal missing length information or inconsistent colour descriptions early. Do not treat a successful file import as proof that the product data is correct; verify that the resulting records identify the intended garments.
| Master field | Purpose |
|---|---|
| Internal SKU | Unique code for the stockable variant |
| Variant description | Style, colour, size and length in readable words |
| Specification reference | Approved garment and sample version |
| Supplier reference | The corresponding factory or vendor code |
| External identifier | Authorised trade-item identifier where applicable |
| Lifecycle status | Proposed, active, restricted or discontinued |
5. Resolve sets, bundles and separately sold garments
Decide whether a scrub set is physically stocked as one fixed combination or assembled from separate components. SKU planning for scrub collections needs that distinction before bundle mapping is configured. Our scrub sets page supports discussing coordinated products. A fixed medium top and medium trouser pack differs from a customer-selected medium top with large trousers. Record the actual fulfilment method and the component relationship so the system can deduct the correct garments when a set is sold.
Avoid counting the same physical garments as independent stock in both a bundle and its components. SKU planning for scrub collections should be tested with a sample order and a return to confirm how quantities move in the chosen system. A bundle label may need its own reference, while its availability depends on the component records. Do not assume the platform handles that relationship automatically. Check the implemented workflow with the responsible system owner and preserve the approved mapping before accepting orders that combine different sizes or garment options.
6. Prevent duplicate records and uncontrolled code changes
Check for a duplicate SKU before adding a new variant. SKU planning for scrub collections should have one authorised creation process, with validation against the existing catalogue and any reserved codes. Similar product names do not necessarily mean the garments are identical, and different names do not necessarily mean they need separate stock records. Compare the approved specification and fulfilment unit. Keep test records distinguishable from active products, and do not release a code into labels or purchase orders until the relevant data has been reviewed.
Keep product codes stable across locations and channels when they identify the same variant. SKU planning for scrub collections can use separate stock balances and channel mappings without renaming the garment every time it moves. Shopify’s guidance describes using the same variant SKU across locations while tracking inventory by location. Check how that principle applies to the actual systems in use. If a code must change, plan the transition for open orders, labels, historical reports and returns instead of replacing it in one spreadsheet and assuming every connected record will follow.
7. Plan for revisions, discontinuation and replenishment
Define how a material or construction change affects product identity. SKU planning for scrub collections should not silently reuse a code for a meaningfully different garment while older stock is still sold under the same description. Review the actual change and any external identification rules with the responsible team. Our change management guide supports preserving approvals. Keep the revised specification, effective product version and remaining old stock visible so customer service and fulfilment can distinguish what was ordered and supplied.
Retain a discontinued variant in the historical map rather than assigning its code to an unrelated product. SKU planning for scrub collections needs to support old orders, returns and repeat enquiries as well as current stock. Record whether the item can still be reordered, has a replacement option or is no longer available. Our repeat order specification guide helps preserve continuity. A clear lifecycle status allows purchasing to consolidate active demand without accidentally reviving an obsolete colour or sending a substitute that the buyer has not approved.
For an international manufacturing enquiry, provide Medical Uniform BD with the approved variant matrix, garment specifications, quantity breakdown and required label or packing references. Our own sample section supports development before bulk approval. Use our enquiry page to confirm the collection and applicable production terms. The internal code system should make the order easier to understand, while the full specification remains the manufacturing reference. A controlled mapping between those records helps each party discuss the same garment from sampling through receipt and replenishment.