Summary: Reference 1 can drop off a label for two reasons: the carrier accepts only a few reference fields, so filling Reference 2, 3, and 4 pushes Reference 1 out; or a rule that sets Reference 1 from another field blanks it on batch orders. Use fewer reference fields, and add a check so the rule skips batches.

Problem

Reference 1 that you entered on a shipment, or mapped on a batch import, does not show on the label. On batch imports, Reference 1 loads and then goes blank.

Cause

Two causes. First, the carrier accepts only a limited number of reference fields, so when Reference 2, 3, and 4 are all filled, Reference 1 is dropped. Second, a rule that fills Reference 1 from another field (for example, Department) on the After Shipment Loads event overwrites Reference 1 with nothing on batch orders, because those orders have no value in the source field.

Fix

  1. If Reference 1 drops when several reference fields are set, remove Reference 2, 3, or 4 so the carrier keeps Reference 1.
  2. If Reference 1 goes blank only on batch imports, open the profile rule that sets Reference 1 from another field.
  3. Add a check so the rule does not run for batches (for example, Shipment is Batch Processed set to Not Active), or limit the rule to the correct order source.
  4. Apply the same check to that rule on every profile that shows the problem.
  5. Run a test batch and confirm Reference 1 stays after import.

What you should see

A batch import keeps Reference 1, and a label with fewer reference fields than the carrier's limit prints Reference 1.

Related articles

  • A suite or building number in Address 3 does not print on the label