How should ticketing operators manage inventory changes after onsale?
After an event goes on sale, operators may need to add dates, change seating configurations, adjust held stock or release new ticket quantities. Those changes should be controlled as inventory transactions, not silent edits to historical sales.
Which changes are routine?
A performance may add a new date or release unsold production holds. A seated event may need a camera kill, newly accessible space or a revised standing section. A touring show may move venue. The impact varies: adding a new occurrence is typically less disruptive than changing the layout for an occurrence with sold seats.
What should change controls capture?
Record the original state, proposed change, approver, effective time and expected effect on existing purchases. Capacity changes should not break the invariant that issued, reserved and withheld entitlements remain within the applicable limit.
Why is an audit trail necessary?
When two departments manage onsales, a support agent must be able to explain why a seat moved from held to public inventory. Change history also supports reconciliation if a partner claims more tickets than originally allocated. Reports should distinguish newly introduced capacity from released holds, returned allocations and previously cancelled stock.
What should happen before publishing a change?
Preview the public effect, check active baskets and API channels, then execute during a controlled window if needed. Reconcile orders and inventory afterwards. If a change affects a buyer’s seat, access or date, communicate through an approved service process rather than hoping a new ticket silently solves it.
A platform’s value here lies in preserving trust in sold entitlements while still allowing teams to operate dynamically.