Mirakl

ParcelPilot currently supports direct Mirakl seller API integration for order pulling only.

Implemented

• Pulling seller orders from Mirakl into ParcelPilot using the seller GET /api/orders endpoint
• Incremental sync using Mirakl start_update_date
• Manual backfill via Client Integrations → Pull Orders
• Scheduled order pulling via the normal ecommerce sync jobs
• Reimporting a Mirakl order from upstream
• Normalizing Mirakl orders into the existing ecommerce importer shape used by ParcelPilot
• Test connection from the Client Integration edit screen
• Optional shop scoping via Mirakl shop_id
• Optional order-state filtering via integration settings

Credentials needed

Enter these under Integrations → Client Integrations → Mirakl:

• Marketplace base URL
• API key
• Shop ID (optional)
• Page size (optional)
• Order states to pull (optional)

Still to do

• Live end-to-end validation against a real Mirakl seller account
• Confirm best default order-state selection for each client workflow
• Product import from Mirakl
• Inventory sync with Mirakl
• Pushing shipment confirmations or order updates back to Mirakl
• Decide whether operator-level Mirakl support is ever needed in addition to seller API support
• Add richer operational help for common Mirakl marketplace differences between implementations

Notes

• Current implementation uses the seller API, not the operator API.
• Authentication is via the Mirakl seller API key in the Authorization header.
• ParcelPilot currently uses Mirakl order pulling as a pull-only integration.
• The implementation uses Mirakl offset pagination and fetches a single order by reusing the orders endpoint with order_ids.
• Current Mirakl implementation is intentionally isolated from other ecommerce integrations so existing integrations are not affected.