The Salesmen portal is a streamlined experience for reps who work outside the full CRM UI — mobile-friendly lists, quick capture, territory-scoped data, and offline order taking.
Please note:
- Reps only see records their role and territory allow — the same RBAC model as the main app; see Roles, permissions, and RBAC.
- Lead capture in the portal feeds the same pipeline as Create and manage leads in the full CRM.
- Without a checked-in customer, Orders history lists only shops on the salesman’s active assigned routes — not every order ever attributed to them.
Portal capabilities
| Area | Rep can | Admin configures |
|---|---|---|
| Leads | View and update assigned leads | Pipeline stages, required fields |
| Customers | Browse accounts in territory | Zone, route, and ownership rules |
| Orders | Place or review orders; queue offline | Product catalog, price lists |
| Carts | Keep up to 30 active carts; checkout retires the used cart | Catalog and credit rules |
| Offline data | Download route catalogs, sync outbox | Route assignments, portal access |
| Activity | Log visits and notes | Interaction types — syncs to Track interactions |
| Dashboard | See quotas and today’s tasks | KPI widgets — pair with Pulse for stale-lead review |
Enable the portal
- Confirm Salesmen module is enabled under Settings → Modules
- Create or edit a role with portal-appropriate permissions (for example
leads.read_own,orders.write) - Assign the role to field users and active routes
- Share the portal URL or add it to mobile home screen
Offline mode and order outbox
Field coverage often has weak connectivity. Use Offline data in the portal shell to prepare the device before a beat:
- Open Offline data
- Download / refresh catalog & images for customers on assigned routes
- Optionally Switch to offline mode so the app works from cached data and queues orders locally
- When back online, Sync offline orders from Offline data or the Orders list
| Signal | Meaning |
|---|---|
| Offline mode on | App prefers device cache; new orders go to the local outbox |
| Connection slow | Network is up but latency is poor — offline mode often feels faster |
| Pending outbox | Orders waiting to upload |
| Rejected outbox | Server rejected a queued order — open it from the Orders list to fix |
The portal remembers a confirmed session for cold starts so reps are not bounced to login after a brief disconnect. Hung requests time out instead of freezing the UI.
flowchart LR
Prep[Download catalogs] --> Beat[Take orders on route]
Beat --> Outbox[Local outbox]
Outbox --> Online{Back online?}
Online -->|Yes| Sync[Sync outbox]
Sync --> CRM[Central orders / Sage]
Orders and carts
- Checked in to a customer — order list is for that shop.
- Not checked in — history is limited to FMCG customers on the salesman’s active routes.
- After checkout, the cart used for the order is removed from the active list (it is not left as an empty cart for the same customer).
- A salesman can keep up to 30 active carts in the stacked-cart UI.
Typical day flow
flowchart LR Start[Sign in to portal] --> Today[Today's visits and tasks] Today --> Prep[Optional: refresh offline catalogs] Prep --> Visit[Log customer visit / check in] Visit --> Order[Create or amend order] Order --> Sync[Sync outbox if offline] Sync --> Manager[Manager visibility in reports]
Pair the portal with Logistics and live map when dispatch needs to see rep location or route progress. Keep FMCG customer status and routes current under Vendors and FMCG customers. Qualified opportunities should stay aligned with Work with deals and pipelines after order capture. Customer-facing access uses the separate Customer portal.