Skip to content

Getting printing working

Printing configuration consists of four consecutive stages: defining the available devices, specifying the material each of them is loaded with, assigning jobs to particular devices, and defining the events that start a print without any further prompt. Each stage has its own screen. A shop that stops after the first stage ends up with a printer that no job ever reaches.

This page goes through the whole chain in an order that ends with the document being printed correctly.

A printer that can already be printed to is required. Stockly sends jobs and does not install drivers. A device reachable from the shop server, from the browser, or from a small local service is sufficient.

A packing station is required if the bench is to own its printer. Jobs are resolved to the station the operator is standing at before any other assignment is considered. → Elements

Stockly → Operations → Printing → PrintersAdd printer. The wizard asks how the data reaches the device: the shop server sends it directly to a network port, the browser prints it, a small program at the station fetches the jobs, or a PDF is sent over IPP to an office printer.

Print test label places a real job in the queue, which tests the whole path end to end.

Stockly → Operations → Printing → Stock typesAdd stock type. A stock type describes the material a device is loaded with — A4 paper, a 100 × 150 mm label — and prevents a pick list from being sent to the label printer standing at the same bench.

Set it on the printer in the Stock type field. A device left on Any remains available for every job that does not name a stock type.

Stockly → Operations → Printing → Default printersAdd default. A row here names the device for a given operator, packing station or warehouse; the most specific row that fits the job wins, and two equally specific rows resolve to no device at all.

The module works through five possibilities in turn and stops at the first one that fits the job:

  1. the device named explicitly by the screen that requested the print;
  2. the configured defaults described above;
  3. the device standing at the operator’s packing station;
  4. the printer assigned to the operator on their user page;
  5. the only device in the shop that can serve the job.

Two screens are available, each covering a different origin of the document.

ScreenUse it when
Automatic printingThe document belongs to a moment of work, such as a pick list when a wave is planned or a packing slip when an operation finishes
Document rulesA shipping module stores its label as a Shopware document instead of handing it over directly

Both start empty and report it: Nothing prints by itself yet and No document rules.

Stockly → Operations → Printing → Print queue lists every job the module received, together with its origin and its outcome. A job that reached paper leaves a record; a job that did not carries its reason.

Start the diagnosis from the queue, not from the printer. A job that remains on Sending is released by the module itself: after the number of minutes set in Release claimed jobs after (minutes), five by default, it returns to Waiting and is handed out again, so waiting is the correct response rather than retrying. A failed job names its cause, and the most common one is a stock type mismatch: a label printer uses its own language and does not accept a PDF.

  • Printers — every connection type and how to calibrate a label.
  • Print queue — what each state means and how to clear a stuck job.
  • Automatic printing — the full list of moments a rule can wait for.