Reps Won't Use Odoo on Their Phones? Build the 3 Screens They Actually Need

Because Odoo's CRM and Sales apps, like most full ERP interfaces, are built desktop-first: lots of fields, menus, and options available on one screen, which is genuinely useful for someone sitting at a computer managing a full pipeline. A rep standing in front of a customer, working from a phone, is in a completely different context, and a full-featured interface that wasn't designed for a small screen and a rushed moment tends to feel slow and cluttered exactly when speed matters most.

Reps don't stop selling, they stop entering data where it belongs. The order gets written on paper, typed into a personal notes app, or sent over a messaging app to someone back at the office to enter later. The sale still happens, but it takes longer to reach Odoo, sometimes with details lost or altered in the hand-off, and Odoo's own records fall behind what's actually happening in the field. It's a well-documented pattern: the problem usually isn't reluctance to use software, it's a genuine mismatch between the interface and the moment it's being used in.

Almost always the same three things, in the same order: pick the customer they're standing in front of, add the products being ordered, submit it. That's the entire field workflow for most in-person or on-site sales, and it doesn't require anything else Odoo's full Sales app also shows, like pipeline stages, marketing fields, or reporting views that only matter back at a desk.

Because the problem isn't knowledge, it's fit. More training on Odoo's full Sales app doesn't make a desktop-oriented interface fit a rushed, one-handed, small-screen moment any better; it just asks reps to work around the mismatch more diligently. A purpose-built three-screen flow, by contrast, mirrors exactly what a rep does in the field and nothing more, which is precisely the kind of narrow-but-exact fit that tends to actually get used rather than worked around.

It should end up as a real sale.order written directly into Odoo through its API on submit, the same underlying record a rep entering it through Odoo's own Sales app would create. This is a write-back integration, not a read-only lookup tool, so it needs the same care around validation and authenticated, per-user submission that any write-back build does; see the read-only vs. write-back guide, linked below, for what that involves.

Directly: this is exactly the pattern behind the sales / mobile ordering app on this site, linked below, with its own live demo of the customer-products-submit flow. The three-screen shape isn't a simplification for its own sake, it's what the actual field workflow already looks like once everything not needed in that moment is left out.