Field Sales CRM Built to Process 10 Million Orders Across 5 Tobacco Sales Territories

Why Tobacco Field Sales Cannot Scale on Paper Order Pads and Spreadsheets

A field sales operation managing 500 representatives across 5 national territories cannot coordinate product ordering, inventory visibility, promotions execution, and customer management through paper order forms, WhatsApp, and shared spreadsheets. Without a centralised system, sales managers have no real-time visibility into rep activity, reps have no current product availability data when they are in front of a retailer, and the back office has no reliable order record until the rep returns to the office. The gap between visit and entry creates order errors, missed promotions, and delayed fulfilment.

The tobacco distributor approached AppMatic Tech with a specific operational brief: replace the field order-taking process with a system where every rep carries a complete, real-time product catalog on their device, can create and submit orders on-site at the retailer, and can see which promotions to pitch during the visit. Managers needed territory-level reporting without waiting for daily call reports. The admin team needed product catalog control, pricing management, and promotion scheduling without developer involvement.

AppMatic Tech built the complete field sales CRM from scratch: product catalog engine, order management module, inventory and promotions layers, customer management, territory-level reporting, and a role-separated admin panel, all deployable as a web application accessible from any tablet or laptop the field rep carries.

How a Purpose-Built Field Sales CRM Compares to Generic Sales Platforms

Generic CRM platforms manage leads and pipelines. Field sales platforms for FMCG and CPG distribution manage physical visit-based order-taking, live product catalogs, SKU-level inventory, and promotion execution at the point of sale. AppMatic Tech's purpose-built system delivers the exact workflow tobacco field sales operations require, without the configuration overhead of adapting a generic CRM to an order-taking use case.

What AppMatic Tech Built

AppMatic Tech designed and built a seven-module field sales platform covering the complete sales rep workflow: from opening the product catalog at a retailer visit through order submission, inventory check, promotions execution, and manager reporting.

Product Catalog Engine

A real-time browsable product catalog with category and subcategory filtering (Papers, RYO, Pipe, Real, Tubes, Various), Promotional vs Non-Promotional product classification, and SKU-level product records with images and descriptions. Admin manages the full catalog including pricing, SKUs, category assignments, and product availability without developer involvement.

Field Order Creation Module

Field sales reps browse the live catalog, select products with quantity inputs, and submit orders directly from the retailer location. Orders are associated with the rep's assigned customer record and territory. Order submission is confirmed in real time against the backend, and the rep receives an order reference before leaving the retailer.

Inventory Management

Stock levels are visible to reps at order creation time, so reps see current availability for each SKU before committing to an order quantity, eliminating back-orders caused by reps promising quantities the warehouse cannot fulfil. Admin manages stock adjustments, receipts, and low-stock thresholds from the admin panel.

Promotions Management

Admin configures promotional campaigns with product inclusions, validity windows, and discount or bundle rules. Field reps see active promotions highlighted in the catalog during a visit, with clear Promotional vs Non-Promotional classification on every product card. Promotions are applied automatically to qualifying orders at the time of submission.

Customer and Territory Management

Each field rep manages an assigned portfolio of retailer customers within their territory. Customer records hold contact information, visit history, order history, and outstanding balance. Territory assignment is managed by admin, and all reporting is grouped by territory for regional manager visibility.

Sales Reports and Manager Dashboard

Territory managers see real-time sales performance by rep, by product category, and by customer. Order volume reports, conversion tracking by rep, and product mix analysis are available across configurable date ranges with CSV export. Rep activity (visits logged, orders submitted) is visible at the territory level without requiring manual call reports.

Role-Separated Admin Panel

Admin users manage the product catalog, pricing, promotions, territory assignments, and user accounts without developer access. The RBAC model separates Super Admin, Territory Manager, and Field Sales Rep roles with API-level enforcement, ensuring territory managers see only their territory's data, and reps see only their assigned customers.

Delivery Metrics

Orders Processed

10M+

Field Sales Reps

500+

Sales Territories

5

Interface Design

The field sales interface required two distinct design modes: a rep-facing product catalog and order flow designed for speed and minimal input errors during a live retailer visit, and a manager and admin dashboard designed for data density and reporting clarity. AppMatic Tech applied the Engineer-Paired Design Protocol across both modes, with every screen reviewed for technical feasibility before finalisation, eliminating redesign cycles after development began.

"Before this system, our reps were writing orders on paper and calling in quantities at the end of the day. Now every order is submitted in real time at the retailer, the rep knows what is in stock before they commit to a quantity, and managers have territory reports without asking anyone for a call report. The promotions module alone changed how our reps pitch during a visit."

Head of Sales OperationsNational Tobacco Distributor

Platform Specifications

Tech Stack

React

Frontend framework for the rep and admin interfaces

Laravel

Backend API and business logic layer

PHP

Backend server language

MySQL

Relational database for orders, products, customers, and territories

AWS

Cloud infrastructure and hosting

Tailwind CSS

Frontend styling utility layer

Node.js

Build tooling

Redis

Session management and caching

Security and Operational Standards

A field sales platform where 500 representatives access customer data, pricing, and order history across 5 territories requires strict data isolation, audit logging, and access control designed for distributed field operations.

• API-Layer RBAC Enforcement

  RBAC access control is enforced at the Laravel API middleware layer on every authenticated request. Territory managers access only their territory's orders, customers, and rep activity, with no cross-territory data leakage possible through direct API calls.

• Immutable Audit Log

  Every order submission, status update, and product catalog change is written to an immutable audit log with timestamp, actor user ID, and actor role. Dispute resolution and order reconciliation are fully auditable without relying on rep memory or paper records.

• Server-Side Pricing Enforcement

  Product pricing and promotional discount rules are stored server-side and applied at order submission by the backend, not the client. Reps cannot modify prices or discount percentages from the field interface.

• Offline Order Queuing with Deduplication

  Offline order queuing allows reps in low-connectivity areas to compose orders locally and submit them when connectivity is restored, with server-side deduplication preventing duplicate submissions on reconnect.

• AWS Infrastructure Sizing

  AWS infrastructure is sized to actual field usage patterns, with RDS read replicas serving the catalog browsing load independently of the order write path, preventing catalog slowdown during peak ordering windows.

How AppMatic Tech Approached This Build

1. Field Sales Workflow Discovery

   AppMatic Tech mapped the existing order-taking process end-to-end: how reps visit retailers, how they communicate product availability, how orders are submitted and processed, and how managers track territory performance. The database schema and module boundaries were defined from this mapping before any development began.

2. Product Catalog Architecture

   AppMatic Tech designed the category and subcategory taxonomy (Papers, RYO, Pipe, Real, Tubes, Various), the Promotional vs Non-Promotional classification model, and the SKU record structure to support the admin's existing product management workflow without requiring reps to change how they think about the catalog.

3. Order Management and Customer Module

   AppMatic Tech built the rep-facing order creation flow, customer portfolio assignment, territory grouping, and order history. Order submission was tested under concurrent rep load before the promotions and inventory modules were added on top.

4. Inventory and Promotions Layer

   AppMatic Tech built real-time inventory visibility into the catalog browse flow, low-stock indicators, and the promotions engine with validity window enforcement and automatic discount application at order submission. Promotion rules were validated against the client's existing promotional campaign structure.

5. Territory Reporting and Manager Dashboard

   AppMatic Tech built territory-level performance reporting, rep activity views, product mix analysis, and CSV export. Reports were validated against the client's existing manual reporting outputs before sign-off.

6. Admin Panel and Deployment

   AppMatic Tech built the admin catalog management, pricing control, territory assignment, and user management modules, then conducted UAT with admin users and field reps from two territories before production deployment to AWS.