Amazon DSP Dashboard

This repository is the single source of truth for CJMK DSP operations software.

Canonical repo: https://github.com/ckknighten-cjmk/amazon-dsp-dashboard

Path	App	Stack
Repository root	CJMK Ops — daily HQ for CJMK Inc. / DNA4 Memphis	Next.js App Router
apps/morning-dispatch	Earlier Vite command center, including the Morning Dispatch Readiness Center	Vite + React

Live CJMK Ops seeds come from Amazon DSP Console: the Week 38 scorecard (Sep 13–19, 2026, with Week 37 still on the scorecard switcher), the 2026-10-30 Delivery Execution board, the Week 38 10-hour bonus list, and the Week 38, Week 39, and Week 41 schedule workbooks used by Compliance. Fleet and incidents in CJMK Ops are still mock fixtures. Do not invent metrics that Console did not publish.

CJMK Ops (repository root)

Operations HQ for CJMK Inc., an SDVOSB Amazon DSP running last-mile out of station DNA4 (Memphis, TN). Station managers and owners can open it daily to see performance, routes, drivers, fleet, incidents, and Amazon-style scorecard health.

This is a demo app. It does not call Amazon APIs and does not require credentials.

Run

npm install
npm run build
npm run dev

npm ci uses the lockfile and is what CI should run. Then open http://127.0.0.1:43123.

Script	What it does
npm run dev	Next.js App Router dev server on port 43123
npm run build	Production build
npm start	Serve the production build on 43123

No auth in v1. Dark theme is the default; toggle light/dark from the top bar or Settings.

Refresh

Every dashboard page has a Refresh control in the page header, next to that page's seed as-of time. It does two things:

1. POST /api/refresh with { page, station, week?, date? } so an external job can pull a newer Console or ADP capture. station defaults to DNA4 when it is omitted. The same page and station cannot start another pull for 10 minutes; a different station is its own limit. The app does not call Amazon or ADP itself.
2. router.refresh(), which re-reads the seed modules already in this build.

The webhook key never goes to the browser. Set these on the server:

Variable	Required	Purpose
REFRESH_WEBHOOK_URL	yes	URL that receives the JSON body.
REFRESH_WEBHOOK_KEY	yes	Secret sent with that request.
REFRESH_WEBHOOK_KEY_HEADER	no	Header name for the key. Defaults to Authorization, and that header's value is Bearer <key>. Any other name sends the raw key.

If REFRESH_WEBHOOK_URL or REFRESH_WEBHOOK_KEY is missing, POST /api/refresh returns 503 and the button only re-reads the current seeds. The same page and station cannot start another pull for 10 minutes; a repeat returns 429 with lastRequestedAt. Copy .env.example for placeholders. Do not commit a real key.

After a pull is accepted the header says Pulling fresh data… usually 5–15 min. That note stays across reloads until the page's seed as-of time is newer than the request, which then shows Updated and that time. If 30 minutes pass with no newer seed, it shows Still waiting. Sign-in may be needed.

Page keys: overview (also Settings), routes (also a route detail page), drivers, fleet, scorecard, payments, compliance, bonus, incidents. week and date are sent when that page already has them.

Stations

The station list is src/lib/stations.ts. Each entry has a code, display name, and region. DNA4 (Memphis) is the default. WTN2 (West Tennessee) is the station opening soon.

The header Station menu is on every page. The choice is stored in the station query (?station=WTN2), the cjmk-ops-station cookie, and the localStorage key of the same name. Sidebar links, the period control, the scorecard week menu, and Refresh keep it. A missing or unknown value falls back to DNA4.

WTN2 has no capture. Every page shows No data for WTN2 yet, and the as-of line says No capture yet. DNA4 figures are not copied onto that station.

Add a station's first seed files

DNA4 files stay in src/lib/data/seed/. Put a new station's files in src/lib/data/seed/<code-lowercase>/ (WTN2 is src/lib/data/seed/wtn2/) and register one loader per dataset on STATION_LOADERS in src/lib/data/station-seeds.ts. Pages call loadStationDataset. Until that loader exists, the page stays on the empty state.

WTN2: {
  routes: () => buildWtn2Routes(),
}

The DNA4 callback already receives the page's week when a dataset has one ({ week }). A WTN2 loader receives the same argument.

Dataset	Loader key	What to add under src/lib/data/seed/wtn2/
Overview	overview	delivery-execution.json in the same shape as delivery-execution-2026-10-30.json
Routes and route detail	routes	that delivery execution file, plus the packages-exceptions CSV
Scorecard	scorecard	scorecard/weeks.json (the loader receives { week })
10 Hour Bonus	bonus	10hr-bonus.json (and the by-DA CSV if you keep one)
Drivers	drivers	Amazon schedule, ADP timecards, and the census file the roster reads
Fleet	fleet	amazon-fleet.json, dvic.json, and fleet-issues/issues-YYYY-MM-DD.json
Incidents	incidents	incidents.json
Compliance	compliance	weekly Amazon schedule, ADP timecard, and breaks JSON ({ week })
Payments	payments	settlements, variable invoice, and work summary JSON ({ week } for reconcile)
Settings	settings	no file; register when the settings form should use stationSettings for this station

DNA4 fleet issues stay in src/lib/data/seed/fleet-issues/. The Fleet page loads that catalog with loadStationDataset, and the New damage CSV and Excel include the station in the filename and a Station column. For WTN2, put the same dated files in src/lib/data/seed/wtn2/fleet-issues/ and register a fleet loader that calls loadFleetIssueCatalog on that directory. Until that loader exists, Fleet shows No data for WTN2 yet and does not read the DNA4 yard or the DNA4 issues snapshot.

CSV and Excel downloads put the station code in the filename and in a Station column. POST /api/refresh includes station.

Seeded data

Surface

Source

Routes / Delivery Execution

Amazon DSP Console Delivery Execution evening wrap for 2026-10-30 (~8:02 p.m. CT; 39 routes, 4 in progress, 35 complete, incomplete null, associates, stops, packages, board totals) plus the exception Packages CSV (161 rows). Board package-status chips use Console totals (remaining 61, reattemptable 8, undeliverable 12, missing 12, RTS 39, pickup failed 92). The CSV and the embedded exception rows are the same 161 rows. Export statuses are reattemptable 7, undeliverable 12, missing 10, returned to station 40, pickup failed 92. Reattemptable, missing, and returned to station differ from the board chips (7 / 10 / 40 export rows versus 8 / 12 / 39 on the chips). Remaining is a board chip and is not an export status. Route-row packages are 11,246 delivered of 11,309 planned. Per-route packages remaining sums to 63 (CX285 14, CX271 11, CX276 13, CX257 4, CX263 7, CX279 2, CX295 1, CX300 11). The board remaining chip is 61. Vehicle and on-time % were not on the Console board — the UI leaves them unavailable and does not invent them. Execution gauges were read from the visible board graphics (locations 99%, stops 99%, packages 99%, attempt success 99%). Console rescueActions is 0. A route is marked Rescue: Yes when it lists more than one associate (14 multi-transporter routes). The first associate is primary and the rest are rescuers. That column is not Amazon’s official rescue flag. Other board chips in the seed: unknown stops 28, work-hour risk 0, on break 0, no breaks taken 1, inactive 1, on-road pickups 5 (2 remaining, 3 complete), ahead 3, at risk 1, behind 0. The capture also includes weather delay 0, SWA eligible , SWA injected , and paused ; those stay in the seed file and are not separate board chips. In progress: CX285 (93/102 stops, route row marked 9 behind), CX271 (189/196, 3 ahead), CX276 (192/199, 5 ahead), and CX257 (193/197, 32 ahead). Status is in progress per the board (those four routes); the other 35 routes are complete. The behind chip is while CX285’s route row is marked 9 behind. Incomplete was on the capture and is shown as unavailable. Oct 29 is also seeded (40 routes, 2 in progress, 3 not departed, 116 exception rows) and Oct 28 stays in the catalog.

Station clock is frozen at Fri Oct 30, 2026 · 8:02 p.m. CT (the evening-wrap Console capture time).

Pages

• Overview — KPIs from the Oct 30 evening-wrap Delivery Execution board (package gauge 99%, remaining 61 / reattemptable 8 / undeliverable 12, 4 in-progress routes). Package delivered counts are the sum of Console route rows (11,246 of 11,309). No prior-day deltas. Incomplete was null on that capture.
• Scorecard — DSP Console Week 38 (default): overall 84 Fantastic, plus Safety, Quality, and Service Reliability metrics. Week 37 (85.8 Fantastic) stays on the week switcher. The top-bar period shows a week only when it overlaps that Console week. CSV export uses the values shown for the selected week. Prior week stays “Not shown in Console.”
• 10 Hour Bonus — Week 38 delivery associates on routes with 180 or more completed stops. 100 solo DAs have a clear route total. 115 multi-transporter rows stay flagged: the stop count is the route total, and Amazon did not say which DA completed those stops, so it is not split. CSV and Excel are associate-first (date, deliveryAssociate, stopsCompleted, then route). The table hides days outside the selected period.
• Routes — Evening-wrap Delivery Execution board: 39 routes, gauges 99/99/99/99%, package-status chips (remaining 61, reattemptable 8, undeliverable 12, missing 12, RTS 39, pickup failed 92), work-hour risk 0, on-road pickups 5 (2 remaining, 3 complete), the 161-row exception-package export, and a Rescue column for 14 multi-associate routes. The behind chip is 0 while CX285 is marked 9 behind. CSV downloads sit next to the routes and exceptions tables.
• Drivers — Full Weeks 38–39 schedule roster, plus ADP-only names, with Oct 30 route activity merged by name. Census phone and email attach on a unique name match. The page opens on Active. CSV export downloads the full roster, including blank phones.
• Fleet — 53 DNA4 vehicles from Console My vehicles. CSV export is fleet-vehicles-dna4-console.csv. Year and mileage stay blank. DVIC pairs pre-trip and post-trip for the same vehicle and service day and marks post-trip damage the pre-trip did not list. The Oct 15 morning dashboard capture publishes 0 pre-trip, 0 post-trip, and 0 AVI post-trip, with empty inspection lists, so the count cards show those totals and no vehicle pairs are compared. The Oct 14 file remains 44 / 44 / 10. The Sep 23 file remains 0 / 0 / 0. CSV export downloads the pairs (header only on this capture). New damage reads the newest file in src/lib/data/seed/fleet-issues/, (1247 open issues, 0 inspection defects created 2026-10-15). stays for comparison. WTN2 has no fleet capture, so that page stays on the empty state.

The sticky top bar Today / This week control drives Overview KPIs. Today stays the Oct 30 evening wrap. This week charts every seeded day in Oct 24–30 (Oct 26, Oct 27, Oct 28, Oct 29, and Oct 30). A custom period opens the seeded days inside that range. Days without a file stay blank.

Swap mock / seed data for live sources later

Keep the TypeScript models in src/lib/types.ts. Pages import only from src/lib/data/index.ts.

1. Implement the DataSource interface in src/lib/data/index.ts (CSV, spreadsheet export, or your own API).
2. Point export const source at that implementation instead of mockDataSource.
3. Leave seed files under src/lib/data/seed/ as fixtures for local demo.

Console snapshots used here live at:

• src/lib/data/seed/delivery-execution-2026-10-30.json — live Delivery Execution evening wrap
• src/lib/data/seed/packages-exceptions-2026-10-30.csv — Packages export for that wrap (161 rows)
• src/lib/data/seed/delivery-execution-2026-10-29.json — earlier Delivery Execution evening wrap, kept in the repo
• src/lib/data/seed/packages-exceptions-2026-10-29.csv — Packages export for that earlier wrap (116 rows)
• src/lib/data/seed/delivery-execution-2026-10-28.json — earlier Delivery Execution evening wrap, kept in the repo
• src/lib/data/seed/packages-exceptions-2026-10-28.csv — Packages export for that earlier wrap (149 rows)
• src/lib/data/seed/delivery-execution-2026-10-27.json — earlier Delivery Execution evening wrap, kept in the repo
• src/lib/data/seed/packages-exceptions-2026-10-27.csv — Packages export for that earlier wrap (125 rows)
• — earlier Delivery Execution evening wrap, kept in the repo

Do not put Amazon credentials in this repo. Do not scrape Seller Central / DSP consoles from the app.

Scorecard

The Scorecard page encodes live DSP Console Performance Summary values for CJMK Inc. / DNA4. Week 38 (Sep 13–19, 2026) is the default. Overall standing 84 Fantastic. Week 37 (Sep 6–12, 2026) remains at 85.8 Fantastic. No prior-week comparison was published in either summary, so the UI does not invent deltas.

Fantastic / Great / Fair / Poor numeric bands on each tile are still illustrative. Badges match the standing Amazon displayed. On Week 38 that includes Delivery Completion DPMO Great (4,166.9), CDF DPMO Great (1,360), POD 99.46%, tenured workforce 94.01%, compliance Compliant, and No Data metrics. Bands that would grade a Week 38 value differently from Amazon’s tier are hidden.

Stack

Next.js App Router, TypeScript, Tailwind CSS v4, shadcn/ui, lucide-react, Recharts.

Morning Dispatch (apps/morning-dispatch)

The Vite + React operations command center that already lived on main — Morning Dispatch Readiness Center, live operations, fleet readiness, scorecard intelligence, workforce, and the rest — is preserved under apps/morning-dispatch. Its package.json, src/, public/, and configs are unchanged aside from the move. Its own notes are in apps/morning-dispatch/README.md.

Run

cd apps/morning-dispatch
npm install
npm run build
npm run dev

npm ci works the same way from that directory. Open http://localhost:5173 and sign in with a demo role. Password for every demo account is demo.