A Field Sales App: Orders at the Customer Site, Van Stock and Collections
31 Oct 2026
A field rep needs to record the order, the collection and the visit where the customer stands, and to keep working when the network drops. This guide ties the phone to the inventory and sales system, and says what to ship before maps and reports.
The rep leaves with a price sheet and a photo of yesterday stock, writes the order at the customer door, then types it again at the office in the evening. Between those moments the price changes, a second rep sells the last carton, or the collection is forgotten. A field app moves the entry to the place where the rep is standing. It is not a company brochure and it is not a shop the consumer opens. It is the tool of the employee who sells outside the office.
The value sits in four moves that happen every day: an order, a deduction from van stock or from the warehouse, a collection, and a visit. If you build one of the four and leave the rest on paper, the rep will go back to paper because paper is the complete record. The first release either covers the cycle they already live, or you wait until it does. Half a cycle is worse than the notebook they know.
The order at the customer door
- A product list with the price for this customer or this segment, not an old price saved in the gallery.
- The quantity the system knew at the last sync, with a mark when that number may be stale.
- A credit limit or a block on a late customer, visible before the order is saved and before the rep leaves.
- A signature or the receiver name on the order, so it cannot be denied later with no trace.
- An order number the rep can quote at the office, the same number the warehouse sees.
Van stock
The van is a moving warehouse. The morning starts with a count of what was loaded: item and quantity, signed by the storekeeper and the rep. Each sale from the van deducts that balance. It does not deduct only from the branch warehouse. A return the customer refuses comes back onto the van or onto a return document, according to the rule you write down. The evening compares what is left in the van with what the system expects. The difference is closed with a reason before the same rep goes out the next day.
If the sale is for later delivery from the warehouse, the path is different: the order reserves stock or waits for availability, and it does not touch the van count. Say which path is the common one. Building one path and then discovering that half the sales leave the van means drawing the screen again. The rep should not count cartons in their head and wait for the office to correct the figure. The phone is where the count happens.
Collections and the visit log
- Every amount is tied to a customer and to an invoice or an order, not to a lump called cash for the day.
- A partial payment stays on the same document until it is closed.
- The rep sees what this customer still owes before offering a new order.
- The visit stores an outcome: order, closed, no answer, or a visit with no sale plus a note.
- The time is stored on the device, because the network may return an hour later.
A map pin helps a supervisor see that the rep was in the neighbourhood. It does not prove the meeting happened. Inside a closed shop or on a dense street the pin can be tens of metres off. The written outcome and the amount collected matter more than the dot. Ask for location if you already argue about ghost visits. Do not build the first release around the map alone.
Offline use, and the office that receives the day
Between governorates, and inside a metal warehouse, the network fails. The order, the collection and the visit stay on the phone and upload later. The real clash is two reps selling the last quantity of one item before either order has synced. The rule is decided in the office, not on the two phones: which order stands, and who is told the quantity is gone. Write that rule before programming. The app applies it. It does not invent it during an argument.
The phone is the edge. The books the accountant and the warehouse trust are the back office: items, balances, invoices and collections. If there is no system and the evening is a file copied by hand, the app will pour into a void. Name who confirms an order at the office and who closes a collection. What an inventory and sales system should hold is the office side. This article is the pocket side.
What can wait
Rep commission, a monthly target and a leaderboard are screens you add after the order and the collection are numbers nobody disputes. A heavy photo catalogue that fills the phone before offline saving works will hurt the day. A product photo helps when the rep sells to a buyer who does not know the trade name. Load photos in stages. Do not make a photo a condition for saving the order.
What to send for an honest estimate
The number of reps, whether they sell from the van, from later warehouse delivery, or both, how collection works today, and how many customers sit on a route. A photo of a current order sheet and of a collection list teaches more than a general description. If each segment has a price, say who may change it: the rep inside a limit, or the office only.
The office side is set out in the inventory and sales system. The phone is mobile app design and development, and the order and stock rules are custom software development.
Send the rep count and whether sales leave the van or the warehouse from start your project. The WhatsApp button at the bottom of the page can take a photo of the order sheet or of the collection list you bring back each evening.
