Choose marketplace operations support when approved listing fields, seller-console queues, platform notices, or channel reports need preparation. Choose order-and-returns support when a specific order, return, exchange, tracking, or fulfillment exception needs evidence. Neither role decides publishing, price, inventory, fulfillment, refunds, policy, access, or customer outcomes.
Both roles prepare evidence for owner review. They do not take over merchant decisions.
Use this role for approved listings, seller-console queues, platform cases, channel reports, and marketplace mismatch briefs. The merchant decides claims, category, price, publishing, appeals, and account actions.
Use this role for order, tracking, return, exchange, carrier, and warehouse evidence. The store owner decides eligibility, refunds, replacements, inventory, fraud, policy, and customer remedies.
Choose the smallest lane that makes the next owner review clear.
An approved listing update, seller-console queue, platform notice, channel error, inventory signal, or marketplace mismatch needs preparation.
A specific order, tracking, cancellation, return, exchange, damaged-item, warehouse, or carrier exception needs a case record.
Does the next review concern a marketplace or channel record, or a customer order and fulfillment path?
Approved product fields, listing and SKU IDs, channel notices, screenshots, prior case messages, and merchant rules.
Order, item, carrier, warehouse, return evidence, and the applicable written store rule.
Hold the work when records disagree, required evidence is missing, or a policy needs interpretation.
A listing draft, queue log, platform-case record, mismatch brief, inventory-signal note, or channel report.
An order or return case note with checked records, evidence, held action, owner, and next step.
The reviewer should see verified facts, missing information, deadline, held action, and named owner without reconstructing the case.
Listing publication, claims, category choice, price, promotion, appeal, account action, replenishment, transfer, removal, and stock commitment.
Refund, credit, replacement, exchange, cancellation, fee, inventory commitment, fraud response, delivery promise, and policy exception.
A prepared record never grants authority to change a listing, order outcome, account standing, money, stock, or customer promise.
Named, limited seller-console and approved queue access; no payouts, tax, user administration, recovery, export, or account ownership access.
Named, limited order, carrier, warehouse, and help-desk access for one request type; no payment, refund, inventory, or admin controls.
Owners approve permissions, MFA, review dates, removal steps, and any exception.
Check sample IDs, source fields, screenshots, notices, deadlines, held decisions, and merchant routing before another queue or marketplace is added.
Check source accuracy, evidence, written-rule use, held action, escalation timing, and owner routing before another request type is added.
Repair the source, SOP, template, stop condition, or owner route before expanding the role.
Choose marketplace operations support when the immediate job is to prepare approved listing fields, log platform notices, capture screenshots, and draft a correction for review. The merchant still decides claims, category, price, publishing, appeals, and account actions.
Choose order-and-returns support when delayed orders, returns, exchanges, and warehouse or carrier follow-up need a traceable case record. The store owner still decides eligibility, refunds, replacements, inventory, fraud, and customer remedies.
Start with marketplace operations when the first job is a channel mismatch or platform-case brief. Move to order-and-returns support only when a defined customer order or return needs fulfillment evidence; the named owner decides any outcome.
Assistants can organize approved records, check written rules, flag differences, prepare drafts, and route exceptions. Authorized owners retain listing publication, claims, pricing, inventory, fulfillment, refund eligibility, customer commitments, access, privacy, policy, and final decisions.
"Use the approved source and written checklist to prepare the named marketplace or order-and-returns record. Hold and route requests involving publication, claims, price, stock, fulfillment, payment, refund, customer remedy, policy, account action, access, privacy, or another live change. Link the evidence and name the authorized owner who decides."
This is a house planning sequence, not permission to change a live listing, order, customer outcome, or account control.
Use approved source fields, queue records, limited access, held decisions, and merchant review before another channel expands.
Read the marketplace operations guideOrder pathUse checked order records, return evidence, a written rule, held action, and owner routing before another request type expands.
Read the order and returns guideListing reviewKeep the approved source, proposed change, held price and stock fields, merchant decision, and publishing owner together.
Open the listing approval logNo. Marketplace operations prepares approved listing, seller-console, platform-case, channel-report, and mismatch records. Order-and-returns support prepares specific order, return, exchange, tracking, and fulfillment-exception records.
Possibly, after each lane has separate sources, outputs, access limits, stop rules, reviewer routes, and checked examples. Start with one lane rather than treating a broad ecommerce title as permission to manage every channel and customer exception.
The assistant may compare records, gather evidence, and prepare the brief. The authorized merchant or store owner decides refunds, credits, cancellations, reships, replacements, inventory commitments, customer promises, platform responses, and policy exceptions.
Not as an independent decision. The role can prepare an approved draft, evidence packet, deadline log, and review note. The merchant or senior operator approves publication, claims, pricing, appeals, disputes, and account-level actions.
These sources inform task examples and access caution. They do not standardize job titles, authorize live changes, or prove a staffing outcome.
Use OutsourcedU to write the role, SOPs, onboarding steps, and weekly review before you hire more people.