Van sales manual
The Field seller module drives route-based selling: the seller loads stock into their truck (issue note), visits customers in the field, sells from the Swifto Seller mobile app, then brings back the unsold goods (return note). Everything is consolidated into sales reports.
Overview
Van sales (or route-based selling / van selling) refers to the model where a field seller travels with a vehicle loaded with goods and sells directly to their customers during a route. Swifto manages the complete cycle from the back office: you plan the route, load the truck (issue note), the seller takes payment in the field via the mobile app, and on return the unsold goods are brought back into stock (return note) before the sales reports are reviewed.
Business goal
- Organize routes (seller ↔ customers)
- Load stock onto the truck
- Sell on the go, in the field
- Return unsold goods to stock at the end of the route
- Track sales by seller / route
Target audience
- Field sellers — carry out the route (mobile app)
- Sales manager / supervisor — plans & assigns
- Warehouse / logistics — loads & receives returns
Not to be confused with
Van sales (Field seller module) is independent from standard sales (quotes / POs / delivery notes / office invoices) and from POS registers (fixed points of sale). Here, it is a traveling seller who carries their own stock.
Access and navigation
The module is accessible via the left-hand side menu: Field seller (truck icon). It groups the route screens and a Settings submenu (assignments, loading templates, numbering prefixes…).
Module screens
| Screen | Role |
|---|---|
| Visit scheduling | Route calendar: who visits which customer, on which day. |
| GPS tracking (map) | Field sellers' positions (real-time tracking). |
| Field sellers | Field seller records (master data). |
| Customers by seller | Assignment of customers / groups to each seller (territories). |
| Issue notes | Loading of the stock carried in the truck. |
| Return notes | Return of unsold goods to stock at the end of the route. |
| Sales reports | Consolidation of sales / non-sales reported from the field. |
The module's Settings submenu notably contains: Assignments (terminal / vehicle / seller), issue note templates (standard loadings), field seller classification and the prefixes for numbering issue / return notes.
Visit scheduling
This screen organizes routes as a calendar: you schedule which seller visits which customers and on which date. Each scheduled visit becomes a marker the seller finds again in the mobile app.
08:30
09:00
10:15
Click a calendar slot to create a visit, or an existing event to view / move it. Visits can be dragged and dropped from one day to another to reorganize the route.
Issue notes / truck loading
The issue note (BS) records the stock carried onboard: the list of items and quantities loaded into the seller's vehicle before the route. The colored dot shows the synchronization status with the mobile app.
| ● | Number⇅ | Type⇅ | Seller / Register⇅ | Date⇅ | Nature | Action(s) | |
|---|---|---|---|---|---|---|---|
| BS: N°000312 | Seller | Mouadh BEN AZIZA | 18/05/2026 | Stock replenishment | |||
| BS: N°000311 | Seller | Ayatollah ORABI | 18/05/2026 | Stock correction | |||
| BS: N°000310 | Register | POS Mégrine | 17/05/2026 | Stocktake |
Table columns
| Column | Description |
|---|---|
| ● Sync | Mobile sync dot: see the status table below. |
| Number | Issue note reference (e.g. BS: N°000312). |
| Type | Seller (stock carried by a field seller) or Register (point of sale). |
| Seller / Register | The field seller (or the POS register) receiving the load. |
| Date | Date of the load. |
| Nature | Stock replenishment · Stock correction · Stocktake. |
Synchronization statuses (dot)
| Dot | Status | Meaning |
|---|---|---|
| Blue | In preparation | The note is being entered on the back-office side. |
| Orange | Pending | Sent to the mobile app, awaiting acknowledgment by the seller. |
| Green | Synced | Received / confirmed by the seller's mobile app. |
Validation — once a note is synced (green dot), the Validate action appears to confirm the load and update stock. To save time, create issue note templates (recurring loads) in Settings.
Return notes / unloading unsold goods
At the end of the route, the seller brings back the unsold goods. The return note (RN) reintegrates them into stock. Each return distinguishes intact goods (resalable) from defective goods.
| Nature | Number⇅ | Seller⇅ | Reason⇅ | Date⇅ | State⇅ | Action(s) | |
|---|---|---|---|---|---|---|---|
| Intact | RN: N°000087 | Mouadh BEN AZIZA | Unsold (route) | 18/05/2026 | In progress | ||
| Defective | RN: N°000086 | Ayatollah ORABI | Damaged product | 18/05/2026 | Validated | ||
| Intact | RN: N°000085 | Mouadh BEN AZIZA | Customer return | 15/05/2026 | Rejected |
Return nature
- Intact Resalable → reintegrated into sellable stock.
- Defective Damaged → tracked separately, not put back up for sale.
Note statuses
- In progress Entered, awaiting validation.
- Validated Confirmed → stock reintegrated.
- Rejected Refused → no stock impact.
On validation of an intact return note, Swifto can allocate the quantities across the appropriate stocks / batches / expiry dates (advanced stock), or put everything back into the originating seller's stock. Fine-grained batch management depends on the company's stock mode.
Sales reports
Sales reports consolidate what the seller has reported from the field: the sales made at each customer, but also the non-sales (visit without a sale) with their reason. It is the tool for tracking route performance, by seller and by customer.
| ● | Sale⇅ | Seller⇅ | Customer code⇅ | Customer⇅ | Date⇅ | Nature | ||
|---|---|---|---|---|---|---|---|---|
| Sale | Mouadh BEN AZIZA | CL-0142 | EL MAZRAA | 18/05/2026 | Direct sale | |||
| No | Mouadh BEN AZIZA | CL-0207 | ÉPICERIE CENTRALE | 18/05/2026 | Customer absent | |||
| Sale | Ayatollah ORABI | CL-0331 | SUPÉRETTE LE BON PRIX | 18/05/2026 | Direct sale |
| Column | Description |
|---|---|
| ● / Sale | Green dot = sale made; red dot = visit without a sale. |
| Seller | Field seller who made the visit. |
| Customer code / Customer | Customer visited (reference and company name). |
| Date | Date of the visit / sale. |
| Nature | Type of sale if a sale; reason for non-sale otherwise (customer absent, refusal, etc.). |
The PDF and Excel buttons export the filtered report (by seller / period) — handy for an end-of-day debrief or a weekly follow-up.
Customers by seller (territories)
This screen defines each field seller's portfolio: you attach customers (or customer groups) to a seller. It is the basis for splitting into territories: on mobile, each seller only sees the customers assigned to them.
| Seller (field seller)⇅ | Customer group⇅ | Action(s) | |
|---|---|---|---|
| Mouadh BEN AZIZA | Grand Tunis Territory | ||
| Ayatollah ORABI | Sahel Territory | ||
| Slim TRABELSI | Sfax-Nord Territory |
Assigning by customer group lets you manage a territory in a single action. Combine this screen with Visit scheduling (section 3) to turn a territory into a dated route.
Swifto Seller mobile app
The back office (this interface) and the field communicate via the Swifto Seller mobile app, installed on the seller's smartphone / terminal. Synchronization moves data in both directions: the load goes down to mobile, sales and returns come back up to Swifto.
Back office → Mobile
- Issue notes (stock carried onboard)
- Assigned customers & scheduled visits
- Item catalog & price lists
Mobile → Back office
- Field sales & payments collected
- Unsold goods (return notes)
- Sales & non-sales reports
- Route GPS position
The colored dot of an issue note (section 4) directly reflects the status of this synchronization: blue (in preparation, not yet sent), orange (sent, pending on the mobile side), green (successfully received on the terminal). As long as a note is not green, the seller does not see it yet.
Lifecycle (workflow)
flowchart LR P([Visit
scheduling]):::s --> C[Issue note
Truck loading]:::p C --> SY[(Mobile sync
Swifto Seller)]:::st SY --> T[Route /
Customer visits]:::p T --> V([Field sales]):::ok T --> N([Non-sales
+ reason]):::ko V --> R[Return note
Unsold goods]:::p N --> R R --> S2[(Stock reintegrated)]:::st V --> RP[Sales report]:::p N --> RP classDef p fill:#FFFBEB,stroke:#F59E0B,color:#92400E; classDef s fill:#F5F3FF,stroke:#8B5CF6,color:#5B21B6; classDef st fill:#FEF3C7,stroke:#D97706,color:#92400E; classDef ok fill:#D1FAE5,stroke:#10B981,color:#065F46; classDef ko fill:#FEE2E2,stroke:#EF4444,color:#991B1B;
Scheduling → Loading → Mobile sync → Route & sales → Return of unsold goods → Report.
Business rules
Stock travels with the seller — the issue note transfers goods from the warehouse to the seller's onboard stock. Whatever is neither sold nor returned remains considered "on route".
Synchronization required — an issue note can only be used by the seller once synced (green dot). A blue/orange dot signals that it has not yet reached the terminal.
Intact return = sellable stock — validating an intact return note reintegrates the quantities into sellable stock. A defective return is tracked separately and is not put back up for sale.
Scope siloed by seller — a seller only sees the customers assigned to them (Customers by seller). Assignments, territories and routes determine what comes back up in their reports.
Roles & permissions
| Action | Field seller | Sales supervisor | Warehouse | Admin |
|---|---|---|---|---|
| Schedule visits | — | ✅ | — | ✅ |
| Assign customers / territories | — | ✅ | — | ✅ |
| Create the issue note | — | ✅ | ✅ | ✅ |
| Sell in the field (mobile) | ✅ | — | — | — |
| Enter / validate a return | — | ✅ | ✅ | ✅ |
| View reports | — | ✅ | ✅ | ✅ |
| Delete | — | — | — | ✅ |
Indicative matrix — each action depends on the privileges (create / edit / delete) defined on your company's profiles.
FAQ & real-world scenario
Scenario — a day on the route
- 17:00 AM — Scheduling. The supervisor has scheduled Mouadh's route: 6 customers in the Grand Tunis territory for the day.
- 27:30 AM — Loading. The warehouse creates an issue note: 80 packs of water, 40 crates of juice, 200 yogurts (value ≈ 4,200.000 TND). Orange dot then green after sync.
- 38:30 AM–4:00 PM — Route. Mouadh sells at 5 customers via Swifto Seller (≈ 3,650.000 TND collected); 1 customer absent → non-sale with a reason.
- 44:30 PM — Return. Back at the depot, an intact return note reintegrates 12 unsold packs and 30 unsold yogurts; 4 damaged yogurts → defective return note.
- 55:00 PM — Report. The supervisor reviews the day's sales report, exports the PDF and prepares tomorrow's route.
The seller doesn't see their load on mobile?
Check the dot on the issue note: as long as it is not green (synced), the note has not reached the terminal. Restart the synchronization on the app side.
A customer doesn't appear in a seller's route?
It is probably not assigned to that seller. Open Customers by seller and attach the customer (or their group) to the right seller.
Tip — save time on loading
Create issue note templates (Settings) for recurring loads: a single click is then enough to reload a standard truck, day after day.