Hi everyone,
My organization is part of a consortium, and another member org also sells tickets for us. We recently redesigned our ticket stock, and thus our ticket designs as well, but ran into an issue. The other organization uses their own ticket stock, which doesn't align with ours, and so seating information becomes difficult to read for ushers when the guests have tickets printed by the other org.
Short of creating a second entire set of prices and associated designs for the other organization, can anyone think of a way to solve this problem?
Short of upgrading the box office hardware to ticket printers that are dual-feed (or outfitting those locations with multiple printers), there’s not a whole lot you can do. Given that your organization ended up doing this redesign without assessing the issue you are experiencing beforehand, perhaps it’s the case that you would rather just prevent those tickets from being printed by the other organization in the first place. The other organization’s mode of sale for your performance could have ticket printing turned off.
That may be the direction I end up going. Thank you!
We are also part of a consortium and redesigned our tickets. We have a specific consortium-wide MOS and Price Type that uses our old design so that our redesigned virtually doesn't really affect them. So far it has been working out, we just need to remember to add those price types and MoS's.
Thanks for the input! Sadly we have like 9 PTs so I would like to avoid having to copy all of those. I think the ushers will just have to deal with it!
I wonder if you could solve this by getting really clever with the custom ticket design elements you can output by modifying the LP_TICKET_ELEMENTS stored procedure. Theoretically you could tie back to the organization through the order (and maybe one or two other joins) and use that to determine the content in each of the six custom elements in your design. Custom 1, for instance, could dynamically output the performance date and time for Organization A but the customer's name (or nothing at all!) for Organization B.