Appearance
Menzzo Magento
Menzzo Magento is the customized Magento 2 storefront. This section gives new contributors a source-backed map of the custom modules and their business handoffs. The evidence baseline is the immutable axelites/menzzo source revision 3edcc1e24e9a1e8382dc1bad0dfb3158b8074cea, reviewed on 2026-10-07. This overview describes declared code paths, not the deployed revision or active runtime configuration. The newer commerce guides below use their own reviewed source pin (6bf5acf477d65bcfd54182549fc9487e110da007); follow each page’s evidence scope.
Start here
- Product creation to storefront follows Logidav's Publish action through Meduse, Magento imports and the returned acknowledgement.
- Architecture maps the first-party modules and their responsibilities.
- Workflows follows catalog, stock and price updates, checkout and payment, order export, shipment, refund, menu, and media paths.
- Catalog import is the focused guide for product imports; use it for the detailed file and queue contracts.
- Catalog dependencies traces family, attribute, image, file and menu imports and their different completion rules.
- Varnish configuration provides the staging/dev VCL, persistent Compose mounts, validation and rollback steps.
- Production Varnish bfcache procedure provides the exact production-only change, backup, compile gate, activation and rollback.
- For the cross-system reader journey, see Order to delivery, Stock and catalog, and Support and refunds.
Follow a customer or operator action
| Action | Reading path |
|---|---|
| Add a product and pay | Checkout and payment: quote changes, provider initiation, browser returns, webhooks and order states. |
| Apply a discount or recover a cart | Promotions and cart recovery: banner and manual coupons, chatbot links, and the separate WhatsApp recovery paths. |
| Reserve an upcoming product | Product reservations: request, OTP confirmation and Logidav import. This request does not place an order or reserve inventory. |
| Follow or edit an order | Order to delivery: Logidav import, operator item changes, shipment and carrier identifiers. |
| Cancel or refund | Support and refunds: whole-order versus partial cancellation, pre-refunds and provider reconciliation. Physical return-to-stock remains unresolved. |
Read the failure and verification sections before retrying an action. A provider callback, local status update, queue acknowledgement and delivered order represent different outcomes.
Purpose
Magento serves the customer-facing catalog and cart and connects those flows to provider-specific payment and shipping modules. Custom data exchange is implemented in modules under app/code/Axelites/; the most relevant boundaries in this guide are Logidav, Meduse, payment providers, and scheduled reporting exports.
Dependencies
Axelites_Logidav declares Magento REST and asynchronous queue interfaces for product, stock, price, shipping, order-status, and shipment-related data. Axelites_Meduse declares scheduled supplier-file imports for products, attributes, images, and menu snapshots. These declarations establish the Magento-side implementation points; they do not establish that a remote producer, worker, provider, or destination is currently active.
Setup
Start with Devbox Access and Workspace to select your assigned development environment. Application bootstrap has not been exercised in this source-flow pass; use the owning repository's README and engineering guidance for that environment. A docs-site build does not start Magento.
Flows
Start with Workflows for the Magento-side entrypoint, consumer, and outcome. For operational order processing and the adjacent Logidav screens, see Logidav Orders and Fulfilment. For Meduse-owned screens and file flows, see Meduse media workflows and Meduse scheduled jobs.
Diagnosis
First identify whether the discrepancy begins in a Magento endpoint, a declared cron or AMQP consumer, a provider callback, or the rendered storefront. Then compare the source-side record with the Magento-side result and the customer-visible state. The source map does not prove that a scheduled job ran, a message was consumed, an external provider accepted a request, or an order was delivered.
Evidence and gaps
The module and route declarations have been reviewed at the pinned source revision. Active cron groups, queue workers, provider configuration, deployed code, storefront rendering, and end-to-end owner acceptance remain unverified. The coverage matrix prioritizes remaining workflow and runtime gaps.