Ecosystem Map

View diagram source

flowchart LR
  Magento["Menzzo Magento"]
  Logidav["Logidav"]
  Meduse["Meduse"]
  Chatbot["Menzzo Chatbot"]
  Dify["Dify"]
  ImageLambda["Image resizing"]
  Suppliers["Suppliers"]
  Carriers["Carriers"]
  Marketplaces["Marketplaces"]

  Magento -. "documented relationship; contract unknown" .-> Logidav
  Logidav -->|product, stock and price files via FTP| Meduse
  Meduse -. "product export files; consumer caveat" .-> Logidav
  Logidav -. "documented integration; path varies by partner" .-> Suppliers
  Logidav -. "documented integration; path varies by carrier" .-> Carriers
  Logidav -. "documented integration; path varies by marketplace" .-> Marketplaces
  Chatbot -->|UI conversation path| Dify
  Chatbot -. "conditional business/API paths; see flow page" .-> Magento
  Chatbot -. "backend integration documented; caller scope limited" .-> Logidav

The Meduse/Logidav file edges are traced in the Meduse connector guide. The reverse product-export path has a stopped reader in the reviewed Logidav source; the diagram does not claim successful delivery.

Use this map to decide where a change belongs before editing code. Magento owns customer commerce behavior. Logidav owns operational orchestration and external logistics integrations. Chatbot services integrate with both but should not duplicate core business ownership.

In the diagram, dotted arrows indicate an incomplete or stopped handoff, as explained by their labels and linked guides. The solid Chatbot-to-Dify edge is supported by the linked source references on the Chatbot overview; it still does not prove that a particular environment has that integration enabled.

This is not a deployment topology. The arrows distinguish transports only where a source-backed flow page establishes them. Use Project Boundaries to find the business owner and the coverage matrix to see which handoffs still need evidence.

Ecosystem Map ​

Ecosystem Map