LinxyHelp Guides & support

Requesting a print

In short

Where a community allows it, anyone looking at its album can ask for a photograph to be printed. They pick the picture, choose a size and a quantity, and receive a ticket number. The owner sees the request in a queue and either fulfills it or cancels it.

The check that shapes the whole experience is the resolution one. A community can set a minimum print quality, and a photograph that cannot meet it at the requested size is refused at the moment of ordering rather than at the moment of printing. More usefully, the refusal works out the largest size that photograph can manage and offers it — so the guest gets an answer, not just a rejection.

Turning it on, and the two modes

Print requests are off until the community owner enables them. Once on, there is a second decision that changes the character of the feature entirely.

NormalOpen bar
Name and emailRequiredNot asked for
Who can orderAnyone who will identify themselvesAnyone at all, anonymously
How abuse is limitedBy email addressBy network address
Active-request limitAppliesDoes not apply
SuitsA club, a school, a paid eventA wedding, a party, a stand at a show
Open bar is named accurately. Nobody is asked who they are, and the only thing standing between the printer and a determined guest is a rate limit on their network connection. That is the correct trade at a wedding where the point is that people take away pictures. It is the wrong one anywhere the prints cost somebody money.

What a guest fills in

FieldNotes
NameUp to 120 characters. Not required in open bar
EmailMust be a real address. Not required in open bar
PhoneOptional, up to 40 characters
SizeFrom the sizes this community offers
QuantityBetween one and twenty
NotesOptional, up to 500 characters

What comes back is a ticket number in the form PR- followed by the community’s number and a four-digit sequence. It is what a guest quotes when they come to collect, and what an owner searches for when somebody asks about an order.

Sizes

Six standard sizes can be offered: 4×6, 5×7, 8×8, 8×10, 11×14 and 16×20 inches. The owner chooses which of them appear under Available print sizes. A community that has never configured this offers 4×6, 5×7, 8×10 and 11×14 — the square 8×8 and the large 16×20 appear only once the host turns them on.

A community can also define one custom size with its own label — a square format, a panoramic, whatever the printer in the room actually does. It appears alongside the standard sizes and is only selectable when a label has been set.

The resolution check

A guest asks for 8×10 Has a minimum been set? no → accepted, no check runs Can the photo be measured? no → accepted anyway Does it meet the minimum? no → refused, with the numbers “would print at 180 DPI, 300 required” “it works at sizes up to 5×7” yes → into the queue a ticket number is issued the owner sees it at once The amber branch is a choice: an unreadable photo is let through rather than blocking a guest over a glitch.
Two things in this diagram are unusual and both are deliberate. The refusal does arithmetic on the guest’s behalf — it finds the largest size that photograph would survive and names it, turning a dead end into a smaller order. And the amber branch fails open: when a photograph’s dimensions cannot be read, the request is accepted rather than blocked, on the reasoning that a network hiccup should not cost a guest their print. The queue catches it later and flags it, so nothing slips through unnoticed.

The minimum is set in dots per inch, anywhere from zero to six hundred. Zero switches the check off entirely. Three hundred is the conventional figure for photographic printing; a community handing out 4×6 snapshots at a party can reasonably sit lower.

Bypass minimum resolution goes further: every photo is accepted at any size, nothing is refused or marked low resolution, and auto-print sends it. Small photos may print soft. It suits live events where every guest should walk away with a print.

Limits, and what stops abuse

LimitWhat it does
Three in fifteen minutesPer email address, or per network address in open bar. Slows down a machine, not a person
Active requests per personCounts requests that are waiting or done, but not canceled. One by default; up to fifty, or zero for no limit
QuantityNever more than twenty of one picture on one request
The hidden fieldA field no human sees. Anything that fills it in is told the request succeeded and quietly discarded
The default active limit is one, and it surprises owners more than anything else here. A guest who orders a print and then wants a second one is refused until the first is canceled or fulfilled. At a wedding that is the wrong setting and produces a queue of confused people; raise it, or set it to zero, before the doors open rather than during.

After a guest sends a request

The guest sees a confirmation straight away. On the web it repeats their email address and ticket number (“We will contact you by email at … Your ticket number is …”). The wording depends on how the host set up prints:

Set upThe guest is told
No charge for printsNo payment required. We will contact you by email.
The host charges for printsWe will contact you about payment by email.
Open bar, in the Linxy AppPrints are free.
Open bar, on the webYour print is queued. It will be ready at the pickup station.

The queue, and the two kinds of status

Each request carries two separate statuses, and conflating them causes most of the confusion in the queue.

What it tracksValues
Request statusWhere the order is in your processPending, fulfilled, canceled
Output statusWhether the print file itself came out properlyReady, low resolution, still uploading

Low resolution means the photograph can’t reach the community’s minimum at the requested size, so the output is capped at what the photograph actually contains. Low-resolution requests are never auto-printed. With the minimum at zero, or with Bypass minimum resolution on, nothing is marked low resolution. It is not a failure and the print will still come out — it will simply be softer than the size implies. Those requests can be found and cleared as a group when a queue has collected too many of them.

The queue can be filtered by status, and requests can be printed, retried, downloaded or deleted individually or in bulk. With Auto-print on, new requests go to the printer by themselves — instantly, or after a 30-second, 60-second or 2-minute cancel window. While the window runs, the request shows Auto-print in a countdown and a Cancel auto-print button.

Symptoms, causes and fixes

SymptomCauseFix
Print requests not enabledThe community owner has not switched them onEnable them in the community’s settings
A guest is told they have reached their limitThe active-request limit, one by defaultRaise it, or set it to zero for no limit
This photo is too small for a 8×10 printIt cannot meet the community’s minimum at that sizeThe message names the largest size it can manage. Order that instead
Every photograph is refused as too smallThe minimum is set too high for the pictures being postedLower it, or set it to zero to switch the check off
Requests marked low resolution keep appearingThe pictures can’t reach the minimum at the sizes orderedThey will still print, softer. Clear them as a group, lower the minimum, or turn on Bypass minimum resolution
A guest says they ordered but nothing is in the queueThey may have been caught by the hidden anti-robot fieldAsk them to order again without a browser extension filling forms in
Pick a valid sizeThe chosen size is not among the ones this community offersEnable it, or pick from the ones offered
Two guests report the same ticket numberThey are misreading it — the number includes the communityTicket numbers are unique within a community

Things people commonly get wrong

“Low resolution means the print failed.”The file exists and will print, just softer than the size suggests. It is a quality note, not an error.
“Guests can order as much as they like.”One active request each, unless the owner has raised it. Change it before the event, not during.
“Open bar just skips the form.”It removes the identity anchor entirely, so limits fall back to the network address. Right for a wedding, wrong wherever prints cost money.
“A refused photo cannot be printed at all.”The refusal names the largest size that would work. Read the message; it contains the answer.
“Canceled requests still count against a guest.”Only pending and fulfilled ones do. Canceling frees the guest to order again.

Branded and scannable prints

A host can add a branding bar to every print — the occasion’s name, colors and a logo — and, where Linxy has turned it on for the account, make prints scannable so the paper photo opens its album post in the Linxy App. See Print branding and scannable prints.

Related reading: Running the print station, Print branding and scannable prints, Uploading media, and When something is not working.

Still need help? Contact support