How to Build a Small-Business SKU and Barcode System
Share
Build the item master before printing barcode labels. Give each separately counted variant its own record, choose the scan key your software expects, and test the complete transaction.
A useful barcode system starts with a dependable product list. Printing labels before deciding what each number identifies creates attractive stickers that can send staff to the wrong record. Begin with one receiving shelf or a small product category, then expand after the complete receive, sell, return, and count cycle works.
Separate the identifier from its printed carrier
A SKU is your internal stock keeping unit. A GTIN identifies a trade item for use across trading partners; a barcode is the machine-readable carrier of data. GS1 US distinguishes global GTINs from internal SKUs. An internal barcode does not become a retail UPC simply because it scans. For a shop selling mugs, SKU MUG-042-BLU might identify the blue variant.
Its retail GTIN belongs in a separate field. Decide whether the scanning application expects the SKU, the supplier's GTIN, or another internal record key. Keep a lookup relationship rather than replacing one identifier with the other.
Build a small, controlled item master
Copy this structure into your inventory system or spreadsheet:
| Record field | Blue mug example | White mug example |
|---|---|---|
| SKU | MUG-042-BLU | MUG-042-WHT |
| Description | Ceramic mug | Ceramic mug |
| Variant | Blue | White |
| Unit | Each | Each |
| Supplier identifier | SUP-817B | SUP-817W |
| Retail GTIN | Enter assigned value | Enter assigned value |
| Active | Yes | Yes |
Preserve identifiers as text so leading zeros survive import and export. Avoid recycling retired SKUs. Use a separate location field rather than embedding the current shelf into an item number: products move, but their identity should remain stable.
Choose a consistent length and character policy. Short identifiers are easier to fit and key manually. Avoid ambiguous combinations when people must read them, and document whether case matters in your software. Restrict creation rights to named staff and require a duplicate search before adding a record.
Create a readable label before adding decoration
Use the SKU in text, a short description, the variant, and the barcode your application expects. Keep price separate if it changes often. An illustrative layout contains:
- Product: CERAMIC MUG — BLUE
- SKU: MUG-042-BLU
- Barcode: generate from the approved SKU field
- Human-readable barcode value: MUG-042-BLU
Generate the symbol with barcode software; typing characters in an ordinary font does not create a barcode. For a nominal DYMO 30334 layout, set the document to 2 1/4 × 1 1/4 inches and confirm the actual media specification. This is a canvas size, not a promise that every SKU will fit.
Give the symbol adequate quiet zones, then test the longest production identifier at the actual printer resolution. Remove optional text or select a larger format before squeezing the bars. Printer compatibility must be checked separately from label dimensions.
Test the transaction, not just the beep
Print a small pilot batch. Scan each label into receiving, picking, checkout, and returns where relevant. Confirm the displayed product, variant, unit, and quantity. A scan that reads cleanly but selects a case instead of an each is a failed workflow. Test duplicate handling by trying to import an existing identifier into a second record.
The system should block it or clearly flag it for review. Also test inactive records, missing supplier numbers, and a product with two valid supplier codes. Decide which aliases are permitted and which identifier staff should print.
Keep changes accountable
Record who created or changed a SKU, the date, and the reason. When replacing labels, isolate the affected stock and reconcile its quantity before returning it to the shelf. Do not leave old and new scannable identifiers visible if they lead to different records. At rollout, keep a sample label beside its approved item-master record.
Recheck samples after changing label stock, printer settings, software, or scanner configuration. Compare the exact label format and pack specification with your purchasing record before scaling the system to another station.
Pilot these four edge cases
- A product variant with the longest SKU in the proposed format.
- An each and a case of the same product, if both are handled.
- A returned item carrying an older label.
- An inactive item that should be blocked or flagged by the application.