Verified BursaPay workflow: Explains table-based and general seating configuration for events.
1. Overview & Purpose
Event supports enable_seat_numbering, seating_type, total_tables, seats_per_table and total_seats; Table and Seat are separate models.
2. Requirements & Setup
Seat names are unique within an event, and seats may be assigned to a table and ticket-pricing record.
3. Step-by-Step Workflow
- Enable seat numbering when the event requires assigned seating.
- Choose table-based or general seating.
- Configure tables and seats where applicable.
- Associate ticket pricing with seats when the workflow requires it.
4. Rules & Troubleshooting
Do not reuse the same seat name within one event. Verify the seating plan before ticket sales are opened.
5. Verification & Next Steps
After configuration, test a representative ticket flow from selection to issued ticket.