One account,
several apps

Movira holds separate apps, each doing one job properly. What they share is underneath: the account, the clients and the permissions. Adding the next app does not mean starting over.

Five apps are live. Asking costs nothing.

Apps

A separate tool for each job

The apps are separate because a landlord and a shopkeeper do not have the same day. Accounts, clients and permissions are shared, because it is all one business.

Available

Logistics

Dispatch from order to invoice: planning, routes, waybills and billing. The driver gets an app that keeps working without coverage.

  • Planning on a timeline and a map
  • Driver app: proof of delivery, signature and photos
  • Partner carriers and margin tracking
  • Invoices from journeys, payments from bank statements
Available

Warehouse

Stock, picking, receiving and counting. Pickers get a handheld view built to be used with gloves on.

  • Stock by location and batch
  • Picking in waves, handheld for scanning
  • Webshop and courier integrations
  • Stocktaking without shutting the warehouse
Available

Rental management

Properties, contracts, readings, utilities and payments in one app. Tenants get their own portal, maintenance partners get their own view.

  • Invoices from contracts and readings
  • Utility cost allocation
  • Signing through Dokobit
  • camt.053 payments
Available

Digital signing

Sign documents with Smart-ID and Mobile-ID. Use it as its own app, or embed the signing widget in your own site.

  • Smart-ID and Mobile-ID
  • Several signers per document
  • Embeddable widget and API
Available

Point of sale

A till that speaks the same accounting as the rest of Movira. Runs on the web, Android, iOS and Windows.

  • Register, self-checkout and payment terminal
  • Products in and sales out of the accounting software
  • Shifts, Z reports and thirteen reports
Guides

Every app has a step-by-step guide

Four steps, screenshots from the working app, and a list of what people usually trip over. The guides are open without an account — so you can see what an app actually does before deciding.

POS

From an empty account to a working till, about half an hour.

  1. 1Put your products into the till
  2. 2Make the first sale
  3. 3Watch the day
  4. 4Close the month

Warehouse

From an empty warehouse to working picking.

  1. 1Set up products and SKUs
  2. 2Receive goods into the warehouse
  3. 3Take an order from picking to dispatch
  4. 4Open the dashboard in the morning

Logistics

From an empty account to a planned day, about fifteen minutes.

  1. 1Enter the first job
  2. 2Put jobs onto vehicles
  3. 3Check the day on the map
  4. 4Start the morning on the dashboard

Rental management

To the point where rent invoices come out every month on their own.

  1. 1Write down properties and units
  2. 2Sign a contract with a tenant
  3. 3Create the rent invoices
  4. 4Keep track of what has been paid

Signing does not have a separate guide yet.

Shared foundation

Separate apps, one foundation

This is a technical choice, not a marketing line. The apps share an authentication service, so one account opens all of them and permissions are managed in one place.

  1. 01

    In the browser, on the phone, on the desktop

    The same app opens in a browser, installs on Windows and travels on a phone. The driver and picker apps are built to be used with gloves on and without coverage.

  2. 02

    One sign-in

    The same account opens every app. You add a new colleague once, not once per app.

  3. 03

    Permissions in one place

    Who sees what is decided on the server, not in the interface. A hidden menu item is not security.

  4. 04

    One client register

    A client stays a client, whether they sign a contract or buy something at the till.

  5. 05

    Grow one app at a time

    Start with one. When the second becomes useful, the account and the data are already there.

Integrations

Every module is an API too

All five applications are documented and open. If you already run your own system — a web shop, accounting, a help desk — you do not have to move it: connect it instead.

Authentication with an API key

You create the key in the app, under account settings. The secret is shown ONCE — only a hash is stored, so a lost key cannot be read back afterwards by anyone, ourselves included.

  • Authorization: Bearer mvk_…
  • X-Api-Key: mvk_…

Two forms, so the key also fits tools that consume the Bearer header themselves.

What a key means

  • A key carries the rights of whoever created it: narrow the role and the key narrows with it.
  • Each key can be revoked on its own, without breaking the other connections.
  • A key is valid within one account — if you work under several companies, each has its own.
  • There is no password login for the API. That is deliberate: a password would end up in a config file, and two-step verification would break the integration.
Contact

Would one of these solve your problem?

Tell us what you do by hand today. We will say honestly whether Movira helps or not. Including when the answer is no.

We usually reply within one working day.