Menzzo Magento Workflows

This source map follows Magento-side entrypoints, consumers, and persisted or exported outcomes at axelites/menzzo@3edcc1e24e9a1e8382dc1bad0dfb3158b8074cea. The shipment-report interface was additionally checked at 6bf5acf477d65bcfd54182549fc9487e110da007; the focused commerce guides use their own newer source references. This map describes declared paths only. The documentation coverage matrix names the remaining cross-system and runtime evidence.

Follow the commerce journey

The focused guides use newer source evidence than this overview’s original pin:

1. Checkout and payment follows cart mutation and the separate provider return/webhook paths.
2. Promotions and cart recovery explains displayed discounts, quote eligibility, chatbot links and WhatsApp recovery.
3. Order to delivery follows Logidav imports, operator item edits and shipment feedback.
4. Support and refunds separates cancellation, pre-refund, provider refund and physical return.
5. Product reservations follows the separate product-page OTP request and Logidav importer.

Catalog, stock, and price

Entry point	Magento consumer	Source-backed outcome and limit
Meduse cron declarations for product, attribute, family, and file synchronization	Axelites\Meduse\Cron\SyncProducts, SyncAttributes, SyncFamily, SyncFiles, SyncProductImages, and SyncProductFamily	The module declares these jobs every five minutes in its meduse group. This is the supplier-file path into Magento catalog data and media; active file delivery and final storefront state have not been checked. See Catalog import for the detailed import map.
POST /V1/logidav-api/import-logidav-queue	ApiManagement::importLogidavQueueBatch; ProcessLogidavQueue reads pending logidav_queue rows every five minutes and dispatches groups through ProcessorResolver to product-data or shipping-price processors.	The API accepts work into the database-backed queue; a successful HTTP response does not prove that product updates completed. Separate AMQP consumer declarations cover product, quantity, new-product, image, and category updates. Neither declaration proves a live worker or broker delivery.
Hourly axelites_process_price_updates cron	Axelites\Logidav\Cron\ProcessPriceUpdates reads planned CSV updates from the Meduse-configured FTP integration and records product price-attribute update results.	This is a separate planned-price file path. The source-defined file handling and Magento writes do not prove FTP connectivity, current file contents, or which price is visible in a store.

Magento also exposes product/store-price and shipping-price read routes to Logidav. Their callers, authorization configuration, store mapping, and final storefront/checkout results require separate runtime evidence. The neighboring Stock and catalog page provides the cross-system context.

Menu and media

Meduse declares five-minute jobs for product images and files. The image importer moves files through pending, processing, and complete states, reads the file content, and associates prepared images with Magento products. A successful source-side import does not prove that a CDN or customer-facing page serves the same image.

For menu snapshots, SyncMeduseMenu reads candidate files and passes them to MenuSnapshotValidator. The validator checks the device type, file name, allowed store scope, JSON shape, and category identifiers. MenuSnapshotImporter sanitizes menu content, stores it under axelites_menu_meduse/items_<device>, and handles category image paths. Core then filters, sorts and enriches the snapshots with category URLs, counts, visibility and images before saving derived menu data to axelites_menu/items_*. The SubCategories block reads Desktop data; the Topmenu rewrite selects Desktop or Mobile data. The files and configured records are source-backed; active FTP delivery and rendered storefront/CDN evidence are open.

See Meduse media workflows and Meduse scheduled jobs for the neighboring-system view.

Cart and payment

Axelites_Fastcheckout declares the storefront front name /drop and contains cart add, remove, and update controllers. That identifies custom cart actions, not a complete checkout contract.

Payment paths are provider-specific. Axelites_Payment observes order-save and one-page checkout-success events. Voxpay declares POST /V1/voxpay/paymentreturn/notifyfrompaymentgateway; Revolut has a revolutcheckout frontend route with checkout and webhook controllers; Payline exposes a permissioned order-summary route at GET /V1/payline-page/orders/:orderIncrementId. Alma has an order-payment data-assignment observer. These source paths establish extension points; configured payment methods, provider acceptance, callback retries, order-state reconciliation, and customer-visible confirmation remain unverified.

For customer-order operations beyond the payment adapter, continue to Order to delivery. For refund ownership and evidence limits, see Support and refunds.

Order exports and ERP-facing order routes

Two scheduled exports have different purposes:

• Axelites_GoogleAdsTracking declares a daily 03:00 OrderCsvExport job. The class groups stores and creates an orders CSV for a 09:00-to-09:00 window. It attempts an S3 upload and removes the local CSV before checking the upload result. Bucket configuration and successful delivery are unverified.
• Axelites_Lengow declares an export every four hours. LaunchExport generates a product feed (lengow_feed.csv); this is a catalog export, not the Magento-to-Logidav order handoff.

The Logidav Web API includes routes to import a Cote Cosy sale, change Magento order status, update sale data/address, write a Chronopost reservation number to a shipment, and retrieve shipment reports. The Magento declarations and service methods are source-backed. The shared Order to delivery guide traces the reviewed Logidav callers, import cursor, shipment creation, item edits and Chronopost writeback. The declared shipment-report route still has no matching service method in the inspected source and must not be treated as a verified readback interface. See Logidav Orders and Fulfilment for the Logidav-side guide.

Refunds and returns

This source map did not establish a complete Magento refund submission and provider-reconciliation path, nor a physical-return-to-stock handoff. Provider-specific payment callbacks should not be read as evidence of a refund. The cross-system refund and SAV paths are documented in Support and refunds; the expanded guide traces cancellation and pre-refund ownership, while provider acceptance and physical-return-to-stock remain open in the coverage matrix.

Evidence boundary

All source claims on this page refer to the pinned revision in the page metadata. Cron XML is a schedule declaration; route XML is an interface declaration; queue XML is a consumer declaration. None proves a live schedule, message, remote connection, provider transaction, deployed revision, or accepted customer outcome.