Explore FlexHub’s documented platform and connection options, including Wix. We confirm the connection method, permissions, data flows, and account requirements during scoping.
A current provider documents the connector. Account access, costs and configured flows still need agreement.
Account-scoped
A listed option to evaluate through a partner or custom route; it does not imply a ready native connector.
Native planned
Part of the proprietary WMS roadmap. It becomes available only after scope, build and testing.
Current connection options: some integrations are delivered through FlexHub’s existing integration partners and systems. Listing a platform does not mean every feature is available through a proprietary native connector today.
Custom WMS roadmap: native connections for Amazon US/EU/UK, Walmart, Shopify, and Wix are part of the development direction. Need a platform beyond the list? Bring it into a custom-integration discussion.
25 documented platform and connection options
Marketplaces
Amazon
Account-scoped connection
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Proprietary native connector: planned, separate from current methods.
Marketplaces
eBay
Account-scoped connection
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Method: Partner or custom route selected during scoping
Review seller region, permissions, SKU mapping and order/stock/tracking requirements. Marketplace eligibility and the exact supported flows are confirmed for your account.
Proprietary native connector: planned, separate from current methods.
Storefronts
BigCommerce
Account-scoped connection
Method: Partner or custom route selected during scoping
Review store permissions, SKU/location mapping, order release and the inventory/tracking flows needed. Availability, fees and limitations are confirmed before activation.
Method: Partner or custom route selected during scoping
Review store permissions, SKU/location mapping, order release and the inventory/tracking flows needed. Availability, fees and limitations are confirmed before activation.
Orders can create warehouse orders; configured fulfillment/tracking updates and optional inventory sync require matching SKUs, mapped locations and permissions. Imported order changes and bundle/component stock need explicit testing.
Method: Partner or custom route selected during scoping
Review store permissions, SKU/location mapping, order release and the inventory/tracking flows needed. Availability, fees and limitations are confirmed before activation.
Method: Partner or custom route selected during scoping
Review store permissions, SKU/location mapping, order release and the inventory/tracking flows needed. Availability, fees and limitations are confirmed before activation.
Agree the trading partner, document types, translations, testing, ASNs, labels and portal responsibilities. Each retailer flow requires its own confirmed scope.
Agree the trading partner, document types, translations, testing, ASNs, labels and portal responsibilities. Each retailer flow requires its own confirmed scope.
Confirm authentication, endpoint access, field mappings, stock ownership, retries and test cases. Supported actions depend on the system’s available API and the agreed project.
Eligible orders can import and configured dispatch/tracking updates can return to Wix. Match SKUs and test permissions, cancellations and order changes. Inventory sync is not advertised here as verified.
Discuss non-listed storefronts, ERP/data workflows, custom APIs, and flat-file/SFTP connections under a written integration scope.
CUSTOM DOES NOT NEED TO MEAN UNCLEAR
Agree it. Build it. Test it.
FlexHub’s documented integration approach uses an agreed scope before development. Map the connection, validate the required flows, and coordinate activation with inventory readiness.
FlexHub has also confirmed scoped Ship Sidekick integration capability in a prior account evaluation. Bring your own system and required workflow into the discussion.