
Platform Screenshots

Overview
PJP Online supports field sales teams with a mobile-first workflow for activity planning, execution, and reporting.
Business Problem
Distributed teams need practical tools that work in the field and give management a reliable view of execution. Manual updates and scattered reports slow down decisions.
Solution
PJP Online structures field activity, captures sales-team updates, and gives managers better visibility into daily execution.
Organization and Customer-Store Structure
The platform organizes group teams, branches, product divisions, sales users, and customer stores. Store records include location and QR identity so assignments, visit plans, and reporting can follow the operating hierarchy.
Offline and Reporting Design
SQLite/local storage supports selected field records, periodic synchronization, retries, and explicit conflict handling. Management reporting covers visit effectiveness, sales activity, compliance evidence, and PDF exports without presenting those measurement fields as achieved improvements.
Implemented Operational Effects
- Recurring schedules, assignment, calendar, and reminder workflows.
- GPS/radius validation, QR check-in, photos, duration, and device/network visit evidence.
- Customer-store records organized by group, branch, area, and product division.
- Onsite and online orders across a documented catalog of more than 40,000 items.
- SQLite/local storage, periodic synchronization, retries, conflict handling, and management reports.
Evidence Statement
The project documentation supports the listed workflows and a catalog of more than 40,000 items. It does not provide approved figures for sales growth, time saved, or visit compliance.
Technical Implementation Logic
| Layer | Choice | Rationale |
|---|---|---|
| Mobile App | Flutter | Delivers responsive maps and dynamic routing interfaces for field agents across various device models. |
| API Backend | Laravel | Mature framework with out-of-the-box routing, secure request handling, and robust geofencing check-in validation. |
| Database | MySQL / MariaDB | Relational integrity for storing visit schedules, location coordinates, and team performance metrics. |
Frequently Asked Questions
Can field teams keep working without reliable signal?
Selected workflows use local storage, periodic synchronization, retries, and conflict handling. Exact offline behavior depends on the record type.
Are sales or compliance improvements published?
No approved sales-growth, time-saving, or visit-compliance figures were available, so the page reports implemented workflows only.
Technology Used
Flutter mobile interfaces, backend APIs, MySQL/MariaDB, and dashboard reporting.
