Practical guide
What is van selling
Van selling is a sales model in which a seller carries stock in a vehicle, takes the order and hands over the goods during one outlet visit. Payment follows the agreed terms. The assortment is limited to vehicle stock, which is tracked as a mobile warehouse.
- SFA: field sales automation
- Warehouse Operations and Inventory Management
- Marked Goods & E-Invoicing

In detail
Van selling combines taking an order and handing over available goods during a visit. In pre-selling, the order is captured before a separate delivery. A hybrid model delivers some items from the vehicle and orders the rest for a later delivery; keep those lines and documents separate. In every model, payment follows the agreed terms and need not happen at handover.
Choose the model using the economics of the actual route. Compare trip cost and duration, outlets served, order volume, vehicle utilisation, storage constraints, returns and unfulfilled demand. A small or remote outlet alone does not establish a van-selling advantage. Compare routes over equivalent periods and account for differences in assortment and service conditions.
Track the vehicle as a stock location. Book stock equals opening stock plus receipts minus issues: loads and accepted returns add stock; customer handovers, returns to base, transfers and documented write-offs reduce it. Do not count the initial load twice. Reconcile at the same cutoff, by SKU and base unit of measure, separating batches and stock conditions where needed. Convert cases and individual units using the factor for that SKU; the same packaging name does not guarantee the same quantity.
Illustrative example for one SKU: the vehicle starts with 0 units, receives 2 cases of 12, hands over 5 units to a customer and accepts 2 returned units for inspection. With no other movements, book stock is 0 + 24 + 2 - 5 = 21 units. The physical count should also be 21, including the return. If the remaining 19 units are saleable and free of reservations or other restrictions, 19 units are available for the next sale, not 21. Release returned goods only after deciding their condition. Investigate differences using documents and a recount; checks can also take place during replenishment or a vehicle handover.
Reconcile goods and money separately. A credit sale is not a payment received, and a payment may settle an earlier debt. Link cash, confirmed noncash payments, refunds and cash handovers to documents and responsible people. GPS records the device location and timestamp; it does not by itself prove that goods or money changed hands with the customer.
Offline work depends on the configured workflow and device data. Before departure, check prices, stock and customer terms; on reconnection, check transmission, acceptance, errors and duplicates. Distinguish the time goods changed hands from the time the system recorded it: a late document may explain a discrepancy at the cutoff. Resending the same document does not mean another handover. Local saving is not completed exchange. Confirm marking, fiscal and external exchange capabilities for the country and project.
How it is applied
- Prepare an anonymised example of one trip and SKU: opening stock, load, sale, return and payment. Include units of measure and pack quantity, handover times and document statuses, the current accounting system and staff roles. A full customer database is not needed for the initial discussion.
- Separate pre-selling, van selling and mixed workflows. Define which items can be handed over now, which need a later delivery and which document confirms each handover. A draft order is not a physical stock issue.
- Define mobile-stock opening, conversion from packs to the base unit of measure, and saleable versus blocked stock. If reservations are used, agree how they are created and released: a reservation restricts free stock but does not itself represent a physical issue. Assign a document and an owner to each movement.
- Agree prices, stock availability, customer credit terms and limits, payment methods and exception handling. For offline work, define permitted operations, local data freshness and how sync errors are investigated.
- In a test cycle, check goods and money separately: partial handover, returns awaiting inspection, cases and individual units, late documents, retransmission and count discrepancies. Retain the reason for any correction and its link to the original operation. Test marking and fiscal exchanges for the agreed country within the agreed project scope.
- Discuss the example with Smartup through the SFA and warehouse and logistics pages. Identify whether the difference arises at handover, unit conversion, availability calculation or document exchange. This helps agree operations, data sources and acceptance criteria. Work scope, equipment, integrations and launch terms are confirmed separately.
