Franchise CRM and dispatch with split-payment processing
Role
Full-stack engineer
Booking conflicts
−80%
Payments
Stripe OAuth split
A franchise network needed territory-aware routing and real-time appointment booking, but concurrent bookings collided on the same slots, and revenue had to settle to individual franchise locations rather than one central account.
A Next.js and Django REST platform handling territory routing, corporate analytics and real-time appointment booking. Stripe OAuth enables split-payment processing per franchise location. Redis distributed locks serialize contended booking slots, and a Twilio-powered call center adds PiP mode and live call switching.
High-concurrency booking conflicts fell 80%.
Interested in work like this?
Get in touch