← The journalOPERATIONS / MOBILE

Running operations from your phone

Which ERP work belongs on a phone, which still belongs at a desk, and how to set up mobile use without creating new risks.

Pedestrians in Shibuya with directional camera-motion blur.OPERATIONS / SUNDIAL
Photography: Ayumi Kubo / Unsplash ↗ · Sundial motion treatment
THE PRACTICAL TAKEAWAY

Put short, time-sensitive work on the phone: approvals, lookups, stock moves and field updates. Keep long data entry and reconciliation at a desk.

Why mobile matters more than it used to

Most operations decisions do not happen at a desk. An owner approves a purchase between meetings. A warehouse lead checks stock on the floor. A salesperson confirms availability while sitting with a customer. When the ERP only works well on a large screen, those moments turn into phone calls, photos of paper and messages that someone later re-types into the system. Each step adds delay and a chance of error.

The aim is not to put the entire ERP on a phone. It is to make sure the few things people need to do away from their desks can be done properly, in the system, at the moment they come up.

Approvals that do not wait for a laptop

Approvals are the clearest win. A purchase order, a discount above the usual limit, a leave request or a payment run often waits hours or days simply because the approver is away from their computer. On a phone, the approver needs three things: the document itself, the context to judge it, and a clear approve or reject action.

Context matters more than people expect. For a purchase order, that means the supplier, the items, the price compared with the last purchase, and the budget remaining for the cost center. Without it, approvers either approve blindly or postpone until they reach a desk, which defeats the purpose.

Notifications need the same care. If every approval, comment and status change pings a phone, people learn to ignore them within a week. Send mobile alerts only for things that need a decision or a response from that person, group routine updates into a daily summary, and let each person tune what they receive. A short, relevant list of pending approvals is worth far more than a constant stream of alerts.

Stock and the warehouse floor

Warehouse staff benefit from a phone more than almost anyone, because their work happens away from desks. Useful mobile tasks include checking stock for an item across warehouses, moving stock between locations, recording a receipt against a purchase order, working through a pick list and recording a cycle count.

Keep the screens narrow in scope. A person counting stock needs the item, the expected location, a field for the count and a way to note a problem. Every extra field slows them down and invites mistakes.

Sales and service in the field

Field sales teams need to look up a customer's outstanding balance, check stock, see recent orders and create a quotation or a sales order on the spot. Service technicians need the customer's equipment history, the open issue, and a way to record the visit, parts used and time spent.

The common thread is that the record is created where the work happens. That removes the end-of-day catch-up where details are remembered imperfectly and entered late.

Connectivity is the practical constraint. Warehouses, factory floors and customer sites often have weak signal. Keep mobile screens light so they load on a slow connection, and teach people to check that a record has saved before moving on rather than assuming it went through.

What still belongs at a desk

Some work is better on a large screen and always will be. Bank reconciliation involves comparing two long lists side by side. Month-end close means reviewing many accounts and journals. Configuring price lists, setting up new items in bulk and building reports need room and a keyboard. Pretending otherwise produces cramped screens that nobody enjoys using.

A sensible rule: if a task takes more than a couple of minutes or involves comparing several documents at once, design it for the desk and make it readable, not editable, on the phone.

Keeping mobile use safe

Phones get lost and shared. Use the same role-based permissions on the phone as on the desktop, so nobody sees more because they logged in on a different device. Require strong sign-in, log people out after inactivity, and remove access promptly when someone leaves.

Sundial's redesigned workspace uses one design language across every screen, on desktop and on the phone, so the same records and the same permissions apply wherever someone signs in. If you want to see how your team's daily tasks would look on a phone, try the demo from your own device.