Files pile up
Downloaded slips depend on someone noticing them and printing the right batch.
Packing slips
Print the document when the order reaches the bench.
Generate the same PDF your team already uses, send it as base64, and name the laser or document printer assigned to that location.
PDF to the installed driver
The Station app prints through the computer that already knows the queue and paper setup.
The operational gap
A generated PDF is not a completed warehouse step.
Saving a packing slip to a folder or browser tab still leaves a person responsible for destination, timing, and confirmation.
Locations differ
The order location must resolve to the printer at the bench doing the work.
Labels and slips diverge
Two document types often need two printers but belong to the same shipment.
The RocketPrint path
Treat the packing slip as another job in the order workflow.
Use the same location mapping and lifecycle you use for labels, with a PDF content type and the document-printer ID.
Render the PDF
Generate the packing slip in your backend when the order reaches your chosen state.
Select the document queue
Read the printer ID stored for that warehouse or bench.
Create a PDF job
Send pdf_base64 with a key such as order-1042-packing-slip.
What changes
Labels and documents share one operational trail.
Automatic timing
The workflow event decides when paper appears.
Existing drivers
Use the laser and office printers the station computer already prints to.
Independent retries
Give the slip and label distinct idempotency keys so each stays safe.
One history
Both jobs can be stored against the same order or shipment.
Start with one printer
Make the physical step part of the workflow.
Install RocketPrint Station beside a printer, send one request, and keep the job ID. That is the whole path.