Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt

Use this file to discover all available pages before exploring further.

Printing has two layers: the entity PrintNode connector and each user’s printer preferences. The connector makes printers available to Arcus. User preferences decide which printer receives each job.

​
What PrintNode Does

PrintNode connects a browser-based app to physical printers. A PrintNode client runs on a workstation that can see the printer. Arcus sends a print job to PrintNode, and PrintNode forwards it to the client and printer.

  • Label printers: used for carrier labels, usually 4x6 thermal printers.
  • Document printers: used for packing slips, pick lists, invoices, checks, and letter-size documents.
  • Workstation client: must stay signed in and running for direct printing to work.
  • User preferences: let each packing station choose its own default printers.

​
Connect PrintNode To Arcus

  1. Create or open the company’s PrintNode account.
  2. Install the PrintNode client on each workstation that owns printers Arcus should use.
  3. Sign in to the PrintNode client on the workstation.
  4. Confirm the workstation can print to the label and document printers outside Arcus.
  5. Connect the PrintNode API key in Arcus Integrations.
  6. Refresh printing settings and confirm the printers appear.
The client must stay online If the PrintNode client is closed, signed out, offline, or running on a sleeping computer, print jobs may queue or fail even when the printer is selected in Arcus.

​
Review Entity Printing Settings

The entity-level printing settings show connector state, available printers, default behavior, and recent print activity. Admins use this view to confirm that PrintNode is connected before operators rely on direct printing.

Printing settings page showing PrintNode connection, default printing controls, printer options, and recent print jobs
  • Connection state: tells the team whether Arcus can reach PrintNode.
  • Printer list: shows printers returned by the connected PrintNode account.
  • Default behavior: controls printing defaults that affect fulfillment and documents.
  • Recent jobs: helps diagnose submitted, queued, failed, or blocked print jobs.

​
Set User Printer Preferences

Each user should choose their own default label printer and document printer. This is important when two packing stations share one entity but use different physical printers.

Printing preferences with PrintNode connection state, default label printer, default document printer, and auto-print on fulfill
  • Default label printer: receives shipping labels.
  • Default document printer: receives packing slips, invoices, pick lists, and document packets.
  • Auto-print on fulfill: sends configured jobs automatically when fulfillment completes.
  • Manual print fallback: open or download the PDF if no printer is configured.
Name printers by station Printer names like Warehouse Label 1, Front Counter Label, and Office Document are easier to choose than generic system names.

The Fulfillment Station uses the selected or default printer for label and package printing. Pick the printer before printing, then print the active label or use batch actions when multiple packages are ready.

Fulfillment Station with printer selector, Print All, Print Label, Station and History toggle, and package detail
  • Print Label: sends the active package label to the label printer.
  • Print All: prints available package documents in a batch when the station supports it.
  • Package packet: combines package documents when that workflow is available.
  • Packing slip: prints item detail for the package or order.

​
Printer Category Filtering

Some fulfillment stations use printer category assignments. When a selected printer has categories assigned, the station can filter package work to match that printer’s categories. This helps route different product or package types to the right station.

Printer choice can change what work appears If packages disappear after a printer is selected, clear the printer selection or review printer category assignments. The work may be filtered to the printer’s configured categories.

​
Test Printing

  1. Confirm the PrintNode client is running on the workstation.
  2. Confirm the printer is online and can print outside Arcus.
  3. Select default label and document printers in Arcus.
  4. Print a test label or a safe sandbox label from dev.
  5. Print a packing slip or document test.
  6. Review recent jobs if either print does not come out correctly.

​
Common Blocks

  • No printers appear: check PrintNode API key, client login, workstation internet, and whether the client can see the printer.
  • Job queues but does not print: confirm the workstation is awake, client is running, and printer is online.
  • Wrong printer receives the job: update the user’s label or document printer preference.
  • Label prints on letter paper: choose the thermal printer as the label printer and confirm label format.
  • Document prints on label stock: choose a document printer for packing slips, invoices, and packets.
  • Auto-print surprises the team: turn off auto-print on fulfill until the station is tested.
  • Work disappears after picking a printer: review printer category filters.

Shipping Labels

Buy labels, void labels, track shipments, and handle carrier errors.

Fulfillment Station

Operate the station view for picking, packing, and shipping.

Packing and Shipping

Use package suggestions, freight decisions, labels, and tracking.

Shipping and Fulfillment Setup

Configure Shippo, carrier defaults, shipping rules, freight routing, PackPilot, scanners, and PrintNode printing.

Integrations

Connect Stripe, marketplaces, shipping, email, and other services.