Ecosystem Overview

Magento is the ecommerce source for storefront behavior. Logidav is the operational integration layer between Magento, Meduse, carriers, suppliers, and marketplaces. Chatbot services provide support automation and should call owned APIs instead of reimplementing business logic.

These are ownership and integration relationships, not a complete runtime topology. The exact integration mechanism may be an API, queue, scheduled command, file, or manual step; this page only names it when a linked source-backed flow establishes it.

Responsibility at a glance

System	Documented responsibility	Evidence boundary
Menzzo Magento	Storefront, checkout, catalog, customer, and merchant-facing commerce behavior.	Shared docs identify the owner; repository setup and source references remain incomplete.
Logidav	Operational order, stock, shipment, refund, queue, and integration work.	Existing project docs contain detailed legacy workflows; each cross-system statement must be checked against the current source ref.
Menzzo Chatbot	UI, Dify conversation, business API, and diagnostic components.	The overview cites immutable UI/backend/logs commits; the shared flow narrows what those refs prove.
Other project areas	Storefronts, product/catalog services, SAV, tracking, scheduling, and supporting tools.	See coverage for setup and evidence gaps by project.

Boundary rule

Let the owner of a behavior define its contract. A caller may present or cache data without owning its meaning. When a change crosses a boundary, record the producer, consumer, immutable source refs, transport, failure behavior, and operational owner—or mark the missing part explicitly.