Odoo ERP · Sales
Odoo for Field Sales: Orders, Stock, and Collections
· Updated · 2 min read
Field teams lose trust when they promise a quantity the warehouse has already sold, or a customer finance has already put on hold. The order has to see both.
The visit creates a quotation, not a chat
The rep confirms a quotation on the customer, at the price list for that customer, against stock that is reserved when the order is confirmed. A photo of a notebook is not an order the warehouse can pick.
The handoff from visit to invoice is the same chain as pipeline to invoice. Field sales just starts the chain on the road.
Credit and collections sit on the customer
If the customer is over the limit, the rep should see it before confirming. Collections are follow-ups on the open invoice, so the next visit is not a surprise to finance.
A dedicated sales app is useful once this document works. Building the app first gives the rep a pretty way to create orders nobody can deliver.
Pilot one route
One team, one warehouse, and the customers on that route are often a 4–8 week addition to sales and stock, or part of a 2–4 month first release. Do not roll every region out on the same Monday.
Bring one rep’s weekly orders to a free audit.
Frequently Asked Questions
Does the rep need constant connectivity?+
They need to confirm against stock and credit when they can reach the server. Design the pilot for the connection they actually have, and do not promise offline magic.
Can a rep change the price?+
Only inside a rule you write down. An open discount field is how the price list stops existing.
Should reps see cost?+
Usually no. Show them the price and the stock they are allowed to promise.