Operations guide · orders, shipping, cancellation and returns

Who is this guide for? Sales and service teams managing Trendyol, Hepsiburada and N11 orders in separate portals.

Managing marketplace orders in one dashboard is not the same as placing three lists side by side. The operation needs one work queue, one status dictionary and one exception process from order receipt through shipment, cancellation and return. The goal is to make the next action clear, not merely reduce the number of browser tabs.

What should happen in the first 90 seconds?

Receive the order with a durable channel identifier so a repeated message cannot create a duplicate. Match the item or variant to the central SKU, reserve sellable inventory and validate payment and carrier data. An unmatched SKU, invalid address or service failure should enter an exception queue instead of disappearing among normal orders.

MarketOne unified list for web-store and marketplace orders — **A real screen from MarketOne.** Source channel, order status, customer and value are visible in one operating queue.

Translate three channel states into one language

Each marketplace can use different labels and transition rules. Define central states such as new, preparing, ready to ship, delivered, cancelled and returned, then map channel responses to them. Reports gain one meaning and automations follow the company’s decision model rather than a platform-specific label.

A daily rhythm built around carrier cut-off

Start with unmatched items and pending payments. Before cut-off, prioritise orders without a label or with delayed picking. At day end reconcile order count, reserved stock, carrier handover, cancellation and failures against each channel. This short discipline prevents silent data loss from rolling into the next day.

When should cancelled or returned stock be released?

If a cancelled order has not left the warehouse, release its reservation through a controlled event. A return should not become sellable before physical receipt and quality inspection. Record warehouse and disposition, then keep customer notification, refund and marketplace status in the same traceable chain.

Four failure tests before launch

Prove that a repeated notification still creates one order.
Create a clear owner and message for an unmatched SKU.
Test stock and payment effects of partial cancellation and return.
Observe safe retry and alerting during a carrier outage.
Reconcile channel and central order count and value at day end.

Example operating SLA

Task	Target	Exception signal
Receive and reserve inventory	1–2 minutes	SKU missing or insufficient stock
Create shipping label	At least 60 minutes before cut-off	No response or invalid address
Accept return and decide stock	Within 24 hours of receipt	Inspection or document missing

Pilot with a genuinely busy day

Select ten orders from a peak day and run normal, final-stock, cancellation, partial-return and failed-carrier cases through MarketOne. Judge the result by how quickly exceptions become owned and resolved, not by the number of screens in the demonstration.

Explore the MarketOne product page · Request a tailored demonstration

Manage Trendyol, Hepsiburada and N11 orders from one dashboard