Features
The product is deliberately narrow: take an order from a phone at the counter, keep the documents safe for a short, known window, and give the shop a queue it can finish.
For the customer
No app, no account
A single public page per shop. The customer only needs a browser and the order reference.
Up to ten documents per job
Each file is size-checked before it is accepted and re-checked from storage afterwards.
Clear print choices
Copies, colour, sides and paper — limited to what the shop actually offers.
Private order tracking
A high-entropy tracking token or the printed reference reveals only that customer’s order status.
For the shop owner
One-screen order queue
Filter by status, open a job, move it through the workflow, cancel with a recorded reason.
Document access on your terms
Downloads are issued as short-lived, single-use links; you never share a permanent file URL.
Retention you set
Choose whether the clock starts at upload or at completion, within the platform’s allowed range.
Reports and receipts
Orders by status, documents stored, bytes used and completion counts over any date range.
Billing in one place
Plan, period, payment history and lifetime totals, with GST shown as its own line.
Notifications
A simple inbox for events that concern your shop, with an unread count.
For the platform operator
Cross-tenant oversight
An admin console lists every shop with the entitlement decision already resolved.
Audited actions
Suspensions and other platform actions require a reason and are written to the audit log.
Platform metrics
Shop, subscription and order counts are computed from stored state for an at-a-glance overview.
Retention jobs
Scheduled endpoints handle document deletion, authenticated by a shared secret.
How documents are handled
- Documents are checked by extension and file signature; anything else is rejected and never becomes an order.
- A cancelled order schedules its documents for deletion within the hour, rather than waiting out the retention window.
- Every API call is authorized on the server from stored state. Hiding a button is never the control.
- Secrets — payment keys, mail credentials, storage keys — are read only when the feature that needs them is used, so a misconfigured deployment fails loudly instead of quietly.