Configuration

Change the till without changing the software

What an operator sees is defined in data, not compiled into the application. Layouts, button menus, on-screen keyboards and every piece of text can be edited and rolled out without waiting for a release.

In detail

What you get

Skin editor

A visual editor for screen layouts — position, size and behaviour of every control, with the result applied to whichever lanes use that skin.

Screen templates

Each screen is a template describing its controls, so a new dialogue is a definition rather than a development task.

Button menus

Touch menus for departments, quick keys and functions, arranged to suit the counter.

On-screen keyboards

Keyboard layouts defined per screen and per skin, for touch-only lanes.

Languages

Operator text held per language in a translation table and switchable at the till. English, French and German are in place today.

Per-lane behaviour

Parameters that differ by lane or by site held centrally, so a lane's role is configuration rather than a different build.

How it runs

Step by step

  1. Edit Screens, menus and keyboards are laid out in the editor.
  2. Preview Changes are checked against the skin the lane actually uses.
  3. Publish Definitions are distributed to the estate.
  4. Apply Lanes pick up the new layout without a software update.

What it means at the counter

Outcomes

  • Layout changes in an afternoon, not a release cycle
  • The same software behaving differently where it needs to
  • New languages added by loading strings
  • Touch-only lanes without bespoke development

Suits

A good fit for

  • Retailers whose counters are not all the same shape
  • Multi-language or multi-region operations
  • Businesses that want to tune the till themselves

Next step

See LinxPos on your own counter.

Tell us how your lanes are set up today and what you want them to do. We will show you the system running and be straight about what it would take.