The first marketplace a brand adds is a growth story. The third is an operations problem. Each channel delivers its orders into its own screen, with its own address format, its own delivery promise, its own rules for what counts as "shipped", and its own place to paste a tracking number. Packing stops being one job and becomes one job per channel, and support stops being one inbox and becomes one inbox per channel. This page is about the other way to run it: one order queue, with the channel carried as a field on the order rather than as a separate process.
Short answer: Orders from every channel should land in one queue the moment they are placed, carrying the channel, the customer's address in one format, and the delivery promise the channel made. One set of routing rules then picks the carrier and service for each parcel, one label flow prints it, one packing bench works through the queue in whatever order makes sense for the day, and the shipment's tracking number and carrier code go back to the channel that sold it automatically, because a marketplace counts an order as shipped only when it has them. The customer, whichever channel they bought on, gets the same tracking page and the same messages. The parts that usually break are the handover back to the marketplace, the delivery promise the marketplace imposes, returns that start on the marketplace, and stock shared across channels.
What a marketplace order asks of you that a webshop order does not
A webshop order is yours end to end. A marketplace order comes with the marketplace's terms attached. Three of them shape the packing bench directly.
A deadline. Marketplaces measure handling time, the gap between the order and the shipment confirmation. eBay's seller guidance covers handling times as a core part of shipping well, and OTTO reports up to 49 orders a second on its platform, which is the pace its partners' handling is measured against. An order that sits in a separate screen nobody opens until the afternoon is a late order on that channel.
A confirmation with evidence. The channel wants the tracking number and the carrier back. Sello, which connects brands to more than 70 marketplaces, describes the mechanism plainly: orders placed on the connected marketplaces are transferred automatically to the brand's system, and tracking numbers for shipped orders are sent back to the marketplaces automatically. If that return trip is manual, it is the step that gets skipped on a busy day.
A geography. OTTO requires partners to ship from a warehouse in Germany or the EU and to accept returns in Germany or selected EU countries. About You offers partners up to 28 markets. The marketplace decides where the customer is; your carrier mix has to reach them.
The one-queue design
| Element | Per-channel way | One-queue way |
|---|---|---|
| Where orders arrive | One screen per channel (Shopify admin, Seller Central, the Zalando partner portal, CDON's merchant tool) | One queue; the channel is a field on the order |
| Address | Each channel's format, retyped or copied | One normalised address, validated once |
| Delivery promise | Remembered by the packer | Carried on the order and used by the routing rules |
| Carrier choice | Whatever the channel's label tool offers | One rule set: destination, service promised, weight, cost, carrier reliability |
| Label | Printed from each channel's tool | One label flow, any carrier |
| Shipment confirmation | Pasted into each channel | Sent back automatically with tracking number and carrier code |
| Customer tracking | Each channel's page, or the carrier's | One branded tracking page and one set of notifications |
| Returns | Started in each channel's portal | One returns flow that knows which channel the order came from |
The point of the table is the first row. Everything else follows from getting the order into one queue with its channel attached, and fails if you do not.
Routing: the delivery promise is an input, not an afterthought
On a webshop you chose the delivery options; on a marketplace the customer chose from the marketplace's options, and you inherited the promise. The routing rule set has to read that promise from the order. A next-day promise on OTTO cannot go on the cheapest economy service because the cheapest service was the default for webshop orders. In practice this means the rule set keys on three things per order: where it is going, what was promised, and what the parcel is. The rest, rate shopping between carriers that can meet the promise and failover when a carrier is degraded, is what multi-carrier shipping software does, and is explained in what is multi-carrier shipping.
The handover back to the channel
This is the step that decides whether a marketplace counts you as reliable. Each channel has its own definition of a valid shipment confirmation: a tracking number, a carrier identifier the marketplace recognises, sometimes the service level. The one-queue design sends that confirmation the moment the label is printed, in the format the channel expects, through the connector that brought the order in. Done by hand, it is the task that drifts to the end of the day, and the marketplace clock does not wait.
Tracking and messages: one customer experience, however they bought
A customer who bought on Amazon or Zalando is still your customer when the parcel is late. Carriers return between 10 and 115 different statuses each, so the tracking experience across channels is only consistent if every carrier's statuses are normalised onto one plain set and shown on one branded page, with notifications at the moments that matter: shipped, handed over, delayed, delivered. What a good page shows is in order tracking page best practices, and why the alternative is a support ticket is in what is WISMO.
Returns that start on the marketplace
Marketplace customers return through the marketplace, and the marketplace tells you. The returns flow has to know the order's channel so that the refund, the exchange offer and the return label follow that channel's rules and country. OTTO's requirement that partners accept returns in Germany or selected EU countries is a concrete example: the return address and the carrier for the return label depend on the channel. A returns flow built only for webshop orders will send a marketplace return to the wrong place.
The stock problem nobody mentions
Five channels selling from one stock pool oversell the last unit when inventory syncs lag. Sello's basic plan, as one example, syncs from Shopify every 15 minutes. That interval is fine until a product is down to its last few units during a campaign. The operational fix is not in the packing bench; it is a buffer per channel on low-stock products and a sync that runs faster for the channels that sell fastest. The packing bench only sees the consequence: an order in the queue for a unit that is not on the shelf. Treat that as a signal to fix the buffer, not as a packing problem.
Where Pango sits
Pango is not an order management system. It reads the orders from the systems that own them, the webshop and the marketplace connector, and runs the logistics half on one record of the order: carrier selection and routing against your rules, label generation, warehouse pick and pack, a branded tracking page with proactive notifications, and returns and exchanges with labels and per-country refund logic. That is what makes the one-queue design practical: the channel is a field on the record, the routing rules read the promise, the label prints once, and the tracking number goes back to the channel through the connector that delivered the order. The marketplace connectors Pango works with are listed on the integrations page under Marketplaces, starting with Sello and GoJungo, and the category of software to compare is carrier management software.
If your orders arrive from more than one channel, the free shipping and returns audit shows, on your own orders, how long each channel's orders wait before they ship, which carriers carry them, and where the tracking and returns experience differs by channel. Book the audit.
The bottom line
Get every channel's orders into one queue with the channel, the address and the delivery promise on the record, route against the promise, print once, and send the confirmation back automatically. The handover to the marketplace, the inherited delivery promise, marketplace returns and shared stock are the four places a one-queue operation still has to think per channel; everything else is the same job it always was.
