Use Cases

Multi-channel Order and Fulfillment Orchestration

How Orchesty processes marketplace orders across channels, normalizes them for the ERP, manages fulfillment, and synchronizes tracking and delivery statuses in real time.

Expanding into marketplaces creates a fundamental logistical challenge: how to efficiently process orders arriving in different formats while keeping the customer, the ERP, and the marketplace informed about delivery status in real time.

This case study shows how Orchesty orchestrates the full logistics lifecycle through three connected phases, from order ingestion to fulfillment and status synchronization.

Automated Ingestion and Normalization #

The first step is to unify diverse data from marketplaces such as Amazon, Kaufland, and Allegro into a standardized format for the ERP.

Marketplace order processing flow covering ingestion, ERP normalization, fulfillment, and delivery status synchronization
Orchesty orchestrates marketplace order intake, ERP handoff, shipment processing, and delivery status updates across channels.
  • Identity Unification: Orchesty receives a webhook from the marketplace and immediately identifies products and prices using the Marketplace Store, an external repository for ID pairs.
  • Customer Management: The system verifies whether the customer already exists in the ERP. If not, it automatically creates a new customer profile.
  • Recording and Acknowledgment: Once the order is created in the ERP, Orchesty stores the link between the ERP Order ID and the Marketplace Order ID. It immediately sends an Order Accepted signal back to the marketplace, protecting the seller's rating and confirming that the order is in process.

Fulfillment, Labels, and Tracking #

As soon as the warehouse switches an order to the shipping state in the ERP, Orchesty takes over as the dispatch coordinator.

Marketplace shipment flow covering carrier communication, label creation, ERP updates, and tracking propagation
Orchesty coordinates shipment creation, label handling, ERP synchronization, and marketplace tracking updates in parallel.
  • Carrier Handshake: Orchesty communicates with the carrier API, creates the shipment, and retrieves the shipping label.
  • Label Cache: The downloaded label is stored in a cache for immediate warehouse printing, and its link is recorded in the ERP. This keeps the ERP lean because it does not have to store bulky files.
  • Parallel Routing: Orchesty then performs two critical actions at the same time:
    1. Back to ERP: It records the Tracking ID and updates the order status.
    2. To Marketplace: Based on the stored ID pairs, it identifies the correct source marketplace and sends the Tracking ID. The customer receives shipping information seconds after the label is printed.

Shipment Lifecycle and Status Synchronization #

The process does not end with dispatch. Orchesty monitors the shipment until the moment of delivery.

Marketplace order status synchronization flow covering carrier webhooks, ERP updates, and marketplace status mapping
Orchesty tracks shipment events and propagates normalized delivery statuses to internal and marketplace systems.
  • Real-time Monitoring: Based on carrier webhooks, Orchesty tracks the movement of the package.
  • Status Synchronization: Any change, such as picked up, at pickup point, or delivered, is distributed in real time:
    • To the ERP: For customer service visibility and internal statistics.
    • To Marketplaces: Via an intelligent router, statuses are mapped to the specific requirements of Amazon, Kaufland, or Allegro.

Why This Architecture Scales

  1. ERP Integrity: The ERP receives data in a clean, normalized form and is not burdened by marketplace-specific parameters or by storing print files.
  2. Multi-channel Scalability: Thanks to the central Marketplace Store in Orchesty, adding another sales channel is simply a matter of connecting a new webhook to the existing logic.
  3. Customer Experience: Immediate feedback, including order confirmation and tracking information, increases seller trustworthiness and reduces customer support inquiries.

Conclusion: A Single Command Center for Marketplace Fulfillment #

This case study demonstrates that Orchesty is not just an integration tool, but an orchestration layer that transforms the chaos of multi-channel sales into a precisely managed logistics machine.

Related #

  • ID mapping guide — the "Marketplace Store" that holds ID pairs across Amazon, Kaufland, Allegro, ERP, and carriers is exactly the pattern this guide describes.
  • Marketplace product listing at scale — sister use case for how products get into the marketplace before the orders ever start arriving.
  • Operational visibility — Trash workflow for failed status updates and dashboard cadence for incident triage.