Transport manifest missing container IDs on print — how to fix fast

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Thermal label printers, Shipping/transport systems, ZPL/EPL/ESC-POS, PDF forms, ERP/WMS/LIMS integrations

Manifest prints without container numbers — fix missing container IDs, template field mapping, PDF/ZPL, orientation & scaling

Technician

Hey! We’ll get your transport manifest to print the container IDs (container numbers / container codes) reliably. A few details help me target the fix:
• What system generates the manifest — ERP/WMS/TMS (SAP, NetSuite, Oracle, Blue Yonder), a carrier portal, or a custom app?
• Are you printing to a laser printer (8.5×11 PDF) or a thermal label printer (4×6 / 4×8, ZPL/EPL)?
• Do IDs appear on screen but vanish on paper, or are the fields blank in the PDF too? Any signs of text clipping, scaling, or portrait/landscape mismatch?

Customer

We export a PDF manifest from our TMS. On screen I can see the Container ID column, but when we print to a Zebra ZT410 and also a regular HP laser, the container numbers are missing. Sometimes the header prints, sometimes it shifts off the page.

Technician

Got it. Missing container numbers on print usually trace back to one of these:
1) Template mapping — the ContainerID field in the manifest report isn’t bound to the data set your TMS outputs (common after an update).
2) Font/encoding — PDF uses a font not installed or embedded; thermal driver substitutes and the text disappears. Also happens with monospace only ZPL.
3) Page size or orientation — printing a Letter/Legal PDF to 4×6 causes auto-scale/crop; right edge with container codes gets truncated.
4) Barcode logic — if the system renders a Code128 barcode for the container number and human-readable text is disabled, you’ll see a blank spot if the barcode font isn’t available.
5) Driver mode — Zebra set to “Use printer fonts” vs “Download as Graphics”, or HP using PCL when the PDF needs PostScript.
We’ll check each quickly and lock it down.

Customer

Where do I check the mapping? We recently changed the TMS report to add a seal number and container weight. After that, the IDs started dropping from printouts.

Technician

Step 1 — Verify report/label template mapping
• Open the manifest template (Crystal Reports / BIRT / Jasper / TMS designer). Confirm the field bound to ContainerID, ContainerNumber, or cntr_no still points to the live data source after your change.
• Make a test run: export the report to CSV/JSON and check the payload includes container numbers for each line.
• If the report draws a barcode for the ID, enable human-readable text below the barcode or render as a PDF font to guarantee visibility even if the barcode can’t load on the printer.

Customer

The data exists in CSV. In the designer, ContainerID is there, but the PDF uses a custom font. Could the Zebra be dropping that font?

Technician

Step 2 — Fix fonts & driver rendering
• In the PDF export settings, embed fonts. Avoid rare fonts; use Helvetica/Arial or render text as graphics.
• Zebra: in driver prefs, set Print Mode → Download as Graphics (or “Use TrueType fonts as graphics”) so the Container ID text isn’t substituted with an unsupported ZPL font.
• For HP/laser: choose Print as Image (Adobe Reader) or PostScript driver to prevent PCL skipping vector text.
• If a Code128 barcode is used, make sure the Code128 barcode font is embedded, or switch to the printer’s native barcode command (ZPL ^BC) with human-readable text on.

Customer

We also try to print the same manifest on 4×6 for the dock. That’s where the right column with container numbers gets cut off. Any layout tips?

Technician

Step 3 — Correct page size/orientation
• Don’t auto-shrink a Letter PDF to 4×6. Instead, create a dedicated 4×6 manifest layout that includes only the required fields (Container ID, seal, weight, stop, BOL).
• In the Zebra driver, set media to the exact size (e.g., 4.00 × 6.00 in), orientation = portrait, and disable “Fit to page.”
• In Chrome/Edge/Adobe: turn off “scale to fit,” set Margins: None, and ensure the printable area doesn’t clip the right column.
• If your TMS can output ZPL directly, map the Container ID to a fixed-width field and test with ^FO/^FB blocks so long IDs wrap rather than disappear.

Customer

Sometimes the manifest shows the ID as a barcode but no text. Drivers are updated. Could the API payload be missing the field on certain jobs?

Technician

Step 4 — Validate API/data and conditional rendering
• Inspect the TMS → report data contract; confirm containerId is populated for all legs (export/import, transload, empty return). Missing values often occur after status transitions.
• Remove conditional visibility rules like “Hide when barcode true” — keep human-readable container number always on.
• If multiple containers are on one shipment, use a grouped sub-report so each Container ID line renders, rather than a single value in the header that may be null.

Customer

We print over VPN from the warehouse. Could spooling or drivers on the server affect this?

Technician

For managed environments:
• Use a Type 4 or vendor PS driver on the print server and mirror the same driver on clients to prevent font substitution.
• Enable “Render print jobs on client computers” when output is PDF-based; this avoids server-side font loss.
• If using label print servers (Loftware/NiceLabel/BarTender), check the variable mapping for ContainerID and confirm the printer is set to the correct DPI (203/300/600) so fields don’t shift off-canvas.

Customer

After embedding fonts and creating a 4×6 layout, the Container IDs finally appear on both the Zebra and the HP. Any final checks?

Technician

Final checks:
• Lock the Container ID field to a safe font size (10–12 pt for laser, 18–24 pt for thermal).
• Keep human-readable text under any barcode. Export PDFs with subset-embedded fonts.
• Version your manifest template and test with long IDs (e.g., MSCU1234567) and multi-container shipments.
• Save printer defaults (media size, orientation, no fit-to-page) in the driver profile for the dock PCs.

Customer

Perfect — the manifest prints correctly and all container numbers are readable on every printer. Thanks!

Technician

Summary: If a transport manifest prints without container IDs, fix template mapping, embed fonts, turn on human-readable text, and match page size/orientation to the target printer (PDF for laser, ZPL for thermal). Adjust driver rendering (Print as Image / Download as Graphics). Need help applying this in your TMS or WMS? Open the chat.

Quick answer: the accepted fix

Accepted fix when a transport manifest is missing container IDs on print: verify report field mapping, embed fonts or print as image, enable human-readable container numbers, and output to a page size that matches your device (Letter for laser, 4×6 for thermal). For Zebra, use Download as Graphics or native ZPL with wrapped fields.

FAQ

Step-by-step (Windows 11)

1. Validate data: export CSV/JSON and confirm ContainerID is populated for all lines.
2. Open the report/label template and re-bind the container number field; keep human-readable text on.
3. Embed fonts in PDF; for Zebra choose Download as Graphics or render via native ZPL.
4. Match media size and orientation; disable auto-fit and clipping.
5. On laser printers, use PostScript or Adobe “Print as Image.”

Note for mixed environments (macOS)

1. In Preview, set Scale = 100% and select the correct paper size; avoid “Scale to Fit.”
2. When using AirPrint for Zebra, ensure the label size matches 4×6; otherwise, the right edge may truncate container numbers.

Sources

• Microsoft — Printing and document rendering guidance
• Zebra — ZPL/driver documentation on fonts & graphics
• Adobe — Print PDF as Image to resolve font/driver issues

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.