MySalesRoute command center

This first pass resets the scaffold around route sales, field execution, delivery coordination, and Neon-backed account access.

System slices

Route planning, field execution, order capture, delivery visibility, and account access.

Auth status

Neon Auth is configured for sign-in and account flows.

Execution lanes

The product is split into app routes for operators, reps, and dispatchers, with typed modules for route, order, and sync boundaries.

Mobile-first field flow

Start with account access, route visibility, visit execution, order capture, and delivery exceptions before deeper analytics.

Platform boundaries

Auth, route planning, order submission, delivery status, and downstream sync are isolated behind explicit contracts in `lib/`.

The scaffold is aimed at the first reliable field-to-fulfillment loop, not the full ERP surface.

Accounts, routes, visits, and orders live in the Next.js app shell.
Dispatch, delivery, and integration work is modeled as explicit async boundaries.
Neon Auth is the planned identity layer for rep and operator access.
The first build should prioritize execution clarity over broad feature coverage.

Define daily territory coverage, stop sequencing, and rep assignments before the field team rolls out.

This belongs in the synchronous app path and should become a planner view backed by territory, customer, and inventory data.

Track visit completion, order capture, notes, and exception handling from a mobile-first workflow.

The first implementation should support route progress, quick order entry, and missed-stop follow-up without requiring a heavy admin surface.

Move approved orders into delivery runs, then persist normalized downstream sync state for operations.

Async workflows should handle release, delivery exceptions, and external system sync while Postgres remains the source of truth.

These are the concrete follow-ons after the reset.

Prisma schema for accounts, route plans, visits, order drafts, delivery runs, and sync audits.
Neon Auth session wiring and account-aware layouts for reps and operators.
Dispatch and fulfillment workflows for route release, stop completion, and delivery exceptions.
ERP or accounting integration boundary for downstream sync once database credentials exist.

The workspace was bootstrapped from the requested shadcn preset.