Kitting/assembly label prints with missing UOM — mapping & template fixes
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
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.
| Symptom | Likely cause | Quick 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)
- Remap the UOM text object to
display_uom; add fallback touomthenbase_uom; apply Uppercase/Trim. - Implement kit/pack rules (SET for kits, BOX/CASE for packs; show “{qty} {UOM}”).
- For HTML→PDF, lock label size and DPI; prevent overflow on the UOM span.
- For ZPL, define a UOM field (^FN) and ensure ^FB width is sufficient; pass UOM in the payload.
Note for mixed environments (macOS)
- On AirPrint/IPP drivers, disable scale-to-fit and select the exact roll size to avoid clipping the UOM.
- Prefer vendor drivers or print via middleware that outputs ZPL with explicit UOM variables.
Sources
- GS1 — Barcodes and Application Identifiers
- Zebra — ZPL variable/text formatting
- BarTender — Data sources & transforms (white papers)
Filed under: General Printer Problems
Related articles
- Next.js SSR form prints missing input borders — hydration
- Epic EHR Label Font Mismatch — Why ZPL Profile Push Is the Real Solution
- Fusion 360 drawing prints missing dimensions — export mode and print pipeline checks
- Walmart Marketplace label compressed — enforce 300dpi
- CBP EVUS page prints truncated top — browser fit
- Insurance EOB PDF prints cropped CPT codes — border margin
- Salesforce PDF contract prints misaligned fields — template DPI checks you can do safely
- Premiere frame export prints jagged — TIFF: safe checks before you change settings