Multi-Channel Order Management From One Screen
How to manage marketplace orders from Amazon, eBay, Etsy, Trendyol and more in one list, write them to your ERP automatically and ship daily without errors.
Multi-channel order management means collecting orders from every marketplace and your own store into one list, preparing and shipping them through the same flow, and writing tracking details back to each channel. Instead of opening five seller portals to download orders, you look at one screen; the order is written to your ERP automatically, and invoicing and shipping continue in your own routine. This article walks through the daily order flow step by step and shows which errors a single list prevents.
The morning routine without integration
In a business selling on several channels the morning starts like this: open the Amazon portal, download new orders. Open eBay, repeat. Etsy, Walmart, your Shopify store. Key each list into the ERP or import via spreadsheet. Print labels. Let the warehouse pick. In the evening, enter tracking numbers into each portal one by one.
The routine works at low volume. As channels and orders grow, two things happen: you need a person doing the same job repeatedly, and the error rate rises. A tracking number typed into the wrong portal, a forgotten cancellation, an order written to the ERP twice.
Single-list order management reduces this routine to one screen. In Bulutegra's Integration Panel the orders page opens with channel tabs; you pick a date range, search by customer name or SKU, and export to CSV when needed.
The order flow: from arrival to delivery
The stages an order passes through are the same regardless of channel. The platform keeps them in one status list:
- Received: the order is pulled from the channel; customer, address, line items, shipping preference and payment details are gathered in one record.
- Stock deducted: the quantity leaves the single stock pool and the remaining value is written to the other channels. See inventory sync and overselling.
- Written to ERP: the order passes to Nebim V3, Logo, Mikro or SAP with customer, line items, carrier and payment details. The invoice is issued in the ERP.
- Preparing: the warehouse picks according to the pick list. A user in the Warehouse role sees only their own screen, with no access to pricing or settlement pages.
- Shipped: the label is printed, a tracking number is created and written back to the channel automatically.
- Delivered / returned / cancelled: status changes on the channel side are reflected in the list.
Every stage is visible in the panel. "Where is this order" is one search away.
Handling channel differences
Each marketplace has its own rules: handling time, carrier choice, invoice requirements, cancellation windows. These rules change, so check each marketplace's current seller agreement. Integration's job is to hide the differences inside one flow.
A concrete example: a Trendyol order uses the marketplace's contracted carrier, while an order from your own store uses your own carrier account. Both sit side by side in the list; the person packing sees which label to print from the system and does not have to decide.
On global channels the differences grow. For Amazon, eBay and Etsy orders, currency, customs data and micro-export paperwork are prepared at order time; on US orders the size is converted one step up according to the product's own size chart. We cover this in the cross-border marketplace integration guide.
One list does not mean no rules. It means the rules come from the system, not from whoever is packing.
Cancellations and changes
The most delicate point in order management is a change that arrives while the order is being prepared. The customer cancelled, but the warehouse already sealed the box; the parcel left, and the marketplace return process began.
In a single-list flow, the moment a cancellation is pulled from the channel the order status changes and it drops off the pick list. Stock returns to the pool; the ERP record is marked cancelled. The order disappears from the warehouse user's screen, and "did anyone tell them" is no longer a question.
Address or line-item changes follow the same logic: the record is updated and the label reprinted. For an exchange request, a new exchange order is opened through the returns portal; the customer logs in with e-mail and order code, receives an automatic return code, and the warehouse accepts the item by barcode. Details in marketplace returns management and the returns portal.
Who sees what: roles
Everyone entering the orders screen with the same permissions is both an error risk and a security problem. A warehouse worker does not need to change prices; accounting does not need to cancel shipments.
Bulutegra has six roles: Admin, Content, Warehouse, Returns, Accounting and Reporting. Warehouse sees only orders to prepare and shipping actions; Accounting looks at settlement and reconciliation pages; Content works on product text; Admin has access to everything. Login is protected by two-factor authentication. See security, 2FA and roles in marketplace integration.
The mobile interface lets you check order status from your phone, and when a channel goes quiet, a notification lands there. "No orders from eBay for two hours" is noticed now, not in the evening.
Daily checklist
After moving to a single list, closing the day with this short list catches problems early:
- Were all of today's orders written to the ERP? If any failed, the system health screen shows why.
- Any orders left in "preparing" from yesterday? Ship before the marketplace's handling time expires.
- Does every shipped order have its tracking number written back to the channel?
- Have cancelled orders dropped off the pick list?
- Did any channel raise a monitoring alert?
- Any products at the low-stock threshold? See low stock and days of stock.
The list takes five minutes and closes most days cleanly. For the monthly view, use the metrics in marketplace performance reports and KPIs.
How it works with Bulutegra
In Bulutegra, orders from more than 24 marketplaces land in one list: Amazon, eBay, Etsy, Walmart, Ozon, Temu, SHEIN, Jumia, plus Trendyol, Hepsiburada, N11 and the other Turkish marketplaces. Channel tabs, date range, customer and SKU search and CSV export are on the same screen. Every order is written to Nebim V3, Logo, Mikro or SAP with customer, line items, carrier and payment details; invoicing and shipping continue in your own routine. Admin, Content, Warehouse, Returns, Accounting and Reporting roles settle who sees what; two-factor authentication protects logins; the mobile interface and continuous channel monitoring let you follow the day from your phone. See all modules under Solutions.
To see the order flow with your own channels, request a demo.
Frequently asked questions
What is multi-channel order management?
Collecting orders from Amazon, eBay, Etsy, Walmart, Trendyol and your own store into one list, picking and shipping them through the same flow, and writing tracking numbers back to each channel. It removes the need to log into every seller portal.
Can marketplace orders be sent to my ERP automatically?
Yes. The integration platform writes each order to your ERP (SAP, Logo, Mikro, Nebim V3) with customer, line items, carrier and payment details. Invoicing and shipping continue in your existing routine; the manual order entry step disappears.
What is the most common order management mistake?
Entering the tracking number into the marketplace late, or not at all. The order stays "preparing" and your delivery-time metric suffers. The second most common is a cancelled order that keeps being picked in the warehouse. Both are prevented by a single, status-based order list.
