Appearance
Architecture Overview
Logidav is a Symfony 3.3 / PHP 7.3 logistics ERP and middleware that orchestrates orders, stock, shipments, and marketplace integrations for the Menzzo commerce ecosystem. It sits at the center of a complex network of external systems -- pulling orders from Magento 2 and third-party marketplaces, synchronizing inventory with Meduse, generating shipping labels through carrier APIs, and processing payments across multiple providers.
The system is composed of 14 bundles, 227+ service classes, 22+ API clients, 19 domain events, a hybrid SQL + RabbitMQ queue system, and 164 cronjobs that keep data flowing between all connected systems.
System at a Glance
Logidav sits at the center — all external systems connect through it, never directly to each other.
View diagram source
graph LR
MAG[Magento 2] <-->|orders, products, statuses| LOG[Logidav]
MED[Meduse] <-->|inventory, back-office data| LOG
MKT[Marketplaces] <-->|orders, stock, catalog| LOG
CAR[Carriers] <-->|labels, tracking| LOG
PAY[Payment Providers] <-->|charges, refunds| LOG
Internal Components
How data moves inside Logidav between the core components.
View diagram source
graph TD
CRON[Cronjobs<br/>164 scheduled tasks] -->|normalize & import| SVC[Business Services<br/>227+ service classes]
SVC -->|persist| DB[(Database<br/>MySQL / MariaDB)]
SVC -->|async tasks| QUEUE[Queue System<br/>SQL + RabbitMQ]
QUEUE -->|execute| SVC
SVC -->|dispatch| EVT[Event System<br/>19 domain events]
EVT -->|side effects| SVC
Order Inbound — Where Orders Come From
View diagram source
graph LR
MAG[Magento 2] -->|website orders| CRON[Cronjobs]
AMZ[Amazon] -->|marketplace orders| CRON
CDI[Cdiscount] -->|marketplace orders| CRON
MNM[ManoMano] -->|marketplace orders| CRON
MED[Meduse] -->|internal data| CRON
CRON -->|normalize & import| SVC[Business Services]
SVC -->|persist| DB[(Database)]
Outbound — Carriers & Shipping
View diagram source
graph LR
SVC[Business Services] -->|labels, tracking| DPD[DPD]
SVC -->|labels, tracking| BRT[BRT]
SVC -->|labels, tracking| CP[ChronoPost]
SVC -->|labels, tracking| GLS[GLS]
SVC -->|labels, tracking| GEO[Geodis]
Outbound — Marketplace Sync
View diagram source
graph LR
SVC[Business Services] -->|stock, prices, products| AMZ[Amazon]
SVC -->|stock, prices, products| CDI[Cdiscount]
SVC -->|stock, prices, products| MNM[ManoMano]
SVC -->|order updates| MAG[Magento 2]
SVC -->|inventory sync| MED[Meduse]
Outbound — Payments
View diagram source
graph LR
SVC[Business Services] -->|charges, refunds| STR[Stripe]
SVC -->|charges, refunds| HIP[Hipay]
SVC -->|charges, refunds| KLR[Klarna]
SVC -->|charges, refunds| PL[Payline]
INFO
Logidav acts as the central hub -- all data flows through it. External systems never communicate directly with each other; Logidav normalizes, transforms, and routes all information.
Key Architectural Characteristics
| Characteristic | Description |
|---|---|
| Monolithic | Single Symfony application with 14 bundles, deployed as one unit |
| Cron-driven | 164 cronjobs poll external systems and trigger processing |
| Event-driven | 19 domain events decouple business logic from side effects |
| Queue-based | Hybrid SQL + RabbitMQ queues handle asynchronous processing |
| API-heavy | 22+ API clients connect to carriers, marketplaces, and payment providers |
| No migrations | Schema changes are applied directly with doctrine:schema:update --force |
Pages in This Section
- Bundle Responsibilities -- what each of the 14 bundles does and how they connect
- Queue Model -- the hybrid SQL + RabbitMQ queue system
- Data Flow -- how data moves between Logidav and external systems
- Runtime & Deployment -- production execution model and deployment process