See the whole system at work

Every walkthrough is recorded in the real thing, with English voice-over.

Start free
A faster day: search, rows and scanning

Search that forgives typos and spacing, clickable rows, barcodes with a check digit, several order lines in a row and scanning at goods receipt.

2:49
The warehouse in your pocket: shelves, counting and moving

On the phone: scan the shelf, quick in, count the shelf against the list, move to the service van as one action, and the overview grouped by warehouse with minimum right in the table.

2:04
Receiving with lot and expiry, labels and an unknown code

One GS1 scan gives product, lot and expiry on receipt; the lot follows the product card and overview; labels on sheets or rolls; an unknown barcode becomes a product with one tap.

2:04
Is the box packed correctly? Weight check when packing

Small items without barcodes are checked by weight: weigh a handful to get the weight per unit, weigh the packed box against the order, and get suggestions for what a deviation could be. Optional per company.

2:08
Plan the week by dragging: technician, day and time in one movement

Drag a job from the unassigned list straight onto a technician’s hours. The card hangs from the pointer all the way, and technician, day and time are set by the same drop. Move it on, lay out the rest of the week in the week view, and see the system speak up – with the reason, not just a question – when you are about to schedule a job waiting for a part.

2:49
From text to checklist: workstations, AI-made checklists and bikes that take their own route

A bike workshop with four stations. The job is written as plain text on each work step, and the checklist is created from the text, with a preview before anything is saved. One flag decides whether the repair is included: one bike just needs a wash, one needs repairs. On the board the checklist follows the card from station to station, every answer is saved at once and remembers who and when, and the overview shows where the checklist was used and which bikes raised a deviation.

5:50
The customer calls, you answer with a date: catalogue, promised delivery, production and purchasing

A bike workshop that builds bikes. The seller finds the bike in the catalogue, picks the tyre size the customer wants, and gets a delivery date calculated from free stock, supplier lead times and station capacity, with the bottleneck named. The order becomes a sales order, production orders with sub-orders for the wheels made in house, and draft purchase orders per supplier, all sharing one reference. The second half shows the setup: bill of materials with minutes and setup time, choice groups, the internal cost breakdown, supplier lead times and pack sizes, and the station calendar with closed days.

4:52
Many rows at once: CSV in and out, with a preview and a full trail

The supplier sends a new price list. You download what is in the system, correct it in a spreadsheet, and upload it again. Before anything is written the system shows what will be new, what changes with the old and new value field by field, what is unchanged, and which rows have errors. Afterwards the whole run sits in a log with who, when and row by row, and the same changes appear on the product itself. Stock goes the same way, but is booked as a count in the movement log. Finally: products with an end date that leave the search without leaving the history, barcodes that several products may share, documentation on the product, and the build record showing everything that actually went into a production order.

3:39
The customer calls: one search box, and the whole customer on one page

The support desk. The customer gives an e-mail, a phone number or her own order number, and you get cases, sales orders, the production behind them and deviations on one page — including the deviations the customer reported herself. Phone numbers are found whatever the spacing and country code, and a single unambiguous hit opens straight away. If she says something that is written down nowhere, it is written down there and then as a deviation and a case that are linked. The case opens straight from her card, and the rest becomes one log: the comment with the photo and the report she sends in the same entry, a checklist for what the plumber should go through, and who takes it and by when.

3:15