The sales process worked, technically, but it was slower and messier than it needed to be:
Management wanted reps working directly out of SAP, but without handing them laptops or making them learn the full SAP GUI.
We built a custom SAP Fiori app around how reps actually work in the field, order booking, stock check, and retailer account status, all in a simple mobile interface.
The app connects directly into the backend SAP sales and inventory modules, so:
Getting the SAP Fiori integration right with their existing sales module took more back and forth than we’d initially planned for. Their SAP sales setup had some older custom pricing logic tied to specific reps and territories, and making sure that logic carried over correctly into the mobile order flow, without anyone accidentally booking at the wrong price tier, needed a few rounds of testing with the actual field team before we were confident it was solid.
Orders now hit SAP the moment a rep books them instead of showing up hours later. Stock-availability mistakes dropped significantly in the first two months after rollout, based on the client’s own order-rejection tracking. Reps also stopped booking fresh orders from retailers with significant overdue payments, since that flag is now visible on the order screen instead of surfacing days later in finance’s reports.
A few reps in areas with weaker mobile coverage still fall back to WhatsApp when the app can’t sync in time. An offline mode that queues orders and syncs once connectivity returns is something we’re still working on, it wasn’t part of the original scope.
Frontend: ReactJs
Backend: NodeJs
Mobile: Flutter
Database: MongoDB & Redis
Cloud/Hosting: AWS
Other Tools/Integrations: Flolive