How to set up barcode and SKU systems for your retail store

A barcode is a machine-readable label — printed as bars and spaces or as a two-dimensional matrix — that encodes a product identifier scannable at the point of sale. A SKU (stock keeping unit) is a merchant-defined alphanumeric code that uniquely identifies a product variant within a store's inventory. Together, barcodes and SKUs form the product identification backbone of any retail POS system, enabling fast checkout, accurate inventory counts, and reliable reorder workflows.

If your store still relies on manual product lookup or handwritten labels, the cost is measurable: slower checkout lines, miscounted inventory, and pricing errors that erode margins. A proper barcode and SKU system is one of the highest-return operational investments a retailer can make.

Understanding barcode formats: UPC, EAN, and internal codes

Not every product arrives with a scannable barcode. Manufacturer-applied barcodes are standard for packaged goods, but loose produce, in-house prepared items, and custom bundles require you to generate your own. The first decision is which format to use.

The three formats most retail stores encounter:

EAN-13 is the dominant format in MENA markets. If your store is in the Gulf, Levant, or North Africa, most supplier barcodes will be EAN-13. Your POS and scanners must handle EAN-13 natively — not as a secondary format.

When to use manufacturer barcodes vs. generating your own:

• Use the manufacturer barcode when the product arrives with one and you sell it as-is. This avoids duplicate entries and simplifies supplier coordination.
• Generate internal barcodes for products you repackage, weigh and price in-store, prepare on-site (bakery, deli), or bundle into custom sets.
• Never assign the same internal barcode to different products. This happens frequently in stores that reuse labels from discontinued items.

For internal barcodes, most retailers use Code 128 or EAN-13 with the 200-299 prefix range, which GS1 standards designate for internal use. Your POS system should enforce uniqueness when you create internal barcodes.

Designing a SKU naming convention that scales

A barcode identifies a product at the scanner. A SKU identifies it in your business logic — purchasing, reporting, shelf management, and cross-store transfers. A well-designed SKU convention makes your inventory readable by humans, not just machines.

SKU structure: category-brand-attribute-sequence

Effective SKU conventions encode product information in a consistent, hierarchical format:

[Category]-[Brand]-[Attribute]-[Sequence]

Examples:

SKU design rules:

• Keep it under 20 characters. Longer SKUs increase data entry errors and display poorly on labels and reports.
• Use uppercase letters and numbers only. Avoid spaces, special characters, and lowercase letters that create ambiguity.
• Make the category prefix consistent. Create a master list of 3-letter category codes and enforce it across all stores.
• Do not embed price in the SKU. Prices change; SKUs should not.
• Include size or variant in the attribute segment. Two sizes of the same product need different SKUs — different shelf space, different reorder points.

Common mistakes to avoid:

• Using the supplier's part number as your SKU. If you switch suppliers, the SKU becomes meaningless.
• Letting each store create SKUs independently. This makes cross-store transfers and consolidated reporting nearly impossible.
• Starting the sequence at 1 and hoping you will never exceed 999. Plan your numbering for growth.

In bilingual MENA markets, your SKU convention should work in both Arabic and English contexts. Latin-character prefixes are standard even in Arabic-speaking markets because they integrate cleanly with barcode systems and POS databases.

Hardware and setup: scanners, printers, and labels

The best SKU convention and barcode strategy fails if your hardware cannot reliably read and print labels. Here is what to evaluate.

Barcode scanners

Two main categories:

What to look for in a scanner:

• EAN-13 and Code 128 support — Non-negotiable for MENA retail. Some cheap scanners only decode UPC-A reliably.
• Scan speed — A good scanner reads in under 200 milliseconds. Test with your actual product labels, not the demo card in the box.
• Durability — Retail scanners get dropped. Look for a drop rating of at least 1.5 meters onto concrete.
• 2D capability — If you plan to use QR codes for promotions or receipts, you need a 2D imager, not a laser-only scanner.

A reliable mid-range USB scanner at a fixed checkout counter handles most retail scenarios. Save wireless scanners for inventory counting and receiving where mobility matters.

Label printers

Thermal label printers are the standard for retail barcode labels. They use heat to print on coated label stock — no ink cartridges, no toner.

Two thermal printing methods:

• Direct thermal — Heats the label surface directly. Labels fade over months when exposed to heat or sunlight. Good for perishable goods with short shelf life.
• Thermal transfer — Uses a ribbon to transfer ink onto the label. Labels last years. Better for shelf labels and products with long shelf life.

For most stores, a direct thermal printer handles daily needs at a lower operating cost. If you sell products that sit on shelves for months, consider thermal transfer for those labels.

Label material considerations for MENA:

• Heat resistance — In Gulf countries where temperatures exceed 45C, direct thermal labels may darken or become unreadable. Thermal transfer is more reliable in high-heat environments.
• Bilingual labels — If labels include Arabic and English, ensure your printer and design software support RTL rendering. Not all label tools handle this correctly.
• Adhesive quality — Labels on refrigerated or frozen products need cold-environment adhesive that does not peel in condensation.

Integrating barcodes with your POS system

Hardware and labels are the physical layer. The real value is in how your POS uses barcode data to drive operations.

Checkout speed

When a cashier scans a barcode, the POS should retrieve the product name, price, tax rate, and current promotion in under one second. Every product in your store should be scannable — including items you weigh and label in-store. Stores that achieve 100% scan rates see measurable improvements in transaction speed and cashier throughput.

Inventory adjustments and receiving

Barcodes serve more than checkout. A POS with barcode integration should support:

• Receiving — Scan incoming products against purchase orders. The system matches barcodes to expected items and updates counts automatically.
• Cycle counts — Staff scan products on shelves and the system compares scanned quantities to expected inventory.
• Transfers — Scan items out at the source store and in at the destination. The system maintains accurate counts at both locations.
• Returns — Scan the returned item to pull up the original transaction and process the return without manual lookup.

The error rate on barcode scans is approximately 1 in 10,000, compared to roughly 1 in 300 for manual keyboard entry.

Multi-store product consistency

If you operate multiple stores, barcode and SKU consistency across locations is critical. A product scanned at Store A must resolve to the same record at Store B. This requires a centralized product catalog with unique barcodes, consistent pricing rules, and synchronized inventory counts.

A multi-store POS system like Sandooq maintains a single product catalog that all stores reference. When you add a product or update a barcode at headquarters, the change propagates to every location. See how Sandooq handles inventory across multiple stores.

Getting started: a practical implementation checklist

Setting up barcodes and SKUs does not require a massive upfront investment:

Phase 1: Foundation (Week 1-2)

1. Audit your product catalog — how many items already have manufacturer barcodes?
2. Define your SKU naming convention and create a master category code list
3. Assign SKUs to your top 50 products first
4. Purchase a USB barcode scanner and thermal label printer

Phase 2: Product setup (Week 3-4)

1. Enter all products into your POS with barcodes and SKUs
2. Print labels for products that need internal barcodes
3. Test scanning at checkout with your actual products
4. Train cashiers on the scanning workflow

Phase 3: Expansion (Month 2+)

1. Extend barcodes and SKUs to your full catalog
2. Begin using barcode scanning for receiving and inventory counts
3. Review scan failure rates weekly and reprint problematic labels

Watch a demo to see Sandooq in action — including barcode scanning and multi-store inventory sync.

Frequently asked questions

How do I create barcodes for my own products?

For products you sell beyond your own store (wholesale, online), register with GS1 and obtain a company prefix to generate globally unique EAN-13 codes. For products sold only in your store (repackaged goods, prepared food, custom bundles), use the 200-299 prefix range to generate internal EAN-13 codes, or use Code 128 format. Your POS system should let you generate and print these labels directly.

Do I need a barcode scanner for my store?

If you sell more than about 50 distinct products, yes. Manual product lookup creates queues, increases pricing errors, and makes inventory counting impractical. A basic USB scanner costs $30-$50 and pays for itself within days through faster checkout and fewer errors. For specialty shops with 20 items, quick keys on the POS screen may suffice initially, but you will outgrow that approach as you add products.

What is the difference between a barcode and a SKU?

A barcode is the physical, scannable representation — the printed bars or matrix on a product label. A SKU is the logical identifier — the alphanumeric code your business uses to track that product in reports, purchase orders, and inventory. A single product has one SKU but could have multiple barcodes (manufacturer barcode on packaging, internal barcode on your shelf label). The barcode encodes a number; the SKU encodes meaning about category, brand, and attributes.

Which barcode format should I use in the Middle East?

EAN-13 is the standard retail barcode format throughout the MENA region. All major suppliers, distributors, and retail chains in the Gulf and Levant use EAN-13. Your scanners and POS must support EAN-13 as a primary format. For internal products, use EAN-13 with the 200-299 internal prefix or Code 128.

How many products can I manage without a barcode system?

Stores start experiencing significant friction around 50-100 products without barcodes. Cashier lookup time becomes noticeable, inventory counts take too long, and pricing errors increase. Stores with fewer than 50 products may manage with quick keys, but any growth plan should include barcode implementation from the start.

Can I use my phone as a barcode scanner?

Most modern smartphones can scan barcodes via camera, but phone-based scanning is significantly slower and less reliable. A phone scan takes 1-3 seconds including focus time; a dedicated scanner reads in under 200 milliseconds. For occasional inventory checks, a phone may work. For checkout, always use a dedicated scanner.

Trusted by 10,000+ businesses across 25+ countries, Sandooq provides built-in barcode management, multi-store inventory sync, and flexible SKU configuration. Contact our team to discuss your store's needs, or explore pricing plans. Already evaluating POS systems? Read our guide on how to choose the right POS for your retail store.

Authoritative sources

• GS1 — barcode standards (EAN, UPC, GS1-128, GTIN) — the global authority on barcode formats and product identification.
• GS1 — GTIN management standard — guidance on assigning, allocating, and reusing Global Trade Item Numbers.
• GS1 — verified company prefix lookup (GEPIR) — verify that a barcode prefix maps to a real, registered manufacturer.

Related guides

• POS hardware: printers, scanners, and terminals
• Multi-store inventory management
• Demand forecasting for retail: turning POS data into stock decisions