Mobile App

Availability — Connecting the mobile app is part of the Inventory module. Manage modules and your plan tier in Account & Billing.

The Knowledge ERP mobile app puts the everyday floor operations in your pocket. It's 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 are live on the device.

Signing in #

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

What you can do #

The app is 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 needs a due date, the same as it does on the web.
• Move stock between bins and locations on the fly — a unit that is out with somebody, missing or already on a transfer is refused with the reason, the same as on the web.
• Rentals — check equipment out to a customer on a rental and take it back, including capturing a due date and signature.

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

The app enforces 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 is refused with a message naming the status and what clears it — see when a unit can't go out. Nothing is recorded when a checkout is refused.

Working offline #

Spotty signal in the back of a warehouse is normal, so the app supports offline sync: it pulls down what it needs, lets you keep working without a connection, and pushes your changes back up once you're online again.

A queued action is still 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 — comes back as a failed operation naming the reason rather than being applied.

Versioning #

The mobile app has 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 ships 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.