Our view: the person responsible for a site knows it better than a developer does. The system should give that person control, not force a routine on them.

The problem with one routine for everyone

A shop, a warehouse and a hotel do not run the same way. Even two shops of the same chain differ. When a system forces every site through the same fixed steps, people find workarounds, and the data gets worse.

What we build instead

• The manager controls the settings from an admin console.
• Each setting can be switched on or off for one location, or applied to all with one button.
• When a setting is switched off, the old setting is kept. Switch it back on and it returns as it was.
• The system does not force extra steps on staff.

Freedom without clutter

Giving people freedom usually adds options, and options add clutter. We try to do both: full control, and a screen you can understand quickly. Our aim is that a new person understands what a screen does within about five seconds. That is an aim we design toward, not a measured result.

How we work toward it: group things by their role on the page, fold repeated items into small collapsed cards, and show only what matters on first sight. It is much harder to make something simple than to make something complicated. A clean screen usually hides a lot of careful work.

Where AI fits

Where it makes sense, we build the system so an AI reads the current settings from the database rather than from a hard-coded copy. That way, changing a setting does not mean rebuilding anything. We do not use AI everywhere. Where judgement is needed we use a model; for plain plumbing we use ordinary code.

Two questions to ask before you buy

• Who can change the settings: the person responsible, or only the vendor?
• If I switch a feature off, do I lose what I configured?