You are here

Home › Theatre Manager Online Help › Outlet Management

Web Sales in Outlet

Subscribe to Syndicate
Wed, 12/14/2011 - 13:14 — Tom

In an Outlet environment, some Outlets may choose to have web sales, while others may choose not to. In addition, two or more Outlets may choose to share an Apache server in order to reduce costs for hardware assets. Or to take this further, if there are several Outlets, two may share one Apache server, three others may share a different Apache server, while other Outlets may choose not to have web sales at all. This is easily done since Apache has a great deal of capacity, and can service multiple Web Listeners without taxing the server.

Each Outlet can also have their own web pages to give their ticket sales site their own look and feel so that the branding of their ticket sales web pages matches their home website.

Having a separately branded site does not require separate Apache machines, but does require having separate Web Listeners, with at least one dedicated to each Outlet.

If Outlet B wants to sell tickets online, they can either:

  • Have their own web site (Domain and Web Listener) and sell tickets through tickets.<outletB.org>/TheatreManager/2/. This allows them to have their own branding completely, or
  • Use a common Domain, Apache Server and their own Web Listener and sell tickets through tickets.<outletA.org>/TheatreManager/2/, which means the initial branding will look like Outlet A, but they are completely separate web sites after that.

If Outlet C wants to sell tickets, they can choose NOT to have a web site at all and allow Outlet A to sell online tickets for them. If that is the case, the tickets will appear in Theatre Manager as 'sold by Outlet A.'

If Outlet C plans to use ticket scanners at their venue, because sales data is not shared between Outlets, Outlet C will need to set up its own web listener(s); scanning is not possible at an Outlet which does not have its own web listener.