Live in production
Hans Photography Studio
A live system that digitalizes Hans Photography Studio — online customer booking on one side, onsite day-to-day studio operations on the other, in a single platform.
- 2026
- Full-Stack Developer
- Laravel, PHP, MySQL, Blade, JavaScript
Overview
Hans Photography Studio is a live client system that digitalizes how the studio actually runs. It covers both sides of the business in one platform: online customer booking — packages, rooms, branches, add-ons, availability, and GCash payment submission — and onsite studio operations — staff verification, admin and cashier work, inventory, and reporting.
Problem
A photography studio has two fronts that have to stay in sync: the public side, where people book packages and rooms, and the floor side, where staff manage schedules, rooms, payments, and records while the studio is operating. When those live in separate places, availability, payment status, and reporting drift apart — and the business stays only partly digital.
Solution
The platform is a Laravel application with Blade views and a MySQL database. It digitalizes both online and onsite operations as one system of record. Customers move through a structured booking flow remotely. Inside the studio, admin and cashier views work from the same bookings: payment verification, operational records, and revenue reporting. Payments are a manual GCash workflow — the customer submits payment details and a receipt image, then staff verify onsite. There is no online payment gateway.
Key Features
-
Online and onsite operations
One system for customer-facing booking and the in-studio operational loop — digitalizing the business instead of leaving the floor on paper or chat.
-
Customer booking
The online front of the studio: a guided flow from package and room selection through confirmation.
-
Photography package selection
Customers choose from managed photography packages rather than ad-hoc arrangements.
-
Studio room rental
Room selection is part of the booking, tied to what the studio actually offers onsite.
-
Branch selection
Bookings can be associated with a specific studio branch.
-
Add-ons
Optional extras can be attached to a booking without breaking the core package structure.
-
Booking availability
Availability is checked against existing bookings so rooms and schedules do not overlap blindly.
-
Manual GCash payment
Customers pay via GCash outside the app. The system records the payment for staff review — not through a payment gateway.
-
Payment receipt upload
A receipt image is uploaded with the booking so cashiers can verify the transfer onsite.
-
Admin booking management
Onsite administrators review, update, and oversee bookings while the studio is operating.
-
Cashier workflow
Cashiers verify payments and move bookings through payment state from inside the studio.
-
Revenue tracking
Confirmed payments feed into revenue views for studio operations.
-
Reporting
Weekly, monthly, and yearly reports summarize booking and revenue activity.
-
Package management
Studio packages can be created and maintained without changing application code.
-
Studio room management
Rooms are managed as first-class records used by availability, booking, and onsite operations.
Technology
A conventional Laravel MVC structure: Blade for the interface, controllers and validation for the booking and payment-verification workflow, Eloquent models for studio data, and MySQL as the system of record for both online bookings and onsite operations. JavaScript supports interface behavior such as availability and form interactions. Payment confirmation is an internal staff process, not a third-party checkout.
Architecture
-
01
Interface
Blade views and JavaScript for online customer booking and onsite staff administration.
-
02
Application
Laravel controllers, validation, and booking / payment-verification logic.
-
03
Data
MySQL with relational models for branches, packages, rooms, bookings, and payments.
-
04
Payments
Manual GCash workflow with receipt upload and staff verification. No payment gateway.
Challenges
-
Availability had to respect rooms, branches, and existing bookings rather than treating the calendar as a simple form field.
-
The payment flow needed to be reliable without an online payment gateway — receipt upload plus staff verification, not automated capture.
-
Online bookings and onsite studio work had to share the same records, while admin and cashier tasks stayed distinct on the floor.
-
Reporting needed to roll the same booking and payment data into weekly, monthly, and yearly views without a separate analytics stack.
Outcome
The platform is live in production. It digitalizes Hans Photography Studio’s business operations: customers book and submit GCash receipts online, and staff run the studio onsite from the same records — verifying payments, managing packages and rooms, and reviewing activity over time. It does not use an online payment gateway.
Gallery
