Print System

A job printed but wasn't billed to the right member

Member self-service print identity is carried by which print queue the job came through — each member has their own dedicated queue on the print server. If a job lands in the wrong place (or falls through to the generic front-desk queue), it gets billed as a walk-in guest job instead of to that member's account. Check that the member's install kit is actually pointed at their own queue, not a shared one.

Nothing prints at all

The print system runs through a real Raspberry Pi at the physical location talking to CUPS and the actual printer. If nothing prints:

1. Confirm the Pi is powered on and reachable on the local network.
2. Confirm the printer itself is on and not out of paper/toner — CUPS will still accept a job and report success even if the physical printer can't actually produce it.
3. Confirm the Pi is running current agent code — an on-site update requires physically pushing new code to the Pi; a code fix merged elsewhere doesn't take effect at the printer until that happens.

Metering looks wrong (page count or color detection)

Some printer drivers force a raster conversion that can throw off color-vs-black-and-white detection during metering. If billed page/color counts look consistently wrong for one specific printer model, that's worth investigating as a driver-level issue, not a logic bug in the billing calculation itself.

Front-desk guest settlement

A print job that can't be attributed to a member's own account becomes a guest job requiring manual staff settlement (cash, check, terminal, bill-to-member, or void) — this is expected behavior for a walk-in with no account, not a failure of the automatic billing path.