The expo floor plan that matches the hall: three patterns and where each breaks

Every exhibition floor plan is a race between the sales team and the print deadline. Booths sell, swap and resize until the night before doors — and every change has to reach the app, the website, the kiosks and the signage. Teams handle this three ways.

Pattern one: redraw and export

Someone maintains the plan in a drawing tool and exports images to every channel after each change. It works for a twenty-booth fair and collapses at two hundred: by opening day the app shows Tuesday's hall, the kiosk shows Monday's, and the printed you-are-here board shows last month's.

Pattern two: nightly sync

A script pulls the booking system each night and regenerates the plan. Better — the map is only ever a day wrong. But the day before opening is exactly when a day is too long, and the script is unowned infrastructure that fails silently on the busiest week of the year.

Pattern three: the plan renders from the data

The floor plan is not a drawing that gets updated; it is a view of the booking records. A booth is drawn because a booking exists, named because the contract names it, and tiered because the record says gold. When sales confirms a booth at 6pm, every kiosk, phone and embed shows it at 6:01.

The hard part is not plumbing; it is stable place IDs on both sides, so links, QR codes and routes survive re-plans. That discipline is the core of how Mapnyx is built — the hall is mapped once, and each event renders as a data layer on top of it.