Printer troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: ERP/WMS label printing, Zebra ZPL, BarTender, NiceLabel, GS1-128, Data Matrix, Windows/macOS print

UOM not printing on kitting/assembly labels — missing unit of measure, field mapping, data source, GS1 text

Technician avatar Technician
Hey! We’ll fix your kitting/assembly label missing UOM so the Unit of Measure prints (EA, PCS, BOX, SET, KIT). A few checks to target the issue:
• Which label platform do you use — BarTender, NiceLabel/Loftware, ZebraDesigner, or a custom HTML→PDF template?
• Where does UOM come from — item master in ERP/WMS (SAP/Oracle/NetSuite/Microsoft), BOM, or a JSON/CSV payload?
• Should the label show display UOM (e.g., SET), base UOM (EA), or a pack UOM (INNER/CASE) depending on kit qty?
Customer
We build kits from components. Labels are designed in BarTender and triggered by our WMS. The quantity prints, but the UOM field is blank on some labels. The JSON has qty and uom for most items; for kits it sometimes sends only base_uom.
Technician avatar Technician
Understood. Missing UOM on kitting/assembly labels usually comes from one of these:
1) The data source uses a different field name (unit_of_measure, uom_code, display_uom) than the template token expects.
2) Conditional logic hides UOM when quantity = 1 or when kit flag is true.
3) The ERP sends base UOM (EA) but your template references pack/inventory UOM (BOX/CASE).
4) In ZPL templates the variable is referenced with ^FN/^FD incorrectly, or the data filter trims uppercase.
5) GS1 text element is linked to the barcode object, not the text field, so when the barcode is optional, the Human Readable UOM disappears too.
Customer
The field in WMS is display_uom. Our BarTender text object is bound to UOM (uppercase). Maybe that’s it. How do we fix and keep it consistent?
Technician avatar Technician
Step 1 — Map fields with a safe fallback
• In BarTender, open the data source for the UOM text object → set it to display_uom.
• Add a transform: Uppercase and Trim to normalize “ea”, “Ea”, etc.
• Configure a fallback expression: if display_uom is empty → use uom; if still empty → use base_uom or static “EA”.
• If ZPL: ensure the variable name matches your print engine input and that the ^FB box width accommodates long UOM like “INNER PACK”.
Customer
Some kits require “SET” on the label even though the base UOM is EA. Can we calculate UOM from quantity or BOM?
Technician avatar Technician
Step 2 — Apply UOM business rules
• Add a conditional: if is_kit = true or qty > 1 → UOM = “SET”, otherwise use the provided UOM.
• For case/inner packs, map pack_size and pack_uom so “12 PCS / BOX” renders as “12 PCS (BOX)”.
• In GS1 Human Readable line, concatenate: {qty} {uom} — e.g., “5 SET”. Keep the barcode AI data separate from display text.
Customer
Our labels also print from a web app (HTML→PDF). There the UOM sometimes wraps off the edge or disappears.
Technician avatar Technician
Step 3 — Fix HTML/PDF rendering
• Use a fixed label size (e.g., 4×6 in) and disable auto-scaling. Set DPI to 203/300 to match the printer.
• Prevent overflow: apply white-space: nowrap to the UOM span and adequate padding so “INNER CARTON” doesn’t clip.
• Ensure your merge tokens use the same key (display_uom) and are not inside a hidden conditional block for kits.
Customer
We also print via Zebra ZPL for some lines. How do we inject UOM there reliably?
Technician avatar Technician
Step 4 — ZPL with variables
• Define a field number for UOM (^FN20) and a text object (^A0N,28,28) with sufficient width (^FB).
• Send ^FD{display_uom}^FS from your middleware; if empty, substitute in the payload before spooling.
• Pair with quantity: ^FD{qty} {display_uom}^FS for Human Readable. Keep barcode data (e.g., GS1-128) independent.
Customer
Good. We also need UOM on packing slip and pallet labels. Any consistency tips across documents?
Technician avatar Technician
Step 5 — Governance & consistency
• Centralize the UOM dictionary (EA, PCS, SET, BOX, CASE, PALLET). Use one API field name across labels, slips, ASN/EDI.
• Version your label templates and store rules in source control; log print parameters (size, DPI) per release.
• Add a pre-flight check in middleware: if UOM missing → warn and default to base UOM with an audit note.
Customer
After mapping to display_uom with fallback and concatenating qty+UOM, everything prints. Anything else to lock it in?
Technician avatar Technician
Final checks:
• Add a test dataset with kits, components, cases, and pallets to validate UOM rules (SET vs EA vs BOX).
• Lock fonts/sizes so UOM is readable; avoid auto-shrink that hides text.
• For audits, print the UOM in the GS1 Human Readable line next to quantity and keep the same wording across all label families.
Customer
Perfect — the UOM now prints on every kitting/assembly label and matches our WMS. Thanks!
Technician avatar Technician
Summary: To fix kitting/assembly label prints with missing UOM, align template field mapping with your data (display_uom/uom/base_uom), add fallback logic, apply kit/pack business rules, and normalize output in BarTender/NiceLabel or ZPL. For web/PDF labels, lock size/DPI and prevent overflow. Need help wiring the rules? Open the chat.

Quick answer: the accepted fix

Accepted fix when a kitting/assembly label shows missing UOM: remap the text object to display_uom, add a fallback to uom then base_uom, normalize to uppercase, and concatenate {qty} {UOM}. Apply rules for kits (SET) and packs (BOX/CASE). For ZPL/HTML→PDF, lock label size/DPI and prevent overflow.


Why kitting/assembly labels print without a UOM

Typical causes: wrong data mapping, different UOM code names between ERP/WMS and template, conditional visibility, JSON keys missing for kits, or ZPL variable misreferences. Web templates may clip UOM due to scaling or overflow. Standardize on a single field and enforce fallback logic.

How to verify the fix

Create test cases: 1×EA, 5×SET (kit), 12×PCS in BOX, PALLET with cases. Print from BarTender/NiceLabel and via ZPL/HTML→PDF. Confirm UOM matches the pick list and packing slip. If any label still drops UOM, inspect the payload and template logs to see which field was used.

UOM missing — quick troubleshooting tips

Most issues come from mismatched fields or conditionals in the label template.

Quick path: map display_uom → add fallback → uppercase/trim → concatenate qty+UOM → enforce kit/pack rules → lock label size/DPI. Keep GS1 Human Readable consistent across BarTender, NiceLabel, and ZPL templates.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.


Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.

Expert will respond in minutes

We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.

Save time & money

No scheduling hassles or expensive consults. Membership can save you significant time and money each month.

FAQ

Why does my kitting/assembly label show a blank UOM?

The template likely points to the wrong field name or a conditional hides UOM for kits. Standardize on display_uom, add fallbacks to uom/base_uom, and normalize casing.

How do I enforce “SET” for kits and “BOX/CASE” for packs?

Add business rules: if is_kit or qty>1 → SET; if pack_size present → show “{pack_size} PCS (BOX/CASE)”. Keep barcode data separate from Human Readable text.

Can ZPL templates drop UOM?

Yes—if the ^FN index or payload key doesn’t match, or the ^FB width clips long values. Map the correct field, expand the text box, and send uppercase values.

Why does UOM print on laser/PDF but not on Zebra?

Class drivers or scaling may clip text on thermal labels. Lock label size/DPI, prevent overflow, or print via native ZPL with explicit UOM variables.

Common UOM problems and quick fixes
SymptomLikely causeQuick fix
UOM field blank Wrong field name; empty data Map to display_uom with fallback to uom/base_uom
UOM inconsistent for kits No business rules If is_kit or qty>1 → show SET; keep EA for components
UOM clipped on label Overflow/scale to fit Lock label size/DPI; white-space:nowrap; widen text box
Thermal prints differ from PDF Class driver/ZPL variable mismatch Use vendor driver or ZPL variables (^FN/^FD) with correct width

Step-by-step (restore UOM on labels)

  1. Remap the UOM text object to display_uom; add fallback to uom then base_uom; apply Uppercase/Trim.
  2. Implement kit/pack rules (SET for kits, BOX/CASE for packs; show “{qty} {UOM}”).
  3. For HTML→PDF, lock label size and DPI; prevent overflow on the UOM span.
  4. For ZPL, define a UOM field (^FN) and ensure ^FB width is sufficient; pass UOM in the payload.

Note for mixed environments (macOS)

  1. On AirPrint/IPP drivers, disable scale-to-fit and select the exact roll size to avoid clipping the UOM.
  2. Prefer vendor drivers or print via middleware that outputs ZPL with explicit UOM variables.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant