Data and Events

Use project docs to describe exact tables, queues, commands, and API contracts. Shared docs should explain ownership and flow only.

View diagram source

flowchart TD
  Magento["Magento orders/catalog"]
  Logidav["Logidav queues and cronjobs"]
  Meduse["Meduse ERP"]
  External["Carriers, suppliers, marketplaces"]

  Magento -. "documented order/catalog relationship; transport varies by flow" .-> Logidav
  Logidav -. "documented operational updates; exact contract is flow-specific" .-> Magento
  Logidav -. "ERP integration documented; exact path unknown here" .-> Meduse
  Logidav -. "external integrations documented; separate per partner" .-> External
  External -. "imports documented; producer and transport vary" .-> Logidav

Diagram

Dashed edges mean that the relationship is described in the shared documentation while its complete transport and contract are not. The graph groups several independent paths; it does not claim that every carrier, supplier, or marketplace uses the same producer or schedule.

Data and transport ownership

Data or handoff	Documented owner / path	Transport and contract status
Customer order and commerce state	Magento owns the storefront order; Logidav imports and maintains operational order state.	Order to delivery cites the reviewed import and shipment paths. The cursor failure edge and CSV shipment path are source-verified; other operational branches remain partial.
Product availability and price updates	Logidav records stock/price changes and has a Magento import path.	Stock and catalog cites source paths for the reviewed queue-to-Magento API segment. Marketplace propagation and scheduler setup remain unknown.
Support/refund state	SAV, chatbot, commerce, and operational tools have documented relationships.	Support and refunds separates reviewed refund-check fragments from unverified request, provider, and case lifecycles.
Carrier, supplier, marketplace data	Logidav has separate documented integrations with external parties.	Per-integration protocols, file/API payloads, and schedule must be read from the owning integration reference; a generic external edge is not a shared contract.

Evidence rule

Use source references for concrete field names, command behavior, state transitions, and retries. A command implementation proves what that command does in the cited revision; it does not prove its installed schedule, deployed configuration, or production outcome. See coverage for systems whose ownership or transport evidence is still missing.