A second marketplace adds owners and dependencies, not just another order source. Build a responsibility checklist before connecting inventory.
Assign each workstream
| Workstream | Accountable decision |
|---|---|
| Seller account | Who supplies business records and completes platform verification? |
| Catalog | Who approves identifiers, images, descriptions and variant mapping? |
| Stock connection | Who authorizes access and owns sellable-stock definitions? |
| Warehouse | Who approves prep, packing, carrier and return instructions? |
| Account monitoring | Who reviews listing errors, performance and payment reconciliation? |
The seller retains responsibility for its platform account even when it appoints providers for specific tasks.
Separate the launch gates
- Account setup complete and permissions available.
- Product records accepted for the intended listings.
- Usable stock confirmed against warehouse records.
- Order, label and tracking tests reviewed.
- Support and exception ownership documented.
Resolve differences before scaling the flow
An item accepted on one platform may need different catalog data or program preparation on another. Keep a record of the source requirement and the approved change so warehouse instructions and listings do not drift apart.
Use FlexHub for a defined scope
Discuss preparation, merchant-fulfilled orders, connection work or separately scoped marketplace support. The current portal and partner/custom routes remain distinct from the new WMS development. No automated product-performance insight, listing approval or sales outcome is assumed.
Official source notes
Sources checked October 22, 2026. Platform rules and account terms can change; use the current official guidance for your account.
Start with your actual operation.
Bring the product, order or system details behind your question so the team can review the relevant scope.