A Blueprint Pattern for Sales-Floor Configurators

The brief

A sales team wants to switch unit finishes, materials, and view orientations live, in front of a buyer, on a single machine. No crashes. No “give me a second.”

The pattern

A small core: one configurator subsystem, one data table, one event channel. UI talks to the subsystem. The subsystem fans events out to whoever is listening. Decoupled.

// pseudocode
ConfiguratorSubsystem::ApplyOption(OptionId);
// fires UConfiguratorChanged on the event channel
// finishes, lighting, materials all listen and update themselves

Why this holds up

• New options never need new wiring. Add a row, add an asset, done.
• Listeners are isolated. A broken material doesn’t cascade.
• The subsystem persists state across level transitions.

A configurator that breaks during a sale is worse than no configurator at all.