Software · Operational tooling
A custom appointment scheduling system for tyre fitting operations — live since 2013, continuously maintained and evolved.
Context
Tyre fitting is highly seasonal — the summer-to-winter and winter-to-summer switchovers generate a concentrated surge of appointments in a short window. Managing this volume manually creates friction: wait times, double bookings, missed slots, and customers who give up.
Quoidbach needed an online booking system that could handle both private customers and corporate accounts — including leasing companies with specific agreements, offsite service locations, and display preferences that differ from standard time-slot booking.
The core constraint: everything had to synchronise with an existing internal management software that was not designed for external integration.
The hard part
The internal management software exposes only an XML interface with significant throttling limits and no shared ID structure. Synchronising online bookings with manual in-shop entries required building a reconciliation layer that works around these constraints without overloading the source system.
When a slot is booked manually at the counter while a customer is completing an online booking for the same slot, the system detects and resolves the conflict — without losing the customer or creating a double booking. Edge cases accumulate quickly at peak season.
Private customers, corporate accounts, leasing companies with specific contractual arrangements, offsite service locations with their own availability calendars — each requires a different booking flow, display logic, and confirmation process within the same system.
Solution
Rather than forcing the business to adapt to a generic booking tool, the system was designed around Quoidbach's actual operational model — including the quirks of their internal software and the specific needs of each customer segment.
Corporate clients can book using period-based display rather than individual time slots, matching how their fleet management works. Leasing company agreements are handled natively, with specific availability and confirmation flows per account. Offsite service locations have their own independent calendars, managed from the same interface.
The synchronisation layer polls the internal system within its throttling limits, maintains a local state, and reconciles conflicts using a deterministic priority model — manual in-shop entries take precedence, online bookings are held until confirmed safe.
Technical scope
Integration
XML-based sync with legacy internal software. Throttle-aware polling, local state management.
Conflict resolution
Deterministic model for online vs. manual booking conflicts. No double bookings, no lost customers.
Customer types
Private, corporate, leasing — each with specific booking flows, display logic and confirmations.
Multi-location
Offsite service locations with independent calendars managed from a single interface.
Stack
Python / Django. Self-hosted, deployed and maintained in full.
Live system
In production since 2013. calendar.quoidbach.com ↗
Result
The system has been running continuously since 2013, handling the full seasonal booking load for each tyre changeover period. Appointment slot discipline is maintained at a level that was not achievable manually — near-zero overruns, measurably reduced customer wait times, and no friction at peak demand.
It has been extended multiple times as the business evolved: new corporate accounts, new service locations, new display requirements. The architecture has absorbed these changes without requiring a rebuild.
10+
years in continuous production
0
service interruptions since deployment
∞
edge cases absorbed over the years