Reprocessing a batch after a partial first run can fail on some records with "Nullable object must have a value." The failing records are the ones that already shipped and were not voided. Void every shipment in the batch, then process it once, or build a new batch.

Problem

Processing a batch returns this error on some records while other labels in the same batch print:

Nullable object must have a value

The failing records are the ones that already shipped on an earlier run of the same batch and were not voided.

Cause

When you run a batch again after a partial first run, the records that already shipped are not rebuilt for the new run, so the batch hits missing values on those records and fails. This is a known defect the developers are tracking. The workaround is to not re-run a batch that has a mix of shipped and unshipped records.

Fix

  1. Void every shipment in the batch from all earlier runs, so nothing in the batch is left shipped.
  2. Process the whole batch once, in a single run.
  3. If a shipment shows shipped and will not void, email support@shipstore.com and ask them to clear the stuck records. Do not leave partly shipped records in the batch.
  4. As another option, delete the batch and build a new batch from the source orders, then process it once.
  5. Refresh Shipstore to see the updated batch state before you reprocess.

What you should see

  • The batch processes and prints all records with no "Nullable object must have a value" error.
  • No record in the batch is left shipped-but-not-voided before a re-run.