Marketplace Integrations
Logidav connects to multiple marketplaces to import orders, synchronize stock levels, and manage product catalog listings. Marketplace connectors like ShoppingFeed and Lengow act as intermediaries for some platforms.
Supported Marketplaces
| Marketplace | Integration Method | Data Flow | Key Commands |
|---|---|---|---|
| Lengow | Connector hub | Orders in, shipment/status feedback out | menzzo:lengow:sales, menzzo:lengow:update-status |
| Amazon | ShoppingFeed / Lengow | Orders in, catalog + stock + prices out | amazon:orders:import, catalog sync |
| Cdiscount | Direct API / Lengow | Orders in, catalog + stock out | cdiscount:orders:import |
| ManoMano | Direct API / Lengow | Orders in, catalog + stock out | manomano:orders:import |
Common Patterns
All marketplace integrations follow a consistent architecture:
Inbound (Marketplace to Logidav)
- Orders: imported via scheduled cronjobs that poll the marketplace API or connector
- Normalization: marketplace-specific order data is converted into the standard Logidav
Sale+SaleProductmodel - Deduplication: orders are matched by marketplace order ID to prevent duplicate imports
Outbound (Logidav to Marketplace)
- Stock updates: current inventory levels are pushed to each marketplace
- Price updates: product prices are synchronized on a schedule
- Catalog sync: product listings, descriptions, and images are managed from Logidav and pushed to each marketplace
- Shipment tracking: tracking numbers are sent back to the marketplace once a shipment is created
:::tip Connector architecture For Amazon, Logidav uses ShoppingFeed and Lengow as middleware connectors rather than calling the Amazon API directly. This simplifies authentication and handles Amazon's frequent API changes. :::
:::info Lengow V3 accounts
The active Lengow V3 accounts are 5622 (Lengow Menzzo), 6395 (Lengow Cotecosy), and 17220 (Mosaikasa). The old V2 feed 113959 is retired and should not be restored in cron or menu navigation unless the retirement is intentionally reversed.
:::
Error Handling
| Scenario | Behavior |
|---|---|
| Duplicate order | Skipped based on marketplace order ID |
| API rate limit | Retry with exponential backoff |
| Invalid product data | Logged and skipped; alert raised |
| Connector downtime | Cronjob retries on next cycle |