Vendor ASN label fields print in wrong order — ZPL mapping & template fixes

Joe B.

Reviewed for technical accuracy

Specialities: Zebra ZPL/EPL, GS1-128/Code128, EDI 856 (ASN), NiceLabel/BarTender/Loftware, WMS/ERP label integration

ASN label fields out of order — fix ZPL ^FN/^FD mapping, data sort, GS1 AI sequence, and template variables

Technician

Hi! We’ll get your Vendor ASN shipping label to print fields in the correct order. To pinpoint the root cause, tell me:
• Which system generates labels — WMS/ERP (e.g., NetSuite, SAP, Blue Yonder) or a design tool like BarTender, NiceLabel, Loftware?
• Printer language and model — Zebra ZPL, ZD/ZT series, or other thermal?
• What’s wrong exactly — Ship To, PO, SSCC, Carton ID, and dates appear in the wrong positions, or the GS1-128 barcode segments are out of sequence?
Field order issues usually come from template mapping or data sort/merge, not the printer itself.

Customer

Labels come from our WMS via a ZPL template. Since a vendor spec update, the PO number and Ship To swapped, and the SSCC (00) barcode is printing above the address block. We push variables as CSV to the print server.

Technician

Thanks — classic ZPL field mapping incorrect scenario. After spec changes, the data file’s column order or field names no longer match the template’s ^FN indexes. A barcode shift can happen when the GS1 Application Identifiers are concatenated in the wrong sequence or a ^FT/^FO position belongs to the wrong field number.
Plan: 1) Freeze the vendor ASN label template. 2) Inspect ZPL ^FN to data mapping. 3) Validate GS1-128 AI order (00, 02, 37, 10, 17…). 4) Test with known-good sample data from the spec. Then deploy presets for all printers.

Customer

We do have a CSV export. The headers changed last month. How do I check which ^FN number feeds each text box in the ZPL?

Technician

Step 1 — Trace ZPL variables
• Open the ZPL in a text editor. Each dynamic field uses ^FNn (n = index) and later receives data with ^FNn^FD{value}^FS or via a download format (^DF + ^FN placeholders).
• Build a quick mapping table: FN → Label on artwork → CSV column. Example: ^FN3 → “PO Number” → PO.
• If you use format strings (^XF), print the expanded ZPL from the driver (Windows “Print to file”) to see final positions (^FT/^FO) for each ^FN.
A mismatch here explains why Vendor ASN label fields print in wrong order.

Customer

I can fix the text boxes, but what about the GS1-128? Our barcode has (00)(10)(17) but the vendor wants (00)(02)(37)(10)(17).

Technician

Step 2 — Correct GS1-128 AI sequence
• In ZPL, a GS1 barcode is typically ^BC/^BY (Code128) or ^B8 with data like ^FD>8 00{SSCC} 02{GTIN} 37{QTY} 10{LOT} 17{EXP} where >8 enables FNC1.
• Ensure parentheses are not printed; the reader expects the AI sequence only, with FNC1 separators on variable-length AIs (10, 21).
• Build/concatenate data in the right order in your middleware (BarTender expression / NiceLabel variable / WMS template). Wrong order = “barcode validated but wrong data”, a frequent vendor compliance deduction.

Customer

We push variables by position. Could the CSV delimiter or line endings cause a shift so fields slide one slot to the left?

Technician

Step 3 — Stabilize the data feed
• Standardize encoding to UTF-8 and line endings to CRLF. A stray comma or quote inside an address can shift positional fields.
• Prefer named variables (JSON/XML) or database bindings over raw positional CSV. In ZPL formats, using ^FN with name tags in your label software avoids order drift.
• If CSV is required: wrap text in quotes, escape inner quotes, and validate with a lint step before printing. Keep a schema version that matches the template revision.

Customer

We’re on Zebra ZT410. Any print settings that affect layout positions? Some labels look slightly shifted vertically.

Technician

Step 4 — Calibrate the printer (so order + positions stay fixed)
• Run media and ribbon calibration; set label length and print width correctly. A bad gap/tooth sensor read shifts ^FT positions.
• DPI in the driver must match the printer (203/300). Wrong DPI rescales coordinates. Use Zebra Setup Utilities to confirm.
• Lock darkness/speed to vendor spec so barcodes remain crisp (helps with GS1 verification).

Customer

We also generate labels in BarTender for another vendor. Can we reuse the same data file without fields jumping?

Technician

Yes — create a template per vendor with a shared named-variable payload. In BarTender/NiceLabel map variables (PO, SSCC, GTIN, QTY) directly to objects. The middleware selects the right template based on vendor code and assembles the GS1 string per spec.
This eliminates the “ASN label fields print in wrong order” when vendors require different layouts or AI sequences.

Customer

After mapping fixes, our sample passes the vendor portal preview. Any final validation before we run production?

Technician

Final checks:
• Print a golden sample and verify each field against the vendor checklist; save the ZPL used.
• Scan the GS1-128 with a verifier/app and confirm the AI sequence and data lengths (SSCC=18 digits).
• Tag the template with a revision and pin the data schema in source control. Roll out via print server/MDM so all stations use the same build. Need help packaging this? Open the chat.

Customer

Perfect — fields print in the right order and the vendor passed our ASN labels. Thanks!

Technician

Summary: When Vendor ASN label fields print in wrong order, align your ZPL ^FN mapping with the data file, correct the GS1 AI sequence in the barcode, standardize the feed (UTF-8, CRLF), and calibrate the printer. Use named variables and a template per vendor to prevent future drift. Need us to review your ZPL? Open the chat.

Quick answer: the accepted fix

Accepted fix when ASN label fields print in wrong order: remap CSV/JSON variables to ZPL ^FN indexes, rebuild the GS1-128 string in the vendor’s required AI sequence, lock DPI & calibration, and publish a versioned template per vendor so field order and barcode data stay consistent.

FAQ

Step-by-step (Windows print server / ZPL)

1. Export one order to CSV/JSON and compare to vendor spec; build a field map against the ZPL ^FN indexes.
2. Correct the GS1-128 build string in middleware (AI order + FNC1); test scan.
3. Confirm printer DPI and calibrate; set media type, print width, and speed.
4. Save a versioned template per vendor; deploy via print server with read-only permissions for operators.

Note for mixed environments (macOS)

1. When printing ZPL via drivers from design tools, ensure the device profile matches printer DPI and label stock.
2. If exporting to PDF first, keep 1:1 scale and avoid “Fit to page” to preserve barcode dimensions.

Sources

• GS1 — Application Identifiers guide
• Zebra — ZPL Command Reference
• BarTender — Variable data & GS1 construction (docs)

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.