What GS1 DataBar Stacked Omnidirectional Composite is
GS1 DataBar Stacked Omnidirectional Composite pairs the 2-row GS1 DataBar Stacked Omnidirectional symbol (covered separately in this catalog) with a linked 2D composite component, so a narrow, roughly square label can still carry supplemental Application Identifier data beyond the GTIN. Confirmed directly: bwipp_databarstackedomnicomposite parses the pipe-delimited payload with its own bwipp_gs1process() call, delegates the linear-component drawing to bwipp_databarstackedomni() (itself a databaromni delegate), and delegates the composite-component drawing to a second, separate internal bwipp_gs1_cc() call.
Generate it now
Enter the linear GTIN payload and a composite-component payload separated by a pipe character, e.g. "(01)00012345678905|(10)ABC123" -- the companion Application Identifier in the composite half must be parenthesized.
Valid input
A pipe character must separate the linear payload from the composite-component payload (bwipp.missingCompositeComponent rejects a missing pipe). The linear half follows GS1 DataBar Stacked Omnidirectional's own rules (a (01)-prefixed 13 or 14-digit GTIN with a valid Mod-10 check digit). The companion Application Identifier in the composite half must be parenthesized -- the same requirement already documented for databaromnicomposite above.
Key options
Supported options include width (a real, working sizing control). Real behavior is genuinely, non-obviously different from its two sibling composites (databaromnicomposite, databartruncatedcomposite): "height" has NO effect at all here across its entire declared range -- confirmed by direct pairwise render comparison, not merely inferred from source -- because this bcid explicitly deletes the caller's height key from its own options Map immediately before its own final render step and replaces it with a value computed purely from its own combined pixel grid, the identical shape already confirmed for the permanent-cohort GS1 DataBar Stacked Composite capability. "width" is the real, working sizing control instead.
Output and printing
Export SVG for vector-precise label artwork or PNG for a quick proof.
Common uses
Small retail packages that need both a narrow, roughly square linear symbol and supplemental Application Identifier data (lot/batch, expiration, or a serial number) on the same label use this composite pairing.
Example
See the live preview above, seeded with a bwip-js-verified valid value.
Size guidance
A fixed "width" changes the overall printed width of the combined symbol; "height" has no effect here (see Key options above).
Troubleshooting
A rejected value usually means either the pipe separator is missing, the linear GTIN's own check digit is wrong, or the composite-component's own companion Application Identifier is missing its parentheses. If a "height" option in your own integration appears to have no effect, that is expected and confirmed for this capability specifically -- use "width" instead.
Related formats
Related formats: the separately-covered plain GS1 DataBar Stacked Omnidirectional generator (no composite component), and GS1 DataBar Omnidirectional Composite / GS1 DataBar Truncated Composite for other DataBar variants paired with a composite component.
FAQ
Why doesn't a "height" option change anything here?
This is a real, confirmed finding specific to this capability: unlike its two sibling composites, this bcid explicitly discards the caller's height value before its own final render step and computes its own from the combined symbol's pixel grid instead. Use "width" to control the printed size.
Why was my companion Application Identifier rejected?
The companion AI in the composite half must be parenthesized -- e.g. "(10)ABC123", not "10ABC123".