When a large batch stops printing partway and the print queue shows nothing left, the jobs are being lost between the server and the printer, not by Shipstore.

Problem

During a large batch, the Zebra printer stops midway with no error and the queue is empty. Smaller batches help only a little, and new printer hardware does not fix it.

Cause

The labels are created correctly in Shipstore. The loss happens after that, on the print path. When the Zebra is reached over a remote-desktop (RDP) or network connection, the job crosses extra layers, and a brief delay or drop can silently remove jobs from the queue. That is why new hardware does not help.

Fix

  1. For reliable large batches, install the Merchant App on a local workstation with the Zebra connected directly by USB. This skips the remote-desktop path. Local stations routinely print 600-label batches this way.
  2. If a local connection is not possible, keep batches at about 300 labels or fewer on the remote-desktop setup.

Good to know

Shipstore cannot reprint only the labels that failed in the middle of a batch. Once a batch is sent, it cannot tell which labels physically printed, so a reprint covers the whole batch or is done one shipment at a time.

What you should see

With the Zebra connected locally by USB, large batches finish without the printer going idle.