Appearance
Menzzo Magento Architecture
This page maps the first-party Magento code at axelites/menzzo@3edcc1e24e9a1e8382dc1bad0dfb3158b8074cea. It is a static source map. It does not describe a verified deployment, active schedule, configured provider, or running consumer.
Application shape
The repository is a customized Magento 2 storefront. Magento's core provides catalog, customer, cart, order, and payment extension points; first-party behavior is concentrated in app/code/Axelites/. The repository playbook also identifies app/design for frontend themes and Magento XML declarations for routes, dependency injection, events, cron jobs, and message queues.
| Area | Magento-side responsibility | Source map |
|---|---|---|
| Shared storefront and scheduled work | Axelites_Core supplies category/menu blocks and schedules product, menu, and search-index tasks. | Core cron declarations, category menu block |
| ERP-facing product and order interfaces | Axelites_Logidav declares Web API routes, database-backed queue processing, and AMQP consumers for product, quantity, new-product, image, and category updates. | Logidav API routes, queue consumers, queue processor |
| Supplier-file integrations | Axelites_Meduse declares scheduled product, attribute, family, file, product-image, and menu-snapshot work. | Meduse cron declarations, menu snapshot import |
| Cart and payment extensions | Axelites_Fastcheckout adds storefront cart actions at the drop route. Axelites_Payment hooks order-save and checkout-success events; provider modules add their own return, notification, and order-summary handlers. | Fastcheckout route, payment events, Voxpay callback, Revolut frontend route, Payline order summary |
| Shipping extensions | Axelites_MenzzoShipping and Axelites_Trusk declare shipping data interfaces; Axelites_Logidav exposes shipment reservation and report routes. | Menzzo shipping API, Trusk API, Logidav shipment routes |
| Scheduled exports | Axelites_GoogleAdsTracking declares an order CSV export; Axelites_Lengow declares a product-feed export. | Google Ads cron declarations, order CSV export, Lengow cron declaration, Lengow product feed |
Declared scheduled work
The following entries are declarations in module XML. Their presence does not prove a cron group is enabled or that a job ran.
| Job family | Declared cadence | Magento-side entrypoint |
|---|---|---|
| Logidav queue processing | Every five minutes | Axelites\Logidav\Cron\ProcessLogidavQueue |
| Logidav planned price updates | Hourly | Axelites\Logidav\Cron\ProcessPriceUpdates |
| Meduse imports, including products, images, and menus | Every five minutes in the meduse group | Axelites\Meduse\Cron\Sync* |
| Core menu preparation | Daily at 00:00 | Axelites\Core\Cron\Menu::execute |
| Google Ads order CSV | Daily at 03:00 in axelites_crongroup | Axelites\GoogleAdsTracking\Cron\OrderCsvExport::execute |
| Lengow product feed | Every four hours | Axelites\Lengow\Cron\LaunchExport::execute |
Reading the boundaries
- A Magento Web API route maps an incoming request to a service contract. The route declaration does not identify which external process calls it or prove that the remote caller uses the same contract.
- The Logidav database-backed import queue and the Magento AMQP consumers are separate source paths. The XML declarations show their configured names and consumers, not live broker bindings or worker state.
- Provider modules own distinct checkout and notification handlers. Read each provider flow separately; a shared payment lifecycle, retry policy, or refund guarantee is not established by the module list.
- Meduse file jobs and the Core menu builder write Magento-side catalog, image, or menu state. A saved local record does not prove final CDN or storefront rendering.
Continue with Workflows for the entrypoint-to-consumer map and Catalog import for the product-import detail. For the source evidence policy, see Documentation Maintenance.