Manual Sales reports
The sales reports consolidate what the seller feeds back from the field via Swifto Seller: the sales made at each customer, but also the no-sales (visit without a sale) and their reason. It is the tool for managing performance by seller and by route.
Overview
Every visit made in the field generates a report row: either a sale (the customer bought something), or a no-sale (visit made without a purchase) accompanied by a reason (customer absent, refusal, shop closed…). By aggregating these rows, the supervisor measures the visit rate, the sales rate, and identifies customers to follow up with.
Business goal
- Track sales by seller / route
- Understand no-sales (reasons)
- Measure the customer coverage rate
- Export for the debrief
Target audience
- Sales supervisor — analyzes performance
- Sales management — manages the territories
- Seller-field seller — feeds the report (mobile)
Position within the module
Reports close out the cycle: Planning → Loading → route → Return → Report. Module overview: Van Sales module.
Access and navigation
Left-hand side menu: Field seller → Sales reports.
The screen is based on the rapportVente page. Reports are automatically populated via mobile sync — no manual entry in the back office.
List of reports
The page lists the visits fed back from the field: a dot (green = sale, red = no-sale), the seller, the customer visited, the date and the type (sale type or no-sale reason).
| ● | 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 | CENTRAL GROCERY | 18/05/2026 | Customer absent | |||
| Sale | Ayatollah ORABI | CL-0331 | GOOD PRICE MINI-MARKET | 18/05/2026 | Direct sale |
Table columns
| Column | Description |
|---|---|
| ● / Sale | Green dot = completed sale; red dot = visit without a sale. |
| Seller | Seller-field seller who made the visit. |
| Customer code / Customer | Customer visited (reference and company name). |
| Date | Date of the visit / sale. |
| Type | Sale type if a sale; no-sale reason otherwise. |
Sale vs No-sale
Every visit has an outcome. This distinction is what makes it possible to measure the productivity of a route.
Sale
The customer made a purchase during the visit.
- Green dot, "Sale" row
- Amount and items sold attached
- Type = sale type (direct…)
No-sale
Visit made, but without a purchase.
- Red dot, "No" row
- Reason mandatory (absent, refusal…)
- Logs coverage (visit still made)
A no-sale is not a failure to hide: its reason informs management (stockouts, price, competition, opening hours) and guides corrective actions.
Report detail
View
ReadThe magnifying-glass icon opens the detail: items sold, quantities, amount collected, timestamp and — for a no-sale — the reason entered in the field.
Location
GPSWhen available, the GPS position of the visit confirms that it did take place at the point of sale.
Related document
SaleA "Sale" row is linked to the sales document generated on the mobile (field receipt / invoice).
Filter by route / seller
The Search button opens the filters. Combine them to isolate a specific route.
By seller
Isolates the performance of a seller-field seller.
By period
Day, week or month of the route.
By outcome
Sales only, or no-sales to analyze.
The summary cards (Sales / No-sales / Rate / Revenue) recalculate based on the filters: handy for comparing two sellers over the same week.
PDF / Excel exports
PDF export
Nicely laid-out report, ready to print or send — ideal for an end-of-day debrief.
Excel export
Raw data for your pivot tables and weekly tracking by territory.
The exported content follows the filters: filter first (seller / period / outcome), then export — you only get the relevant rows.
Mobile sync
Reports are not entered in the back office: they flow in from Swifto Seller. Every time the seller closes a visit (sale or no-sale), a report row is created and synced.
Mobile → Back office
- Visit outcome (sale / no)
- Items & amount sold
- No-sale reason
- Timestamp & GPS
In the back office
- Consolidation by seller / route
- Calculated sales rates
- PDF / Excel exports
Lifecycle (workflow)
flowchart LR V[Customer visit
in the field]:::p --> D{Purchase?}:::s D -->|yes| W([Sale
green dot]):::ok D -->|no| N([No-sale
+ reason]):::ko W --> R[(Consolidated report)]:::st N --> R R --> E([PDF / Excel export
debrief]):::p 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;
Business rules
Read-only — reports are populated via mobile sync and are not edited in the back office: they faithfully reflect the field.
Reason mandatory on a no-sale — a visit without a sale requires a reason (entered on the mobile) to remain usable for analysis.
Coverage tracked — every visit (even without a sale) is logged: the customer coverage rate remains measurable, territory by territory.
Scope per seller — a report only contains the visits of the territory assigned to the seller (see Customers by seller).
Roles & permissions
| Action | Seller-field seller | Supervisor | Management | Admin |
|---|---|---|---|---|
| Feed (field, mobile) | ✅ | — | — | — |
| View reports | — | ✅ | ✅ | ✅ |
| Filter / analyze | — | ✅ | ✅ | ✅ |
| Export PDF / Excel | — | ✅ | ✅ | ✅ |
Indicative matrix — depends on the profiles defined in your company.
FAQ & Tips
A route doesn't appear in the reports?
Check that the mobile device has properly synced and that the filter's period / seller match.
Lots of "customer absent" no-sales?
Adjust the schedule of the route to the opening hours of the points of sale.
Tip — daily debrief
Export the report to PDF every evening, go over the no-sales with the seller, and get the next day's route ready right away.
