Rest Menzzo

Purpose

rest-menzzo is the internal REST API layer for Menzzo business workflows. It exposes product, order, SAV, complaint, planning, upload, and catalog APIs used by operational tools and storefront-adjacent services.

Stack

• Laravel / PHP API application.
• Sanctum-style API authentication.
• Composer-managed backend dependencies.
• Frontend asset tooling for admin or API support screens.

Connected Projects

• Logidav and Logidav V2 consume or coordinate operational data.
• SAV tools use customer service and order-status endpoints.
• Catalog, tracking, and media services rely on product/order context.
• Ameubleo and other storefronts consume shared catalog or order data paths.

Local Docs Submodule

When this repo consumes global docs, use:

cd docs
npm ci
npm start
npm run build

To Expand

• API route map.
• Auth model.
• Deployment and queue/cron notes.
• Integration contracts with SAV, catalog, and order tracking.

Dependencies

The page describes internal APIs for order, product, SAV, complaint, planning, upload, and catalog workflows. Which consumers use which endpoints is not source-mapped here.

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

See Order to delivery, Stock and catalog, and Support and refunds for shared business boundaries; endpoint participation is unknown until referenced.

Diagnosis

Keep API authentication, endpoint response, and downstream persisted state as separate checkpoints. A route map, auth model, service ownership matrix, and failure runbook are missing here.

Evidence and gaps

The Laravel API purpose is documented, but route-level code references, consumer links, setup, queues/cron, and operational behavior remain to be verified.

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.