Feasibility call · Nicasource · Client booking platform
Seat-level booking, inside WordPress
- The situation
- A client asked for a seat reservation system. The team could not agree on whether WordPress could carry it or whether it needed a separate application alongside.
- What everyone assumed
- That this was past what WordPress could hold, and that a second, standalone system was the safe choice.
- The hard part
- The data model. Seats, availability, and reservations had to fit WordPress custom post types, meta, and relations without degrading as bookings grew — the exact failure people expect when you say "we built it in WordPress." The safe-looking alternative traded that risk for two codebases and a sync problem someone would own forever.
- Outcome
- Shipped inside WordPress, on one codebase. The call held up.