Treat each marketplace as a separate operating setup. Reuse clean product data, but review eligibility, catalog rules, fulfillment, returns and payments against the current platform requirements.
Compare the setup areas
| Area | What to review separately |
|---|---|
| Account | Business verification, eligibility, permissions and ownership. |
| Catalog | Product identifiers, brand/variant data and listing requirements. |
| Fulfillment | Marketplace service or merchant fulfillment, prep and delivery settings. |
| Fees | Current category, storage, fulfillment and other applicable charges. |
| Payments | Payout setup, cycle, holds and reconciliation. |
| Returns | Policy, destination, authorization and disposition responsibilities. |
Use your account’s current program terms and fee information when building a margin model.
Use product data carefully
A warehouse SKU is not interchangeable with a marketplace product identifier. For Walmart, use the required identifier or an approved exemption where eligible. Keep brand, product type and variant data consistent with the approved catalog setup.
Connect orders without duplicating stock
- Name the stock source and channel-to-warehouse mapping.
- Review reserved and held stock.
- Test order release, updates and cancellations.
- Agree label, dispatch and tracking responsibilities.
Scope FlexHub’s role
FlexHub can review marketplace preparation, merchant fulfillment and separately scoped marketplace support. The integration directory identifies connection routes without claiming every option is an active proprietary native connector. Marketplace approval and account policies remain with the platform.
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.