Approaching production
The Barber Central booking and business operations
The Barber Central brings the customer and business sides of an appointment together. Customers browse services, prices and durations and book against staff availability; the business manages the day’s appointments and customers.
Business need
An appointment depends on knowing who is available, what the customer needs, which service is being delivered and what has been paid. Staff also need to handle people who arrive without a booking.
What was built and what it enables
I built tools for service management, staff schedules, customer history and appointments, including a walk-in queue. The implementation connects WhatsApp booking, rescheduling and cancellation with the relevant appointment.
Role
I build the product workflows and integrations, including WhatsApp through Meta’s Cloud API, Mercado Pago checkout, Resend email and Stripe subscriptions for businesses using the platform.
Architecture decisions
Design considerations
Appointment payments and business subscriptions are different flows. Each must connect to the right booking or business account, alongside staff availability and customer communication.
Architecture decisions
Keep service details, staff availability and customer information connected to the appointment. Give checkout, business subscriptions and notifications responsibilities that match the workflow they support.
Public links
Execution highlights
Customers can browse services and book; staff can manage availability, customer history and walk-ins. WhatsApp supports booking changes and cancellation alongside payment and email integrations.
Quality, security, and performance
The project emphasizes protected environments, explicit verification commands, browser QA, source checks, and careful handling of auth/provider configuration before public launch.
