Courtes démos des modules – découvrez comment la plateforme fonctionne en pratique.
1:28
HSE in a binder, environment in a spreadsheet, GDPR in a folder — and one login instead.
1:00
The tender that fit you closed before you saw it. Doffin watched for you — pay only if you win.
1:13
The CFO asks what quality work saved, and you have a feeling. Here's the number.
0:29
Thirty seconds: three systems, one login.
0:24
Thirty seconds: pay only if you win.
0:24
Thirty seconds: what the quality work saved.
3:02
A report nobody followed up is worse than none — people stop reporting. From report to closed, on record.
3:03
A plumbing firm with a report point on the loading bay. Someone scans the QR code and reports a deviation with no account and no login, and gets their own link to add photos later. The report becomes both a deviation and a case, so it can be assigned and given a deadline. The follow-up is a checklist, and when an item is set to deviation the new deviation lands on the same case. The road runs both ways, as a relation and not a line of text somebody wrote.
1:55
Internal control as a binder on a shelf: routines nobody reads, inspections from memory. The version people use.
2:10
A risk nobody wrote down is a risk nobody prepared for.
1:35
An audit is due, a review is next month, someone wants last year's numbers — running on live data.
1:21
Someone sees something wrong and says nothing. A safe channel, and control of the data you hold.
1:36
An HSE card ran out, and nobody noticed until the inspector did.
1:11
Holiday requests by email, hours in a spreadsheet, approvals over the shoulder.
1:13
The inspector asks for the data sheet, and someone goes looking for the binder. One scan away instead.
1:11
Anyone can ask how your suppliers treat their people — and the law says you must answer.
1:31
A rebuild brings its own deviations, risks and outside people. Walls around each job.
1:51
A tender asks for your climate accounts, and you have power bills. An afternoon, done yourself.
1:41
The reporting that hit the big companies rolls down to their suppliers — and stops at you.
2:19
Basic module B1–B11 and comprehensive module C1–C9, per location with consolidation, filled from climate data and HR, one report as PDF.
1:16
The tender that fit you closed last week, because nobody reads Doffin every day.
2:00
Finding the tender is the easy part. Then come the evenings of requirements and answers.
6:34
Let the system pick your procurement codes, see the open Norwegian tenders that fit ranked with days left, start a bid from one, pull the requirements out of the documents and draft the answers, then set who gets the alerts and let new tenders be shared between colleagues in turn. English narration, 6 min 34 s.
1:20
A lead comes in — and six weeks later it's signed, or lost between inbox and spreadsheet.
1:27
Four on a Friday, a case comes in — and who takes it shouldn't depend on who's around.
0:59
The job is done on site; the paperwork at a desk, hours later, from memory.
3:06
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.
6:17
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:22
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.
3:58
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:32
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.
1:19
Orders by phone, email and a sticky note by the till — each one typed up, each one missing something.
1:10
Someone calls to book the room; you check, call back, and hope nobody double-books.
1:40
Type a name, article number or barcode. A scanned code selects the product instantly.
1:00
Category matches too, and free-text lines still work next to product lines.
1:01
Search the product, enter the quantity, done. Filter the stock overview by product, SKU, barcode or location.
1:04
One picture per product, shown in the product list, the stock overview and search results.
1:08
Your logo and address on the PDF, and saved e-mail texts to choose from when sending.
0:53
The same product search on returns to the supplier and in the bill of materials.
4:59
The whole chain: setup, sales order with reservation, production with picking, assembly, quality check and packing, delivery and restock from shortfalls.
1:45
Barcode and QR labels, scanning with the phone camera or a reader, in and out with quantity and note, stock updated at once.
3:10
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:21
For the supplier: the customer’s order is read from PDF into a sales order, with product matching, stock before and after, a count, confirmation and shipping.
1:50
For the customer: the supplier’s packing slip is read against the order, lines are tied, goods are counted and the receipt is registered.
2:16
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:15
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:22
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.
1:05
Every answer is in the system — five clicks away. Ask instead, on your own data.
3:01
Quick actions is off until you switch it on. Bind a key to a field, build a recipe of seven steps as you work, give it a key, and read the run log afterwards. The pages are unchanged.
2:06
Mark your own activity and get a draft recipe. Paste a sheet from Excel, map the columns, run every row as a draft, and see each change before you approve. If a row was changed by someone else, nothing is written.