The record starts where the work is. Count in front of the shelf, take the order standing next to the customer, log the service call at the machine. Nothing has to be typed again back at the office.
The mobile app reads the same database as Platform Web. Stock booked out in the warehouse shows on the accountant’s screen straight away, so there is no list waiting to be transferred in the evening.
Who is it for?
Warehouse operators, field sales reps, technical service teams, branch staff, and managers who approve or track on the move are Mobile’s natural users. Large-screen and heavy definition work stays on Platform Web; Mobile is optimized for fast capture, status updates, and closing tasks.
In multi-location setups, every team connects to the same account from its own devices. The permission model matches the web: a warehouse or account you should not see is also hidden on mobile.
What does it do?
On Mobile you run stock counts and movements, sales/order steps, CRM task parity, and service-request flows. Barcode scanning, short forms, and screens built for field conditions cut recording time. When connectivity drops, re-sync is the goal according to the nature of the work; the aim is to share the same truth with the office.
Managers follow field work during the day instead of waiting for it to appear in web lists. With the service-request mobile flow, fault/request records open from the field, and assignment and closure are tracked.
How one database works
Stock written down on Mobile appears in Platform Web inventory lists. A field order writes into the sales process. A CRM task links to the customer card on the web. While B2B orders are picked in the warehouse on mobile, order status on the web updates. Product and account cards coming through Integration carry the same identity on the mobile client.
Mobile is not a “separate app database”; it is the field client of the EQLEM database. That is why reports and dashboards stay consistent on the web.
Key capabilities
Field sales and orders
During a customer visit you can advance quote/order steps on mobile. Inventory status and price visibility (permission-dependent) make on-site decisions easier. When you return to the office, the same order continues on the web.
Warehouse and inventory
You record counts, inbound/outbound, and transfer movements on mobile. Fast product find and movement-type selection match warehouse tempo. Critical-stock signals flow to the web dashboard.
CRM task parity
Field teams see, update, and close CRM tasks defined on the web. Notes and status changes write into customer history. The “field notebook” and CRM do not split apart.
Service requests
The service-request mobile flow supports opening requests, tracking status, and field logging. For technical teams, starting a record without returning to the office shortens cycle time.
Mobile-first experience
Screens are designed for touch, short forms, and clear action buttons. Heavy reporting and definition screens are deliberately left on the web; Mobile’s job is speed and accuracy.
A typical field day
In the morning the warehouse team starts a count or shipment prep on mobile. Field sales checks stock at the first customer and enters an order. At midday a service request opens; the assigned technician updates status. In the afternoon, web operations approve or complete the same records. At close of day, mobile movements and web lists align.
That cycle replaces paper forms plus evening Excel merges.
Relationship to other products
- Platform Web: Definitions, permissions, dashboards, and heavy documents live on the web; Mobile feeds them.
- B2B: Dealer orders can meet warehouse picking on mobile.
- Integration: Master data from your existing system is also valid on the mobile client.
Mobile does not replace Platform Web; it extends it into the field.
Device and operations notes
The Flutter-based client targets current mobile platforms. Device policy, user accounts, and permissions should be clarified with IT. Shared warehouse tablets need a strong sign-out discipline. For processes that need field photos or attachments, the web/mobile division of labor should be written clearly.
When does Mobile strengthen you?
If warehouse or field teams write records late, if stock reality drifts from office lists, or if service/sales visits stay on paper, Mobile is the right next product. It is usually licensed after Platform Web is open, against your heaviest field process.
FAQ
Does Mobile work offline? Field conditions vary. The goal is that critical records are not lost and reconnect with the core. Which operations are supported offline is clarified in discovery for your scenario.
Is every web screen on mobile? No, and it should not be. Definitions, heavy reports, and complex documents stay on the web. Mobile is for fast actions: counts, movements, tasks, order steps, and service.
Can we use shared tablets? Yes. Sign-out, user separation, and physical security discipline are required. Otherwise permission leakage risk rises.
Why do CRM tasks matter? If field notes never write into CRM, customer history fragments. Task parity keeps sales and service in one customer story.
Implementation tips
Pick one field process first (warehouse count or field order). For one week, run only that process on mobile with a pilot team. Reconcile daily with web lists. If barcode and product master quality is weak, mobile speed disappoints, clean cards first. In training, run a real warehouse walk instead of “touring the menus.”
Next step
Try free, or use a demo to clarify your field scenario (warehouse, sales, service). After Mobile is live, you can complete the end-to-end chain with B2B and Integration.