Appearance
Logidav
Logidav is the logistics ERP and middleware layer connecting Magento, Meduse, carriers, suppliers, and marketplaces.
Purpose
Use this page to navigate Logidav's existing architecture, integration, workflow, operations, and reference documentation. The connected-system summary is documented context; this index does not establish the live configuration or end-to-end state of each integration.
Core areas:
- Interfaces and menu workflows — start from the screen, then follow the endpoint and processing path.
- Getting Started
- Architecture
- Workflows
- Integrations
- Runbooks
- Reference
- Legacy MkDocs Import
Dependencies
The documentation describes connections with Magento, Meduse, carriers, suppliers, and marketplaces. For exact ownership, contracts, and current external configuration, begin with Architecture and Integrations; missing source or runtime evidence should remain marked unknown.
Setup
Application setup is not specified on this index. Follow the owning repository's README and approved local setup instructions. The docs site's own setup is in the local development guide; those commands do not install or start Logidav.
Flows
- Sales import covers Magento order import and selected status reconciliation behavior.
- Shipment generation documents the reviewed shipment-file path and its evidence limits.
- Stock updates and Product sync describe reviewed quantity/catalog paths.
- Refunds and SAV separates SAV records, refund submission, and reconciliation.
These workflow pages are partial where their source packet covers only selected paths. Marketplace propagation, installed schedules, and complete customer/business outcomes may remain unknown.
Diagnosis
Start with the relevant runbook and preserve the affected order, SKU, provider, or shipment context. Compare the source and destination through the approved environment procedure; a command result or intermediate API response does not prove downstream delivery or owner acceptance.
Evidence
Architecture and workflow pages distinguish documented relationships from pinned source references. Check each page's evidence status and remaining gaps before using it operationally. The documentation coverage matrix tracks what is documented, source-verified, or still missing across the projects.