Tracking Menzzo

Purpose

tracking-menzzo is the order tracking application. It exposes customer-facing tracking, invoice, and delivery confirmation flows backed by operational order data.

Stack

• Laravel 12 and PHP 8.2-era application.
• Vite, Tailwind CSS, and Alpine-style frontend tooling.
• Customer-facing pages tied to order and delivery state.

Connected Projects

• Logidav provides order, shipment, and delivery truth.
• RDV Menzzo overlaps with appointment and delivery scheduling.
• SAV and chatbot may link customers back to tracking pages.

Local Docs Submodule

When this repo consumes global docs, use:

cd docs
npm ci
npm start
npm run build

To Expand

• Tracking URL contract.
• Invoice/download behavior.
• Delivery confirmation workflow.
• Incident triage for stale statuses.

Dependencies

The page documents customer tracking and delivery confirmation over operational order/shipment data, with adjacent appointment and SAV context. Exact upstream endpoints and status ownership are unknown.

Setup

Application setup is not established by this page. Follow the owning repository's README and setup instructions, and request the approved local access or environment you need. The shared documentation submodule and docs-site commands are described in the repository map and local development guide; they do not start this application.

Flows

Order to delivery covers order and shipment handoffs. The page does not establish that a shipment record proves physical delivery or customer confirmation.

Diagnosis

For stale tracking, compare the displayed status with the last documented operational event and separate shipment creation from carrier movement and delivery confirmation. URL contracts and stale-status procedures are missing.

Evidence and gaps

The application role and stack are documented only; source refs, tracking URL behavior, invoice/confirmation contracts, setup, and stale-state runbooks remain to be added.

Next evidence to add: source commit and file references for the owned boundary, then repository-specific setup and the relevant operations procedure. See the documentation coverage matrix for the system-wide gap record.