POS operations guide
Photography studio session-booking, print-order and deposit POS workflow
A studio sells reserved creative time and later delivers selected digital or physical products. Keep session booking, package scope, deposit, photographer and room assignment, delivery, proofs, selections, retouching, print orders, balance, cancellation and refund distinct.
Evidence and review scope
Evidence reviewed 2026-09-05. Reviewed the current Posnic stable release boundary and archived customer, sale and item models.
Stable release: v1.6.1, source commit 567a176. This page does not establish a live studio deployment, booking calendar, image gallery, consent release, copyright licence, retouching workflow, lab fulfilment, delivery proof, payment settlement or accepted pilot. Evidence remains pinned to an archived source snapshot.
What the current evidence establishes
Client account evidence exists
Customer identity, balance and payment-term fields can be evaluated for a client or company payer. They do not prove consent, model releases, usage rights or image privacy.
Sale and payment records exist
Sale lines can model sessions, packages, deposits, extras, prints, tenders and refunds. They do not prove calendar availability, card settlement or creative delivery.
Stock evidence exists
Item and stock-history paths can be inspected for frames, albums, media and other physical products. Image selections, retouching and lab status need separate controls.
Creative and legal duties remain operational
Image retention, release wording, copyright, child data, lab quality, delivery and local tax and privacy duties require owner review outside POS evidence.
Photography studio POS controls before rollout
A booking promises time; a deposit proves only part of the payment; a completed session is not the same as delivered images or prints.
| Area | Record to keep | Why it matters | Acceptance check |
|---|---|---|---|
| Client | Client or payer, contact permission, billing fields and duplicate check. | The correct person must own the booking and balance. | Private image notes stay off receipts. |
| Session product | Session type, duration, location, included people, deliverables, price and tax. | One generic shoot item hides scope. | Quote and receipt show accepted inclusions. |
| Booking | Date, start, duration, photographer, room or location and status. | Time and space are scarce resources. | Overlaps are blocked or flagged. |
| Deposit and balance | Deposit, total, due date, instalments, outstanding amount and payment proof. | A deposit is neither full payment nor delivery. | History reconciles to the package total. |
| Package scope | Session time, looks, edited files, prints, album pages, revisions and expiry. | Unclear inclusions cause disputes and unpaid work. | Extras remain distinct sale lines. |
| Session delivery | Completed, client no-show, rescheduled, studio cancellation or weather hold. | Booking and delivery are different states. | Outcome does not overwrite payment. |
| Proofs and selection | Gallery or job reference, proof date, selected image references and approval. | Selections should not expose image files in billing exports. | References link without sensitive media. |
| Retouching extras | Included edits, additional image count, revision, rush fee and approval. | Scope changes need price and consent. | Added work traces to approval. |
| Print order | Image reference, size, finish, quantity, lab state, promised date and cost. | Physical fulfilment is not session delivery. | Production and payment states remain separate. |
| Delivery and remake | Digital or physical delivery proof, collection, courier, defect and remake. | Completion needs evidence and an exception path. | Remake does not create hidden revenue. |
| Cancellation and refund | Notice window, retained fee, credit, refund, reason and approver. | Informal exceptions create disputes. | Original booking and value changes remain intact. |
| Owner review | Sales, balances, future sessions, delivered work, print orders, refunds and failures. | Cash and creative obligations diverge. | Owner reconciles money and deliverables together. |
Practical workflow
Define the package before taking money
State session time, location, people, edited-image count, print or album inclusions, revision limit and delivery window.
Separate booking, payment and delivery
Keep deposit, final payment, session completion, image selection and final delivery independently visible.
Use references, not image files, in POS
Link a controlled gallery or job reference without placing private images, release documents or sensitive notes in receipts and broad exports.
Close money and promised work together
Review tenders beside balances, upcoming sessions, undelivered selections, lab orders, remakes, credits and refunds.
Studio booking-to-delivery flow
Create client
Capture minimum billing, contact and permitted follow-up fields.
Book scoped session
Reserve time, photographer and room against written package inclusions.
Record deposit
Keep part payment, balance and cancellation terms visible.
Deliver and select
Record session outcome, controlled proof reference, selection and extras.
Fulfil and reconcile
Track digital or print delivery, balance, remake, refund and close.
Hardware, software and data setup
Hardware
- Reception computer or tablet and receipt printer.
- Barcode scanner only for labelled frames, albums, media or retail goods.
- Payment terminal kept outside POS card-data storage.
- Separate controlled storage for images and release documents.
- Off-device backup for client, booking, sale and fulfilment records.
Software and data
- Client and company accounts with minimum necessary billing data.
- Session, package, deposit, retouching, rush, print, album, delivery, credit and refund items.
- Separate booking, session, selection, production and delivery states.
- Reports for balances, future sessions, undelivered orders, refunds and reversals.
- Export and restore workflow before real client data is imported.
Setup sequence
- Write package, deposit, reschedule, cancellation, edit, delivery, remake and refund rules.
- Create synthetic clients, photographers, rooms, session products and print options.
- Book overlapping sessions to prove photographer and room conflicts.
- Take a deposit and settle a balance without marking work delivered.
- Record completion, no-show, reschedule and studio cancellation cases.
- Add a controlled proof reference, image selections, extra edits and a rush request.
- Send a synthetic print order through production, delivery and remake.
- Test failed payment, reversal, retained credit and refund.
- Back up and restore synthetic records, then obtain operations, finance, privacy, copyright and local approval.
Product evidence to inspect
Mistakes to avoid
- Treating a booking, deposit or completed session as proof of final delivery.
- Selling a package without exact deliverables, revisions and delivery timing.
- Promising one photographer or room to overlapping sessions.
- Putting private images, release documents or sensitive notes in POS receipts or broad exports.
- Mixing session fees, edits, print production, delivery and deposits into one item.
- Changing selections, extras, cancellations or refunds without approval history.
- Importing real client data before backup and restore pass.
Use the blank photography studio POS acceptance record
The CSV keeps 24 controls blank until the exact studio workflow is tested, including bookings, packages, deposits, selections, print orders, payments, delivery, refunds, reconciliation and restore.
Primary sources used
Current stable release
Pinned source tree
Customer model
Sale model
Item model
PCI SSC merchant process
Questions
Is photography studio POS the same as studio management software?
No. Calendars, galleries, selections, releases, editing and lab fulfilment need separate controls.
Should a booked session count as collected revenue?
No. Booking, deposit, payment, session, selection and delivery are separate states.
How should a photography deposit be handled?
Link it to the client, session, package, balance, cancellation rule and receipt.
How should print orders be tracked?
Keep image reference, size, finish, quantity, production, approval, date, delivery and remake separate from the session fee.
Where does Posnic fit?
Archived evidence can be evaluated for accounts, sale lines, payment labels, stock history and reports. It does not prove complete scheduling, image workflow, consent management or a live rollout.
Where Posnic fits
Posnic Community Edition can be evaluated for reception billing, client accounts, session and print products, deposits, payment labels, physical stock and reports. Keep calendars, galleries, releases, image storage, copyright licences, editing, lab fulfilment and delivery proof outside scope until the workflow passes the blank record. Posnic Cloud helps only when the studio needs remote dashboard access, managed backup, multi-site visibility or scoped custom work.