Skip to content

A system you can shape, with an undo button.

We can't build every shop owner their own software. So we built one you can shape yourself, and made sure that shaping it never costs you your data or your nerve.

How it's assembled

Three layers, and you own the last one.

Every form you see is assembled from three layers in order. You never edit ours; you layer on top of it, which is why you can always get back.

01

The base definition

What every product, customer or supplier has in common: title, code, status, stock. Ours, and it doesn't change under you.

02

Your trade's template

Chosen when you sign up. It surfaces the fields your trade cares about, relabels them in your language, and hides the ones that don't apply. Fashion gets a variant grid; a kitchen gets serving units instead of shipping weights.

03

Your own overrides

Where you work. Add fields, reorder them, mark them required, hide ours, split them across sections. This layer is yours alone and sits on top of everything else.

Not a settings page. The actual forms.

Add a field

Six types: text, number, true/false, date, single-select and multi-select. Pick the type and it's checked from then on; a number field refuses a word.

Rename anything

If your staff call it a docket number, the form says docket number. The database keeps its own name; your people never see it.

Reorder and group

Arrange fields into the order you actually fill them in, and group them into sections so the busy screen isn't the first one.

Require or hide

Make a field compulsory so nobody skips it, or hide the ones you'll never use so the form stays short.

Show it only when it matters

Set a condition so a field only appears when it's relevant, keeping the form short for everyone else.

Decide who can touch it

Per role, per action: see, create, edit, delete. One set of rules covering the till and the back office together.

A custom field that can't answer a question is just a note.

Plenty of systems let you add a field. Then you discover you can type into it but never filter by it, sort by it, or put it in a report. A field you add to a product is typed, indexed and filterable from the moment you make it, the same as the fields we shipped.

  • Filter your product list by any field you added
  • Use it as a dimension or a measure in a report
  • It arrives at the till with its label, and works offline
  • Indexed automatically, no waiting on us, no schema change
  • Typed on save, so your totals never silently break

A real example

A bottle store

Adds alcohol % as a number and bottle size as a select. From then on: the product form asks for both, the till shows both on the tile, and the back office can group last month's sales by strength.


A hardware shop

Adds warranty months and power source. Now which corded tools are selling and what warranty exposure you carry is a report, not an afternoon.

Change it freely, because you can always change it back.

The reason people don't customise their systems is fear. We took the fear out.

01

Preview

See the form exactly as staff will, before anything is saved.

02

History

Every version kept, with who changed it and when.

03

Rollback

Return to any earlier version in one action.

04

Reset

Throw away your changes and go back to the default form.

Retiring a field doesn't delete the past

If you stop tracking something, the field comes off the form, but every value you already captured stays in place and stays searchable. Last year's numbers keep working even though this year's form is different. Nothing is stranded where you can't see it.

Shape it around how you already work.

Start free and change the forms on day one. Nothing to unlearn.