Projects
Special automation projects hosted on Jingles.
Process Orders
Upload the customer order file and shop file to start, or open a saved run to review it.
Internal remarks — salesperson note to ops (internal only)
Drop or click to upload
.xlsx / .csv
Drop or click to upload
.xlsx / .csv
Needs SKU + franchise databases loaded for accurate weight/CBM and flags.
Reports
Order history by stage: reviewed, routed, confirmed in Operator, plus non-Ninja leads.
Franchise Database
Key: Branch ID = 门店编码 (one record per store) · Shipper ID = 客户编码 (0 records)
| Shipper ID | Branch ID | Branch Name | Status | Payment Cycle | KAM | Province | Pricing-Rate | Pricing-Min X | Delivery | VAS Items | Actions |
|---|
SKU Database
Key: SKU id = 物料编码 / Product Code (0 records)
| Product Code | Name | Category | Unit | Weight (KG) | CBM | Actions |
|---|
Special Treatment
Dedicated-trip revenue captured from review submissions (0 trips).
Billing
Monthly revenue by route date, for routes marked completed in Operator. Box qty × box rate (province × fuel), trip rate (franchise × fuel, merge logic), VAS, helper, and special trips.
Access Control
Assign users to projects, set their role, and suspend or remove access.
| Role | Status | Actions |
|---|
Fleet
OFM drivers registered through the LINE app, and the vendors they can be assigned to.
| Name | Phone | Vehicle | Plate | LINE Name | Display Name | Registered | Actions |
|---|
Vendors are the shared operator/billing records — the same DB. Admin/onsite can add one here (no separate operator sync needed); a new vendor is immediately assignable to a driver in the driver editor and payable in a release.
| Company | Tax ID / DBD | Legal type | Bank | Contact | AP master |
|---|
| Driver | Type | Dates | Days | Note | Photo | Actions |
|---|
Address Collection
Invoice barcodes scanned by drivers, with the GPS location captured at scan time.
0 record(s)
| Delivery Date | Invoice no. | Lat | Long | Location Detail | Delivery Window | Service Time | Driver Display Name | Map |
|---|
Performance
Unique invoices scanned per driver. The top-10% target (P90) is the score a driver needs to reach the top tier — the same target shown in the driver app.
| Rank | Driver | Unique scans | Tier |
|---|
COD Collection
Every cash-on-delivery invoice, the slip the driver banked it with, and what the OCR read off that slip. Invoices covered by one slip appear as a single row — one photo, one decision.
0 row(s)
| Route date | Invoice no. | Recipient | Driver | Citizen id | COD amount | OCR read | Slip | Status | Action |
|---|
Driver Payslips
Loading…
Publish a weekly batch
One row per driver per work day. Drivers are matched by เลขบัตรประชาชน — if any ID has no driver, nothing is published.
— the exact column order the importer reads.
Publish an unpaid estimate
Drivers see this under “ยังไม่จ่าย”, banner-marked as an estimate, with the problematic invoices called out above the breakdown — those are the bills that can still cut their pay.
Drivers can raise disputes until 17:00 (ICT) on this day; ops can still clear after.
— the payslip columns without the ROUND block, plus “วันที่ทำจ่าย” and “Problematic invoices”.
| Period | File | Cut-off | Drivers | Rows | Uploaded | Status | Action |
|---|
| When (ICT) | Action | Driver | Period | Net after tax | By |
|---|
Payment requests
Advance requests drivers submitted for the selected week. Recorded only — finance pays & reconciles offline. Per-driver enable/day/cap lives in the driver editor (Fleet).
| Submitted (ICT) | Driver | Amount | Note | Status | Action |
|---|
Open driver disputes
Drivers contest a problem bill on their unpaid estimate. Clear each one before its cut-off (17:00 ICT on the shown day) — you can still clear after, but new disputes are blocked then. Export covers open and settled.
Click a driver to open the slip exactly as their LINE app shows it.
Capacity Planning
Who is on the roster, which zones and truck codes they hold, and who is in this week.
| Driver | Type | Zones | Truck codes | Max |
|---|
Order Allocation
Group a delivery day's orders by truck code, then allocate them down the ladder: รถประจำ before รถเสริม, primary code before secondary, zone as the fallback.
Demand vs capacity by zone
| Zone | Orders | Codes | Confirmed | + รอ CF | Short | Drivers |
|---|
Gate Log
Who arrived, who drove out, on which truck code, carrying which bills — and where that disagrees with the plan.
Control Tower
Core fleet · last-seen location, pending work & ETA to next drop.
Drivers