The record starts where the work happens. Count in front of the shelf, take the order next to the customer, log the service call at the machine. Nobody retypes it back at the office.
The mobile app uses the same database as Platform Web. Stock booked out in the warehouse is already booked out on the accountant's screen, so no list waits to be keyed in that evening.
Who is it for?
Warehouse operators, field sales reps, service technicians, branch staff and managers who approve on the move. Anything that wants a big screen (definitions, heavy documents, reports) stays on the web. Mobile is for quick entry, status updates and closing tasks.
Each team signs in to the same account from its own devices. Permissions match the web: a warehouse or customer you shouldn't see is hidden on the phone too.
What does it do?
Stock counts and movements, sales and order steps, CRM tasks, service requests and maintenance work orders all run on mobile. You scan barcodes and get through entry with short forms. Managers see field work reach the office lists during the day. A fault report opens from the field, and assignment and closing are tracked.
Why does the data stay in one place?
Stock written down on mobile appears in the Platform Web stock list. A field order is written into the sales process. A CRM task is tied to the customer card on the web. Product and customer cards that arrive through integration carry the same identity on the phone. Mobile keeps no database of its own; it is the field view of the same data.
Key capabilities
Field sales and orders
During a visit you move quotes and orders forward from the phone. If your permissions allow, you see stock and prices on site. Back at the office, the same order continues on the web.
Warehouse and stock
Record counts, receipts, issues and transfers from the phone. Find a product fast and pick the movement type. Low-stock information shows on the web dashboard.
CRM tasks
See, update and close CRM tasks defined on the web. Notes and status changes go into the customer history, so the field notebook and the CRM are not two things.
Service requests
Open a service request in the field, follow its status and log the visit. A technician who can start the record without stopping by the office saves time.
Maintenance (technicians and operators)
At sites using Maintenance Management, technicians and operators run the work from a phone. They scan the machine's QR code, report a fault with a photo, move the assigned work order forward, and start and stop their labor. They enter checklists and meter readings on site, book out the parts they use, and add a signature to the work order. Maintenance records entered without a connection are queued on the phone and sent once when it returns; offline data is stored encrypted on the device. The maintenance schedule, plant board and compliance screens stay on the web.
A typical field day
In the morning the warehouse team starts a count or shipment prep on their phones. A sales rep checks stock at the first customer and enters the order. At noon a service request opens and the assigned technician updates it. In the afternoon the office approves or completes the same records. By evening, what happened on phones matches the web lists.
Paper forms and the evening spreadsheet merge become unnecessary.
Relationship to other products
- Platform Web: Definitions, permissions, dashboards and heavy documents live on the web; mobile feeds them.
- Integration: Master data from your existing system is valid on the mobile client too.
Mobile does not replace Platform Web. It carries it into the field.
Device notes
The client is built with Flutter. Settle device policy, user accounts and permissions with IT. If the warehouse shares tablets, signing out has to be a habit, or permissions get mixed up.
When to add it
If warehouse or field records are entered late, if stock drifts away from the office list, or if service and sales visits stay on paper, Mobile is next. It is usually licensed after Platform Web is open, for your busiest field process.
FAQ
Does mobile work offline? For maintenance, yes: fault reports, work order status, labor, checklists, meter readings and part consumption are queued without a connection. For other flows, offline scope is settled in discovery for your scenario.
Is every web screen on mobile? No. Definitions, heavy reports and complex documents stay on the web. Mobile has the quick jobs: counts, movements, tasks, order steps, service.
Can we share tablets? Yes, but watch sign-out and keep users separate.
Why are CRM tasks on mobile? If field notes never reach the CRM, the customer history falls apart. This keeps sales and service in one customer record.
How to start
Pick one field process first, for example a warehouse count or a field order. Run only that on mobile with a pilot team for a week and compare with the web lists every day. If barcodes and product cards are messy, fix those first, or mobile's speed won't help. Train with a real count in the warehouse, not a tour of the menus.
Next step
Try it free, or use a demo to walk through your warehouse, sales and service scenario.