Databar Stacked Generator

What is DataBar Stacked?

GS1 DataBar Stacked takes the same GTIN-only data as DataBar Omnidirectional and folds it into two rows instead of one continuous line, so the resulting symbol is much narrower but taller. It encodes a GTIN through Application Identifier (01), the same as (01)09521234543213, but where DataBar Omni is a wide, flat symbol, DataBar Stacked squeezes onto labels where width is the scarce resource, not height.

How stacking changes the symbol — and the tradeoff

The top row of DataBar Stacked carries the left half of the encoded GTIN data, and the bottom row carries the right half, connected by a finder pattern that lets a scanner reassemble the two halves into one GTIN. This is the same underlying RSS-14 data structure as DataBar Omni, just physically rearranged.

The tradeoff is scan direction: because the data is split across two vertically stacked rows rather than laid out along a single sweep line, DataBar Stacked is not built for full omnidirectional sweep-scanning at a busy retail checkout the way DataBar Omni is. It's intended more for handheld or fixed-position scanning where an operator can aim carefully, rather than for high-throughput lanes where a cashier drags every item across a scanner in an unpredictable direction. If a label needs to stay narrow AND remain reliably omnidirectional at POS, DataBar Stacked Omni is the better fit — it adds height specifically to preserve full-direction scanning, which plain DataBar Stacked does not guarantee.

Technical specifications

DataBar Stacked encodes GS1 Application Identifier (01) with a 14-digit GTIN split across two rows, standardized under ISO/IEC 24724 alongside the rest of the GS1 DataBar family. Total data capacity matches DataBar Omni exactly — it's the same GTIN-only payload, just rearranged into a taller, narrower physical footprint with a two-row separator/finder pattern instead of a single continuous guard bar. GS1 General Specifications define minimum quiet zone and row-separation requirements for the stacked layout, since cropping either can prevent the scanner from reassembling the two halves. As with DataBar Omni, there's no room for supplementary Application Identifiers in this symbol.

Where DataBar Stacked is used

DataBar Stacked shows up on narrow packaging where a wide DataBar Omni symbol simply won't fit across the label — small cosmetic tubes, narrow jewelry tags, compact electronics accessories, and specialty pharmacy or supplement packaging with a tall, thin label area. It's common in scenarios where a stockroom or pharmacy worker scans items one at a time with a handheld imager rather than sweeping items past a fixed lane scanner, since that use case tolerates the more deliberate aiming that a stacked, non-omnidirectional symbol requires.

How to create a DataBar Stacked barcode in Barcode Mint

Choose DataBar Stacked from the GS1 DataBar group in the symbology list, then enter the GTIN using AI syntax, such as (01)09521234543213). Barcode Mint checks the digit sequence and lays out the two-row symbol automatically.

• Adjust module width and row height independently to fit a narrow, tall label footprint
• Set foreground/background colors while preserving scan contrast
• Fine-tune the quiet zone margin around the stacked symbol
• Export to PNG or SVG, or copy the barcode for a label template
• Bulk-generate from a CSV of GTINs into a ZIP or print-ready PDF
• Use the REST API for automated generation: /barcode?type=databarstacked&data=(01)09521234543213

Print and scan best practices

Because DataBar Stacked is typically read by a handheld or fixed scanner rather than a sweep lane, make sure whatever scanning hardware you're deploying is confirmed to support DataBar symbologies before printing a large label run. Keep the gap between the two rows and the quiet zone margin intact — cropping either will break the finder pattern the scanner relies on to stitch the two halves back into one GTIN. Print at a resolution that keeps the narrowest bar elements crisp, since a blurred module in either row can corrupt the whole decode.

When to upgrade to DataBar Stacked Omni instead

The single most common mistake in choosing DataBar Stacked is assuming it will work at a standard retail checkout lane simply because it's part of the DataBar family. It's worth double-checking, early in a labeling project, exactly how the item will be scanned in production: if there's any chance the product ends up at a self-checkout kiosk or a manned lane where a cashier sweeps items past the scanner at an unpredictable angle, DataBar Stacked Omni is almost certainly the safer choice even though it requires slightly more vertical space. Plain DataBar Stacked is best reserved for scenarios you can control — a warehouse pick station, a pharmacy counter, or a back-office relabeling process — where an operator can take the extra half-second to aim the scanner deliberately.

If you're unsure which scanning environment your product will end up in, it's generally cheaper to design the label around DataBar Stacked Omni from the start than to discover a scanning failure rate problem after a large print run has already shipped to retail partners.

Common uses

• Narrow cosmetic tubes and compact packaging
• Jewelry tags too tall-and-thin for a wide DataBar Omni symbol
• Pharmacy and supplement packaging scanned by handheld imagers
• Small electronics accessories with limited label width
• Stockroom items scanned one at a time rather than swept through a lane
• Any small package needing a full GTIN in a narrow vertical footprint

Frequently asked questions

Related barcode types

Browse all 106 barcode & QR types →