1. Home
  2. Integrations
  3. Vista
Integration

Filmgrail + Vista

Vista is the back office most large circuits run on, and there is usually no good argument for replacing it. There is a very good argument for replacing the part of the stack your audience actually sees.

What running Filmgrail on Vista means

Vista is a deep back-office system. Film booking, scheduling, inventory, pricing, concessions, settlement and reporting are the job it was designed for, and circuits that have shaped ten years of process around it are right to be nervous about anyone proposing to rip it out.

We are not proposing that. Filmgrail reads your programme, sessions, seat maps, ticket types and pricing rules out of Vista and takes over everything from the moment a moviegoer lands on your site. The sale comes back into Vista as an ordinary transaction, so your daily reports, your film hire settlement and your distributor reporting carry on exactly as they do today.

What changes is the surface. Instead of a ticketing vendor's web module with your logo on it, you get a site and a pair of native apps designed around the way people actually choose a film — and a CMS your marketing team can use without raising a ticket.

What moves between the two systems

Nothing is re-keyed. The integration reads what your box office already knows and writes back what the moviegoer just did.

Films and metadata

Titles, synopses, running times, certificates, cast, genres and release dates, enriched with artwork and trailers so film pages are not a line of text and a poster.

Sessions and showtimes

Every performance with its screen, format, language, subtitle and accessibility attributes, updated as the schedule changes rather than overnight.

Seat maps and availability

Live hall layouts with holds, house seats, wheelchair spaces and companion seating rendered exactly as they exist in the box office.

Ticket types and pricing

Adult, child, concession, member and loyalty pricing, plus surcharges and booking fees, applied by your own rules rather than duplicated in a second price list.

The completed order

Seats, ticket types, amounts and payment reference written back so the sale appears in your daily reports alongside the counter.

Reconciliation

A matching report on both sides so finance can tie the digital channel to the box office totals without a spreadsheet.

What your moviegoers get

  • A website built to sell, not to inform. Programme, film pages, showtimes, seat selection and checkout on one fast, mobile-first site you control through a CMS rather than a ticket iframe bolted onto a brochure page.
  • Native iOS and Android apps. Not a wrapper around your booking page. Autoplaying trailers, stories, watchlists, personalised showtimes and push — the things that make somebody open the app in a week when they are not buying.
  • One CMS for both. Films, showtimes, articles, carousels, banners, gift cards, push campaigns and loyalty edited once and published to web and app together.
  • A checkout that finishes. Seat maps, ticket types, fees, gift cards, value cards and saved payment in a flow measured on completion rate rather than on feature count.
  • Moviegoer identity. Nine out of ten end users on the platform create a profile, which turns anonymous transactions into a customer base you can segment, target and measure.
  • Audience data you can act on. Demographics, engagement, watchlists, ratings, sessions and digital box office in one view, joined across site and app.

What stays in Vista

Everything that makes Vista worth having. Film booking and distributor settlement, the scheduling engine, inventory and stock, counter and kiosk POS, gift card and voucher liability, the general ledger interface and the whole reporting stack stay in Vista, unchanged.

This also means the migration risk of a Filmgrail project is genuinely small. If it went badly, you would be back to your previous website. Your box office would never have been touched.

Who owns what

The division of responsibility between Vista and Filmgrail, written out so nobody discovers it in month three.

AreaVistaFilmgrail
Programme and schedulingSource of truthReads and publishes
Seat maps and inventorySource of truthReads and renders
Ticket types and pricing rulesSource of truthApplies at checkout
Counter and kiosk salesOwnsNot involved
Website and native appsNot involvedOwns
Online checkout and payment flowReceives the completed saleOwns the experience
Content, campaigns and pushNot involvedOwns
Moviegoer profiles and loyaltyWhere the system provides itOwns the digital layer
Box office reporting and settlementSource of truthReconciles against it

The point of the split is that your finance and operations reporting never moves. Every online sale lands back in your box office as an ordinary transaction, against the same ticket types and the same price rules the counter uses.

How a project actually runs

First we look at what your deployment exposes. That is a short technical conversation, not a discovery workshop, and it ends with a straight answer about whether the integration is a week of work or a quarter of it.

Then the build: your branding, your content model, your seat maps, your ticket types, your checkout rules. You review it on a staging site against your real programme, not a demo dataset.

Then launch, with your old URLs redirected rather than dropped so the search visibility you have built comes with you. Apps follow the site, usually a few weeks behind, because the CMS and the content are shared and there is no point shipping an empty app.

Nothing in that sequence requires you to touch the box office, which is why the risk of trying it is so much lower than it feels.

Answers

Frequently asked questions

Do we have to leave Vista to use Filmgrail?

No. Filmgrail is the digital layer above Vista, not a replacement for it. Programming, inventory, pricing, counter sales, settlement and reporting all stay in Vista.

How does Filmgrail read data from Vista?

Through the interfaces your Vista deployment exposes — typically its published APIs, with a file or database read as a fallback where an older on-premise installation does not expose what we need. We confirm which applies to your site before quoting any work.

Does the online sale appear in our Vista reports?

Yes. That is the whole point of writing the completed order back rather than holding it in a separate ledger. Online sales show against the same sessions, ticket types and price rules as counter sales, and a reconciliation report matches both sides.

What about Vista's own loyalty programme?

Where Vista holds the loyalty balance, Filmgrail surfaces it in the site and apps and earns and redeems against it. Where a cinema wants a richer digital-first programme, Filmgrail Loyalty can run the member experience while Vista stays the transaction record.

We also use Movio. Does that still work?

Yes. Filmgrail does not sit between Vista and your marketing tooling. Transactions still land in Vista, so anything reading from Vista carries on reading from Vista.