Dividing work in a multichannel operation is less about headcount than about clear boundaries: every product, every channel, and every process needs one owner, and orders, stock, content, accounting, and customer communication should run on separate screens but the same data. This article explains how a small team can share several marketplaces, which roles take which tasks, and where to add people as you grow.
Why multichannel selling fails without a division of labor
On a single channel everyone looks at everything and nothing goes wrong. When the second and third channels arrive, the work does not add up; it multiplies. Trendyol's campaign calendar, Hepsiburada's packaging rules, Amazon's content requirements, and N11's store rating all want attention on the same day. Add Etsy or eBay for cross-border and the day gets shorter still.
The typical picture: one person collects orders in the morning, fixes listings at noon, checks settlements in the evening, and finishes none of it. Dividing labor does not mean replacing that person with two; it means sorting the work by type and giving each type an owner. The single-panel approach described in multichannel order management only works once that ownership is clear.
The four core roles
Whether the team is two people or ten, the work falls under four headings. In small teams one person wears several hats; what matters is that the hats have names.
Admin
Opening and closing channels, pricing policy, floor price rules, campaign approval, integration permissions, and team access. Not always in the daily flow, but the final address for every decision. Reads contribution per channel once a week and decides which channel to grow.
Content
Product titles, images, categories, attributes, and variants. Adds new products to the catalog, closes quality findings, and resolves listings the marketplace has taken down. Product content and quality score is this role's daily list.
Warehouse
Picking, packing, shipping labels, return acceptance, and stock counts. The warehouse should see only its own screens in the integration panel: today's outgoing orders, labels, incoming returns. Pricing and campaign screens only get in the way.
Accounting
Invoicing, settlements, reconciliation, post-return corrections, and deductions per channel. Settlement and commission reconciliation is the main job here, including missing payouts and returns where commission was never refunded.
In Bulutegra these four roles come built in, alongside Returns and Reporting roles. Each user sees only the screens for their role, and two-factor authentication is enabled per account.
Splitting the work by team size
One person. If the owner does everything, at least divide the day by role: warehouse in the morning, content at noon, accounting one day a week. Do not repeat by hand what the integration already does automatically, such as order transfer, stock sync, and channel monitoring.
Two people. The most common split: one takes Admin plus Accounting, the other Warehouse plus Content. Money and pricing in one pair of hands, products and parcels in the other.
Three to five. The warehouse becomes its own unit and grows, because order volume strains it first. Content stays with one person. Accounting is often shared with an external accountant who receives CSV exports from the panel.
More than five. Marketplace manager becomes a distinct role, gathering channel health, campaigns, and marketplace correspondence in one person. If cross-border channels are open, export paperwork goes to this person or a dedicated one.
Before adding a person, ask: is this something the integration already does automatically? Nobody should be hired to reduce stock, transfer orders, or poll channels.
Ownership by product and channel
Roles are not enough; if two people share a role, it must also be clear who owns which channel. Keep a simple table: channel, owner, backup. The backup matters for holidays and sick days; a channel without one goes silent during a long weekend.
On the product side the question is: who manages this product's stock and price on this channel? Some businesses have certain channels run by another system or an agency. Bulutegra's ownership flag answers exactly this: per product and channel, it marks whether the integration or an external system is in charge, and prevents both from writing to the same listing.
Who owns customer communication?
This is the area most teams forget. Marketplace questions, return requests, and WhatsApp messages land in different places and go unanswered. Give this job to one person and run it from a single inbox; marketplace Q&A and customer messages describes the flow. Bulutegra's CRM module gathers WhatsApp Business API, email, and marketplace questions in one inbox, so the owner does not bounce between three screens.
A weekly rhythm: who looks at what, and when
Once duties are clear, rhythm follows. The list below is a starting point for a small team; adjust it to your volume.
- Every morning, Warehouse: today's outgoing orders and yesterday's returns. Any silent channel on the system health screen?
- Every morning, Content: delisted items and new findings in the quality tab.
- Every day, Admin: low-stock alerts and the days-of-cover report; anything to reorder?
- Weekly, Accounting: reconcile newly published settlement reports; review open tickets and notes.
- Weekly, Admin: contribution per channel; which channel is growing, which is being eaten by deductions?
- Monthly, everyone: a short meeting on return reasons, customer questions, and campaign results.
Write this rhythm down. When someone new joins, "learning the job" means taking over this list.
Common mistakes
- Giving everyone admin rights. Easy but dangerous; one wrong click can change prices across a whole channel. Security, 2FA, and roles explains the least-privilege principle.
- No backup owner. A channel only one person understands stops when that person is away.
- Showing the warehouse the pricing screen. It distracts and produces errors.
- Leaving accounting to month end. Missing payouts have dispute windows; check weekly.
- Repeating automated work by hand. Tracking stock in a spreadsheet alongside the integration leaves you with two truths.
How it works with Bulutegra
The Bulutegra Integration Panel ships with Admin, Content, Warehouse, Returns, Accounting, and Reporting roles; each user sees only their own screens and signs in with two-factor authentication. Orders are organized in channel tabs, quality findings in one list, settlement reconciliation with status and notes, and customer messages in a single CRM inbox. The ownership flag makes it clear at product level who manages which channel. The full list of roles and modules is in the solutions section.
To plan how roles should be assigned in your own team, request a demo.
Frequently asked questions
How many people do you need to sell on several marketplaces?
There is no fixed number; daily order volume, catalog size, and return rate decide it. With the right tools a team of two or three can run several marketplaces. As volume grows, the warehouse usually needs people first, followed by content and accounting.
What does a marketplace manager actually do?
They watch the daily health of every channel, keep listings live, apply campaign and pricing decisions, check settlement reports, and handle correspondence with the marketplaces. In small teams the owner usually shares this role.
What happens when two people do the same job?
It is the most expensive mistake in multichannel selling: two people change the same product's price differently on different channels, or enter the same stock correction twice. Naming one owner per product and channel, and separating permissions by role, prevents it.
