Operations and exception console

Placeholder console for order exceptions, route recovery, delivery watch, and downstream sync health.

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.

Order exceptions

Surface blocked orders, pricing mismatches, and inventory conflicts before route closeout.

This queue should eventually join visit state, draft orders, customer terms, and warehouse availability in one operator view.

Track loads that slipped, partial drops, and proof-of-delivery follow-up.

The first implementation should focus on route release, stop completion, and manual exception recovery with audit logging.

Monitor pushes into ERP, accounting, and inventory systems after field activity lands.

Do not rely on third-party job history alone. Persist normalized sync attempts and outcomes in the application database.

Give operators one place to see missed stops, stranded drafts, and route notes that need intervention.

This surface should become the operational bridge between route execution, customer support, and dispatch.