> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # CloudHub, Multichannel Commerce Platform inside Vortex Apps > CloudHub is the enterprise multichannel commerce platform inside Vortex Apps. Eight service modules cover inventory [Optimise], orders [Deliver], repricing [Compete], reports [Analyse], warehouse [Locate], setup [Configure], plus Customer Services and Vendor Central, across Amazon, eBay, Walmart, OnBuy, Cdiscount, FNAC, Rakuten, Shopify, and more. CloudHub, also called 247CloudHub, is the enterprise multichannel commerce platform that lives inside [Vortex Apps](/vortex-apps/overview). If your business sells across Amazon, eBay, Walmart, OnBuy, Cdiscount, FNAC, Rakuten, Shopify, and your own webstore, and you need a single console that holds the master SKU, syncs inventory both ways, routes every order through one fulfilment workflow, reprices against competitors, and reports across the lot, CloudHub is that console. CloudHub is meaningfully different from the other Vortex Apps. StagingPro and Vortex Backup are safety nets for one storefront. CloudHub is the operating system for many storefronts at once. It is built around an action-verb design language (\[Optimise], \[Deliver], \[Compete], \[Analyse], \[Locate], \[Configure]) and a multi-account VendorDB model that lets a single login operate across multiple sellers, brands, or trading entities. ## What CloudHub does CloudHub holds your **common inventory** as a master record and pushes that record out to each marketplace listing. It pulls every marketplace order back into one **pending orders** queue, runs them through your warehouse pick / pack / ship workflow, generates carrier labels and manifests, then writes shipment confirmation back to the source marketplace. Repricing against Amazon competitors runs continuously in the background. Reports cross-cut sales, inventory age, returns, late shipments, and shipping costs across all channels. You do not log into Amazon Seller Central, then eBay Seller Hub, then OnBuy, then Cdiscount, and reconcile by hand. You operate all of them from one screen. ## The eight service modules CloudHub uses bracketed action verbs as its design language. Each verb is one of the eight service modules. | Module | Verb | What it owns | | ---------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------- | | [Inventory Management](/vortex-apps/cloudhub/optimise-inventory) | \[Optimise] | Master SKU catalogue, per-marketplace listings, imports / exports, listing status, FBA inventory | | [Order Management](/vortex-apps/cloudhub/deliver-orders) | \[Deliver] | Pending orders, scan pack ship, manual orders, FBA orders, courier manifests, print logs | | [Repricing Automation](/vortex-apps/cloudhub/compete-repricing) | \[Compete] | Amazon repricing dashboard, competition analysis, min / max price rules, per-SKU repricing status | | Reporting and Analytics | \[Analyse] | Sales, products, returns, late shipments, VAT, inventory age, website cart and search reports | | Warehouse Management | \[Locate] | Warehouse and stock locations, purchase orders, suppliers, goods received, stock movement log | | Setup and Configuration | \[Configure] | Marketplace accounts, order workflow, shipping carriers, repricing profiles, document templates, user permissions | | Customer Services | (no bracket) | Create order, customer-service-led order entry, website customers and sales lookup | | Vendor Central | (no bracket) | Amazon Vendor Central direct fulfilment, vendor retail, vendor inventory, vendor setup | This page covers the first three modules in depth (Optimise / Deliver / Compete). The remaining modules are documented in subsequent CloudHub batches. ## The VendorDB multi-account model CloudHub does not assume one user equals one company. The platform is built around a **VendorDB code** that identifies the trading entity. A single user can switch between several VendorDBs from the avatar menu (Switch VendorDB), each with its own marketplace accounts, warehouses, repricing profiles, and SKU catalogue. Examples of VendorDB codes from a real environment: * 247C1005, Channels Ahead Demo Store * 247C1007, The Monogram Group Limited * 247C1035, Five Diamond Trading Limited * 247C1041, Rejel Automotive Parts Ltd * 247C1050, W\.C.Maunders Ltd * 247C1062, Krispy Kreme UK Ltd This is how brand groups, multi-entity retailers, and 3PL operators run several distinct businesses on one login without cross-contaminating data. See [Switch VendorDB](/vortex-apps/cloudhub/account/switch-vendordb) for how to swap between them. ## Who CloudHub is for CloudHub is purpose-built for these merchant profiles: 1. **Multi-marketplace operators**, sellers running Amazon plus eBay plus at least one of OnBuy, Cdiscount, FNAC, Rakuten, TradeMe, Allegro, Fruugo, or Shopline. 2. **Amazon-led brands** with FBA + FBM mix who need repricing automation and FBA stock visibility in one place. 3. **Multi-entity groups**, parent companies with several trading entities or brands that share warehouses but need ringfenced books per entity. 4. **3PL providers and aggregators** who manage marketplace stores on behalf of clients and need per-client VendorDB segregation. 5. **D2C brands expanding to marketplaces**, merchants whose Shopify or BigCommerce store is solid and who are now moving onto Amazon and eBay without a multichannel platform yet. If you only sell on one storefront, CloudHub is heavier than you need. The right Vortex App for a single Shopify store is [Vortex Staging](/vortex-apps/vortex-staging) plus [Vortex Backup](/vortex-apps/vortex-backup). For a single BigCommerce store it is [StagingPro](/vortex-apps/staging-pro) plus [RollbackPro](/vortex-apps/rollback-pro). CloudHub becomes the right choice the moment you are operating across two or more sales channels. ## Current marketplace coverage The Inventory Hub today shows tabs for Amazon, eBay, OnBuy, Rakuten, Cdiscount, FNAC, TradeMe, Shopify, Allegro, Fruugo, Shopline, Abebooks, and FBA (as a distinct fulfilment surface within Amazon). See [Inventory Hub](/vortex-apps/cloudhub/optimise-inventory/inventory-hub) for the full marketplace tab walkthrough. Cross-link the per-marketplace landing pages in the [connector hub](/integrations/connector-catalogue) for marketplace-specific connection mechanics: [Amazon](/integrations/connector-catalogue), [eBay](/integrations/connector-catalogue), [OnBuy](/integrations/connector-catalogue), [Fruugo](/integrations/connector-catalogue), [Shopline](/integrations/connector-catalogue), [Abebooks](/integrations/connector-catalogue). ## Merchant-demand additions in flight These three are the most-requested additions from current CloudHub users and are being scoped for a future release: 1. **Temu**, the cross-border discount marketplace. 2. **TikTok Shop**, the social commerce surface that has lifted ten figures of GMV in the last two quarters. 3. **Tesco**, the UK supermarket marketplace for FMCG and grocery-adjacent sellers. If you have a strong use case for any of these, log a ticket and the product team will weight your request into the priority queue. ## ShipBob and Vortex IQ platform connectors CloudHub is for **marketplace** inventory and order operations. For **3PL fulfilment**, the recommended connector is [ShipBob](/integrations/connector-catalogue), which is already live as a Vortex IQ platform-level connector. CloudHub orders that are routed to ShipBob for fulfilment are tracked in the ShipBob Nerve Centre tab while the order workflow itself is owned by CloudHub. ## Pages in this section | Section | Pages | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | | [CloudHub login](/vortex-apps/cloudhub/login), [CloudHub dashboard](/vortex-apps/cloudhub/dashboard) | Sign-in flow and top-level KPIs | | [Account, edit user and password](/vortex-apps/cloudhub/account/edit-user-and-password), [Switch VendorDB](/vortex-apps/cloudhub/account/switch-vendordb) | Profile, password, multi-account switching | | [Optimise, Inventory Hub](/vortex-apps/cloudhub/optimise-inventory/inventory-hub), [Graphical Dashboard](/vortex-apps/cloudhub/optimise-inventory/graphical-dashboard), [Import and Export](/vortex-apps/cloudhub/optimise-inventory/import-and-export), [Add a Product](/vortex-apps/cloudhub/optimise-inventory/add-a-product) | The \[Optimise] inventory module | | [Deliver, Orders overview](/vortex-apps/cloudhub/deliver-orders), [Scan Pack Ship](/vortex-apps/cloudhub/deliver-orders/scan-pack-ship), [Manual and FBA Orders](/vortex-apps/cloudhub/deliver-orders/manual-and-fba-orders) | The \[Deliver] order module | | [Compete, Repricing overview](/vortex-apps/cloudhub/compete-repricing), [Competition Analysis](/vortex-apps/cloudhub/compete-repricing/competition-analysis), [Repricing Rules and Status](/vortex-apps/cloudhub/compete-repricing/repricing-rules-and-status) | The \[Compete] repricing module | ## How CloudHub connects to the rest of the AI OS * [Nerve Centre](/nerve-centre/overview) tabs for each marketplace surface raw KPIs (sessions, conversion, BSR, buy-box win rate) that complement CloudHub operational metrics. * [Vortex Mind](/vortex-mind/overview) reports such as Daily Revenue Leakage and Customer Recovery Opportunity run against the unified order data flowing through CloudHub. * [Ask Viq](/ask-viq/overview) can answer "how many Amazon orders are stuck in Pending today?" and "which SKUs are blocked on eBay?" by reading CloudHub state. * [Actions](/actions/overview) findings such as "out of stock on eBay but in stock on Amazon" route into the relevant CloudHub Inventory Hub tab.