Mobile App

Availability — Once the mobile app is released, connecting it will be part of the Inventory module. Manage modules and your plan tier in Account & Billing.

Not yet available — The mobile app is not in the App Store or Google Play yet. This page describes what it will do.

The Knowledge ERP mobile app will put the everyday floor operations in your pocket. It will be a native iOS/Android app that talks to your account through a dedicated mobile API, so the same stock and records you see on the web will be live on the device.

Signing in #

You will sign in with your normal credentials, or scan a QR code for a fast, type-free login on a shared device. Mobile access will be available to any active subscriber — it won't require a higher API tier.

What you can do #

The app will be built around scan-first floor work:

• Scan barcodes to pull up a unit or Product instantly.
• Check units in and out — check units out of stock and back in. A checkout will need a due date and who is taking the unit. It will start on Me, so a checkout to yourself needs nobody to be searched for, whatever lists your role can see. You will also be able to choose a customer, a staff member or a customer contact where your role allows you to see them: those lists will be stored on the phone for offline work and appear once the app has synced.
• Move stock between bins and locations on the fly — a unit that is out with somebody, missing or already on a transfer will be refused with the reason, the same as on the web.
• Rental checkout — hand a unit to a customer with a due date, and take it back. You will be able to capture a signature at handover. This records the checkout against the unit; to create a rental agreement or an invoice, use the web app. Needs the Rentals module.

Everything you do will sync back to the same inventory and checkout records as the web app — there's one source of truth.

The app will enforce the same rules the web app does. A unit can only be checked out while it is In Stock, so scanning one that's already checked out, on hold, missing, in transit, out of stock or discontinued will be refused with a message naming the status and what clears it — see when a unit can't go out. Nothing will be recorded when a checkout is refused.

Working offline #

Spotty signal in the back of a warehouse is normal, so the app will support offline sync: it will pull down what it needs, let you keep working without a connection, and push your changes back up once you're online again.

A queued action will still be checked when it reaches the server, so an offline checkout of a unit someone else took in the meantime — or one queued without a due date or without a person — will come back as a failed operation naming the reason rather than being applied. A checkout queued with a due date that has passed by the time it reaches the server will be refused too, with the message "The due date on this checkout has already passed. Check the unit out again with a new due date."

Versioning #

The mobile app will have its own version, independent of both this product's version (the one in the docs version switcher) and the API version. Each follows its own cadence: the app will ship on its store-release schedule, the web product updates frequently, and the API contract changes rarely. The app and these guides won't always carry the same version number — that's expected.

For developers #

The mobile API is a distinct surface under /api/v1/mobile (login, login/qr, inventory check-in/out/move, rental checkout/return, and /sync pull/push). The native app itself is maintained as a separate project; if you're building your own field client, the mobile endpoints are documented in the API Reference.