Van Sales vs Pre-Sales - How SFA Handles Both Models

Van sales and pre-sales are two distinct field execution models with different workflows, data requirements, and operational constraints. SFA systems that try to apply one configuration to both models create friction, inaccurate data, and low adoption. Getting this distinction right is a precondition for any successful SFA deployment.

How Van Sales Works

In the van sales model, the rep travels with physical stock loaded on a vehicle. Orders are taken and fulfilled on the spot - the outlet receives product during the same visit at which the order is placed.

The defining characteristic of van sales is that the transaction, the inventory movement, and the customer interaction all happen simultaneously. The rep is simultaneously a salesperson, a delivery driver, and an inventory manager.

SFA requirements for van sales reflect this:

• On-vehicle inventory tracking - the system must know what stock is loaded on the van at the start of each day
• Real-time stock deduction - as orders are fulfilled during visits, the available inventory must decrease in the system immediately
• Cash collection recording - many van sales routes involve immediate cash collection, which must be captured at the outlet level
• Van loading and unloading workflows - the start-of-day loading process and end-of-day reconciliation are distinct steps that the SFA must support
• Returns handling at point of delivery - goods returned by the outlet during the delivery visit need to be recorded and added back to van inventory

The failure mode for van sales SFA that lacks these features is typically inventory reconciliation errors: the van returns with stock levels that do not match what the system shows, creating disputes and manual correction overhead.

How Pre-Sales Works

In the pre-sales model, the rep visits outlets to take orders, but does not carry or deliver stock. Orders are collected during the visit, consolidated, and then fulfilled through a separate delivery process - usually by a distributor or a dedicated delivery team.

The rep’s role in pre-sales is purely selling: assessing outlet needs, communicating promotions, handling objections, and capturing orders. Delivery happens later, typically the next day or within a defined window.

SFA requirements for pre-sales are different:

• Order capture and transmission - orders taken in the field must be transmitted to the back office or distributor system reliably, including offline
• Order status visibility - reps and managers need to see whether orders placed on previous visits have been fulfilled
• Delivery confirmation - the system needs a mechanism to confirm that orders placed by the rep were actually delivered to the outlet
• Scheme and pricing accuracy - since the rep cannot correct a pricing error at point of delivery, the order capture interface must enforce correct pricing at the point of entry

The failure mode for pre-sales SFA that is not properly configured is order leakage: orders captured in the field that are not transmitted, not fulfilled, or not confirmed, with no visibility into where the gap occurred.

Hybrid Models

Many businesses run both models simultaneously, sometimes across different regions or different channels. Urban territories might use van sales for small general trade outlets while using pre-sales for modern trade chains. Rural territories might use van sales because distributor infrastructure is weaker.

SFA systems in hybrid environments need to support both workflows within the same platform, with the correct workflow presenting to the rep based on their assigned route type. A rep on a van sales route should see the van inventory and fulfilment screens. A rep on a pre-sales route should see the order capture and previous delivery status screens.

Attempting to run both models on a single undifferentiated workflow creates confusion at the rep level and inaccurate data at the management level.

What Managers Need in Each Model

Management visibility requirements also differ between models.

For van sales, managers need to track:

• Van loading compliance (is the van loaded with the right stock each morning?)
• Sell-through rate per van per day
• Cash collection versus expected collection
• Unsold stock returned at end of day

For pre-sales, managers need to track:

• Order capture rate per rep per day
• Fulfillment rate on captured orders
• Time between order capture and delivery
• Orders cancelled or modified after capture

An SFA system that surfaces the right dashboards for each model - rather than a generic activity feed - gives managers the specific visibility they need to manage execution in their model.

Configuring SFA for the Right Model

The configuration decision starts with an honest assessment of the business model. Questions to answer before configuration begins:

• Does the rep carry physical stock, or only take orders?
• Is delivery managed by the rep, a distributor, or a separate logistics team?
• Is cash collected at point of visit or through a separate billing process?
• Are there different models running in different geographies or channels?

Getting these answers right at the outset determines which SFA workflows are configured, which data is captured at which steps, and which reports management uses to track execution. Field sales studies show that SFA configurations mismatched to the actual sales model are one of the leading causes of rep non-adoption and data quality failures.

The model choice is a business reality, not an SFA decision. The SFA system must conform to the model, not the other way around.