Features

What Dental Lager does.

Every section describes something that exists in the application today. No planned features, no integrations that have not been built.

1. Inventory

Inventory per clinic

Products, suppliers and categories are shared across the organisation, so a group does not maintain the same catalogue several times over. Balance, reorder level, critical marking and withdrawal history belong to each individual clinic.

  • Class A, B and C for how urgent an item is
  • Favourite and do-not-order marking at shelf level
  • Deliveries, withdrawals and manual adjustment with a note
  • A barcode per product and a separate barcode for the box

2. The stockroom

Barcode scanning in the stockroom

A tablet is mounted in the stockroom and tied to the clinic by a manager. It is signed in as the clinic, not as a person, so whoever fetches an item does not have to log in mid-task.

  • Barcode reader over USB or Bluetooth. No camera scanning.
  • An item can also be found by name when the barcode will not read
  • The withdrawal records clinic, tablet and behandlare (practitioner)
  • A manager connects and disconnects tablets from their own computer
  • New products are not created at the shelf, that is done at a computer

3. Ordering

Reorder level and the To Order list

Every item has its own reorder level per clinic. When the balance falls below it, the item is flagged automatically in the application and appears on the To Order list, together with how much is missing.

  • Critical class A items are raised separately on the dashboard
  • An order link per product, straight to the supplier's page
  • The list can be printed or saved as a PDF
  • The watching happens inside the application. No email dispatch today

4. Statistics

Statistics per behandlare, with guardrails

Consumption per behandlare is the whole point of the system, and at the same time it is data about employees. The figures are therefore deliberately framed: they are shown to managers, compared against the median for colleagues, and never ranked.

  • Nobody is flagged as an outlier below 30 withdrawals in the period
  • Deviation is measured against the median for colleagues, not an average
  • A breakdown per material, and comparison of up to four behandlare
  • Reports as PDF and Excel, where each report carries its caveats at the top
  • The whole feature can be switched off for an organisation that does not want it

5. Groups

Several clinics under one organisation

The catalogue is shared, the operation is per clinic. The clinic switcher is shown only to someone who genuinely has access to more than one clinic. A single clinic sees no extra control at all.

  • Access to a clinic is controlled per user
  • Statistics are shown for the selected clinic
  • Clinics can be paused or closed without the history disappearing

6. Data

Import and export

The catalogue can be read in from a spreadsheet instead of being typed. The file is read on the server and errors are reported row by row and column by column, so a mistake in row 40 does not quietly take the rest with it.

  • Reads .xlsx, .xls, .csv and .tsv
  • Suppliers and categories are created when a row refers to them
  • Order links can come along in the import
  • Export to PDF and Excel from statistics and the To Order list

7. Permissions

Roles that mirror the clinic

Three roles, plus the tablet as its own sign-in. Nobody sees buttons that would be refused anyway. Someone without permission does not see the control.

  • Staff: see the balance, receive a delivery, record a withdrawal
  • Clinic manager: edit the catalogue, adjust balances, manage behandlare and tablets
  • Organisation administrator: users, permissions and settings
  • Two-factor sign-in is required for administrators

8. Traceability

A history that cannot be rewritten

Withdrawals and the event log are rows that are added, never changed or removed. The application has no function for deleting them. Products and suppliers are archived instead of disappearing.

  • Every withdrawal carries clinic, time, behandlare and who or which tablet performed it
  • Customer data is separated in the database, not only in the code
  • Sign-ins, archiving and imports are recorded in the log

Shall we go through it together?

We show the system in a walkthrough and answer what it does and does not do.

Book a demo