Bulk knitwear barcodes: approve the right hangtag for every garment variant

Start with the retailer requirement and a named data owner

For an overseas brand sending sweaters directly into a retailer or distribution centre, hangtags are part of the order specification. Ask the buyer for the required barcode type, product data fields, tag layout, attachment position and receiving instructions before printing. Name the person who supplies and approves the product identifiers; do not ask the print supplier to invent them. Keep an internal SKU, a GS1 GTIN and any retailer-specific reference in separate fields. Also clarify whether a barcode is needed on the hangtag, individual bag, outer carton or several levels. Approval at one level does not approve the others. If requirements are still missing, quote the label work as pending rather than treating a generic tag as final.

Freeze one mapping row for each sellable variant

GS1 states that each product variation, including a size and colour combination, needs its own GTIN. Ask the buyer to supply the approved identifiers against the exact sellable variants; do not use one style-level number for all sizes. As a planning example, one sweater in three colours and four sizes has twelve variants if all combinations are sold individually. This is a mapping example, not a WTBF order record. The working file should connect each row to the style revision, colour reference, size, internal SKU, buyer-supplied GTIN and tag artwork revision. Preserve identifiers as text so leading zeroes are not lost in a spreadsheet. Flag duplicate identifiers, missing rows and descriptions that disagree before issuing print files.

GS1 — GTINs for size and colour variations↗

Approve data, artwork and the physical print separately

Have the approver compare the decoded value with the authorised variant file, then compare the visible style, colour and size text with the same row. A successful scan only establishes that a particular scanner read a symbol; it does not establish that the garment-to-data mapping is correct. Review the actual printed stock and finish, not only a screen PDF. GS1 India identifies symbol size, placement, contrast, quiet zones and reflective backgrounds as verification considerations, and warns that a local scan does not guarantee performance on every scanner. Agree the required verification specification, report and provider with the buyer before printing. No universal print grade or symbol dimension is prescribed here; these depend on the agreed application.

GS1 India — barcode print verification considerations↗

Keep a short, usable release record

Use separate approval decisions so a signed layout cannot be mistaken for approval of every number in a later print run. Retain the authorised data file, artwork revision, physical print reference and written release together. Record which variants were checked and whether any remain on hold. If formal verification is required, identify the tested print sample and the applicable report rather than substituting a screenshot of a scan. Confirm who may release printing, tag attachment and final packing; these can be different decisions.

Prevent mixed revisions during attachment and packing

Separate tags by variant and artwork revision, and identify the garment batch to which they belong. Agree a practical checking plan at tag issue, attachment and final packing; do not imply that an occasional scan checks every piece. Count tags issued, used, damaged and left over separately from garment quantities, so unused tags are not counted as shipped stock. After a data or artwork correction, identify and hold the affected tags and already labelled goods, obtain the revised approval and record the rework coverage. Remove superseded print files from the active production instructions. Recheck the hangtag, bag label and packing record for consistency without treating a retail product barcode as a carton logistics identifier.

Include barcode decisions in the bulk quotation brief

Send WTBF the garment reference, quantity by style, colour and size, sales channel, destination and required arrival date. Include the buyer-approved identifier file, tag artwork, attachment instructions and any barcode verification or receiving requirements. State which files are final and which decisions remain open. Ask the quotation to separate tag development, printing, variable-data handling, required verification and possible relabelling, and confirm who supplies each item. WTBF accepts bulk knitwear projects from 1,000 to 1,000,000 pieces; material availability, label scope and available capacity determine the order plan. Confirm approval deadlines and factory dispatch separately from destination arrival. Use the bulk inquiry route to share the known requirements and request the missing confirmations.