Hi! We can fix the Oracle E-Business barcode smears problem by checking two things that cause 90% of cases: the barcode module width (X-dimension / narrow bar width) and unintended scaling in the BI Publisher → PDF → printer path.
Quick details so we don’t guess:
• Are you printing from Oracle EBS concurrent program to PDF output (BI Publisher/XML Publisher), or Oracle Reports (.rdf/.rdf → PDF)?
• Which barcode symbology: Code 128, Code 39, EAN/UPC, or 2D (DataMatrix/QR)?
• Where does the smear happen: the barcode looks OK on-screen but smears on paper, or it already looks “fat/blurred” inside the generated PDF?
• Printer type: thermal label printer (Zebra/ZPL), laser, or inkjet? Do you know the DPI (203/300/600) and whether it’s direct thermal or thermal transfer?
• In Acrobat/print dialog, is anyone using Fit to page, Shrink to printable area, or any scaling other than 100%?
Once I have that, I’ll show you a step-by-step path to set a stable X-dimension, keep the barcode’s quiet zone intact, and prevent bar “bleeding”/smudging that breaks scanners.
Customer
We’re on Oracle E-Business Suite R12 and printing shipping labels from a concurrent program. It’s BI Publisher: data model + RTF template, output is PDF. Barcodes are Code 128. In the PDF preview they look “kind of bold”, but on the printed label the bars look smeared/too thick and the scanner struggles. Printer is a Zebra thermal transfer at 203 dpi. People print from Acrobat and I’m pretty sure some users have “Fit” enabled sometimes.
Perfect — that combination (BI Publisher PDF + Code 128 + 203 dpi thermal) is exactly where module width and PDF scaling can quietly wreck barcode quality.
Here’s what’s usually happening:
• Your barcode has a target X-dimension (module width / narrow bar width). If it’s too small for 203 dpi (or too dense for the label stock), the thermal dots “merge” and the bars look fat or smeared (often called print gain/bleed).
• If Acrobat prints at anything other than 100% (Fit/Shrink), it changes the exact bar width by fractions of a millimeter. That tiny change can push the barcode outside the acceptable range, especially for dense Code 128 symbols.
• On the printer side, high darkness/heat and fast print speed amplify smearing on thermal transfer (ribbon + media mismatch can make it worse).
The fix is: lock the PDF print scale to Actual size (100%), set a safer module width for 203 dpi, and then fine-tune darkness/speed so bars stay crisp instead of bleeding.
Customer
How do we “set module width” in Oracle EBS/BI Publisher? We’re using a barcode font in the RTF template (not an image). We basically pick the barcode font and set font size. Also: if the label is 4×6, some users pick “Fit” because otherwise it doesn’t fill the label preview.
Got it. With font-based barcodes, your “module width” is controlled indirectly by a mix of font type + point size + printer DPI + any scaling. That’s why “Fit” is so dangerous — it changes the effective X-dimension even if the template never changed.
Step 1 — Force 100% scaling (this alone often fixes smearing)
On every workstation that prints these labels from Acrobat/Reader:
1) Print → Page Sizing & Handling: select Actual size (or “100%”).
2) Disable Fit, Shrink oversized pages, and anything that “auto rotates/centers” if it changes scaling.
3) If your Zebra driver has an “Apply scaling” option, set it to None / 100%.
Step 2 — Make the PDF page size match the label size
In BI Publisher, ensure the template/page setup is truly 4×6 (or whatever your label is) so users don’t feel forced to use “Fit.” When the PDF page equals the physical label, “Actual size” prints correctly and consistently.
After those two steps, we’ll adjust the barcode density (effective X-dimension) by choosing a safer barcode font size for 203 dpi so the bars aren’t packed too tightly.
Customer
I tried printing at 100% and it’s already better — the bars aren’t as “blobby”. But some labels still look a bit thick, and scanning is inconsistent if the printer runs fast. We’re printing high volume. Is there a good rule for Code 128 size at 203 dpi? Also, could printer settings like darkness cause the smears even if the PDF is correct?
Yes — on thermal printers, darkness (heat) and speed can absolutely turn a “barely OK” barcode into a smeared one, especially at 203 dpi with dense Code 128 data.
Think of it like this: Code 128 can get dense quickly (lots of characters = lots of bars). If your effective module width is small, any extra heat makes the black bars spread into the white spaces. That reduces contrast/modulation and scanners struggle — even when the PDF looks fine.
Step 3 — Stabilize the printer’s print width + heat/speed
On Zebra/ZPL devices, two practical levers are:
• Print Width / label width in dots (prevents clipping and “compressed” output). In ZPL, that’s commonly the ^PW setting for print width, and it should match the label’s printable width in dots.
• Darkness (heat). In ZPL, a common control is ~SD (set darkness). Too high = thicker bars and smearing; too low = faint barcode. You want the lowest darkness that still gives solid bars.
Step 4 — Slow down slightly for barcode-heavy labels
If you’re running very fast IPS, drop speed one notch and re-test. This often improves edge sharpness and reduces smear/bleed on thermal transfer when the ribbon/media need more time to transfer cleanly.
We’ll keep this simple: once we pick a safer barcode size (module width), you’ll be able to run faster without the “random smear” days.
Customer
OK. But I’m still stuck on the Oracle side: we use a barcode font in the RTF. If we change font size, it changes the barcode width and sometimes it doesn’t fit the label. Is there a better way in BI Publisher to control X-dimension/module width more directly? Also, could the barcode be getting “stretched” by the template cell width?
You’re asking the right question. In BI Publisher/RTF, barcodes can get “messed with” in two common ways: layout stretching and font rendering/resolution mismatch.
Step 5 — Stop layout stretching in the RTF
In the RTF template, make sure the barcode field is not being forced to “fill” a cell:
• Avoid justification that stretches character spacing.
• Don’t put the barcode in a table cell that auto-resizes and then gets scaled when the PDF is produced.
• Keep the barcode in a container that preserves its natural width; let the label layout wrap other fields instead of squeezing the barcode.
Step 6 — Prefer a barcode method that lets you set module width
If you’re using a 3rd-party barcode solution (common in Oracle EBS + BI Publisher), many support an explicit X-dimension / module width parameter instead of “guessing” via point size. That gives you stable results across printers and PDFs, and is exactly what you want for high-volume labels.
Even if you stay with fonts, we can still tune it: choose a barcode font variant intended for your DPI, then set a point size that yields a safer narrow bar width. After that, we lock printing to 100% and tune heat/speed so it doesn’t smear.
Customer
This is making sense. Another clue: when we print the same PDF to a laser printer, it scans more reliably. On the Zebra, the problem is worse on some rolls of labels than others. We use thermal transfer with wax ribbon. Could ribbon/media be part of the smears? Also, do we need to clean/calibrate the printer?
100% — that’s a classic thermal transfer reality: the same barcode can be “perfect” on laser but smear on thermal if the ribbon/media combination and heat aren’t matched.
Step 7 — Quick thermal transfer checklist (smears & bleed)
1) Clean the printhead (adhesive residue makes edges fuzzy and causes streaking). Use the proper cleaning pen/alcohol swab and let it dry.
2) Check ribbon type: wax ribbons smear more easily on some label stocks; wax/resin or resin can improve edge definition if your label material needs it.
3) Calibrate after changing media/rolls so the printer is correctly tracking label gaps/black marks and isn’t “micro shifting” the print.
4) Reduce darkness until the bars are solid but not glossy/overburned; then adjust speed as needed.
When you said “worse on some rolls,” that strongly points to a substrate/ribbon/heat interaction. We can still keep scanning reliable by using a slightly larger module width and keeping the bars crisp (not overcooked).
Customer
After cleaning the printhead and lowering darkness a bit, the barcode edges look sharper. Scanning improved, but our longest barcodes (lots of characters) still get dense and sometimes fail. Is that because the X-dimension is too small? Can we “widen” the bars without making the label layout explode?
Exactly — long Code 128 strings can become high density, and at 203 dpi the “safe” module width window is tighter. If the barcode gets too dense, the narrow bars and spaces approach the printer’s dot limit and any print gain makes bars merge.
Here are practical ways to widen the effective module width without wrecking your label layout:
A) Reduce encoded length (when possible)
• If you can encode an internal ID and print human-readable text separately, do it. Fewer characters = less density = thicker, safer bars.
• If your process allows, use a shorter key (or encode only what scanners truly need).
B) Make the barcode area wider (not taller)
• Give the barcode more horizontal space on the label so you can increase font size/module width while keeping it on one line and preserving the quiet zone.
C) Use a barcode generator/component that supports X-dimension
• Many BI Publisher barcode solutions let you explicitly set module width. That’s the cleanest way to control density without trial-and-error point sizes.
If you want, paste one example of the longest data you encode (mask sensitive parts) and I’ll suggest the most scanner-friendly way to keep Code 128 readable at 203 dpi.
Customer
Good idea. Our longest strings are basically shipment number + location + some extra flags, so it can get pretty long. Another thing: a few workstations use different Zebra drivers, and some users print through a print server. Could driver differences affect smearing or module width too?
Yes — driver and print-path differences can change what the printer receives: true barcode commands vs rasterized graphics, different dithering, and even subtle scaling. That can absolutely impact bar width consistency and smearing.
Step 8 — Standardize the print path (huge for consistent X-dimension)
• Make sure everyone uses the same driver type and the same DPI setting (203 vs 300 mismatches are a silent killer).
• If you’re sending ZPL directly, keep it consistent. If you’re printing PDFs via driver rasterization, ensure everyone uses the same “print as image”/rendering options (ideally avoid mixed settings).
• Verify the label size and print width settings match across workstations and the print server queue so the output isn’t being scaled or clipped.
When different users see different results from the same PDF, it’s almost always: (1) scaling not 100%, (2) different DPI/driver render behavior, or (3) different darkness/speed profiles on the printer/queue.
Customer
After forcing 100% printing, cleaning the head, lowering darkness, and standardizing the driver, the smearing is mostly gone. The remaining failures are just on the super-long barcodes, which we can shorten or give more space. Can you summarize the “best fix” so we can document it for the team?
Absolutely. Here’s the clean, repeatable recipe to stop
Oracle E-Business barcode smears and keep the
module width (X-dimension) stable on thermal printers:
1) Lock print scaling: always print BI Publisher PDFs at
Actual size / 100% (no Fit/Shrink). Make the PDF page size match the label so users don’t “fix” it with scaling.
2) Prevent template stretching: in the RTF layout, don’t let table cells/justification stretch the barcode field; preserve natural width and quiet zone.
3) Make X-dimension safer: pick a barcode font/size (or a barcode component) that yields a readable module width for
203 dpi, especially for long Code 128 strings.
4) Tune the printer: clean the printhead, calibrate after media changes, reduce
darkness/heat until bars are solid but not bleeding, and slow down slightly if needed for barcode-heavy labels.
5) Standardize drivers: same DPI, same driver, same queue settings across workstations/print server so output isn’t silently re-rendered or scaled.
If you want,
start a chat and I can help you pick a target X-dimension and a “safe” barcode size for your exact label and Zebra model so scanning stays reliable even at high volume.
Why Oracle E-Business barcodes smear: module width, scaling, and thermal “print gain”
When a barcode smears, scanners usually fail because the bars and spaces no longer match the intended module width (also called X-dimension or narrow bar width). In Oracle E-Business Suite, the most common trigger is the BI Publisher RTF → PDF output being printed with any scaling other than 100%. Even small scaling changes can alter bar widths enough to break scan reliability, especially with dense Code 128 data.
On thermal transfer printers (Zebra/ZPL), barcode “smearing” can also be caused by excessive darkness/heat, too high print speed, a dirty printhead, or a ribbon/media mismatch. Those conditions create print gain where bars expand into the white spaces, effectively shrinking the quiet zone and reducing contrast. The best results come from stabilizing the output size first (no scaling), then selecting a safer X-dimension for your 203/300 dpi device, and finally tuning printer settings.
How to confirm it’s an X-dimension/module width problem (not “random” printing)
A quick way to isolate the cause is to compare the barcode at three stages: (1) inside the BI Publisher PDF preview, (2) printed at 100% from one “known good” workstation, and (3) printed from a workstation that produces smeared output. If the PDF already looks overly bold or compressed, the issue is likely template layout, font choice, or barcode density (too small X-dimension) at your target DPI.
If the PDF looks crisp but the printed label smears, focus on the thermal printer: clean the printhead, calibrate, reduce darkness, and slow print speed slightly. Also ensure the printer driver/queue is consistent (same DPI, label size, and no scaling). If only one workstation has the issue, it’s almost always a driver/profile mismatch or Acrobat scaling difference.
Oracle E-Business barcode smears — quick troubleshooting tips
Lock scaling at 100%, protect the X-dimension, and tune thermal darkness/speed for crisp edges.
Fast path: make the BI Publisher PDF page size match the label and print at Actual size (100%) only. In the RTF template, avoid any layout that stretches the barcode field. For thermal printers, clean the printhead, calibrate after media changes, then lower darkness/heat until bars are solid but not bleeding, and reduce speed if bar edges look fuzzy. If long Code 128 strings are too dense at 203 dpi, shorten the encoded data or allocate more horizontal space so you can increase the effective module width (X-dimension).
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your Oracle EBS output method, barcode symbology, and printer model, please consult a verified expert on Whizz-Tech before changing templates or printer profiles.
Why do my Oracle E-Business barcodes smear only when printed, not on screen?
If the barcode looks OK in the BI Publisher PDF preview but smears on the label, the issue is usually the thermal printer: excessive darkness/heat, high speed, a dirty printhead, or a ribbon/media mismatch causing print gain (bars spread into spaces). Also verify printing is at 100% — even slight scaling changes can alter the effective X-dimension and reduce scan reliability.
What is module width (X-dimension) and why does it matter for smearing?
Module width, often called X-dimension, is the width of the smallest bar/space (or module) that makes up a barcode. If the X-dimension is too small for your printer’s DPI (common at 203 dpi with dense Code 128), the printed dots can merge and the barcode looks bold, blurry, or smeared. Selecting a barcode size/solution that yields a safer X-dimension and keeping printing at 100% helps prevent smearing and scanning failures.
How do I stop Acrobat or the printer driver from changing my barcode size?
Print BI Publisher PDFs using Actual size / 100% and disable Fit/Shrink scaling. Ensure the PDF page size matches the physical label so users don’t “fix” it with scaling. Standardize the Zebra driver and DPI across workstations and print servers, and confirm label size/print width settings are identical in the queue/profile.
When should I change the BI Publisher template versus the printer settings?
If the barcode already looks overly bold, compressed, or uneven inside the generated PDF, start with the RTF template/layout (avoid stretching) and the barcode method (font/component) to set a stable module width. If the PDF looks crisp but the printed barcode smears, focus on the printer: clean the printhead, calibrate, reduce darkness, adjust speed, and verify ribbon/media compatibility.