Skip to main content
The [Optimise] module is where the master SKU catalogue lives. Every product CloudHub knows about begins life here, gets enriched with title / category / images / pricing here, and is pushed out from here to each marketplace. When a marketplace updates a quantity (a sale, a refund, an FBA replenishment), the change comes back into this module and the master record is reconciled. This is the core competency of CloudHub. If you remember nothing else about the platform, remember that the SKU master is held centrally in the Inventory Hub and the marketplace tabs are projections of that master.

​
The two views, master and marketplace

CloudHub gives you two complementary views of the same catalogue:
  1. Inventory Hub (Common Inventory), the master view. One row per SKU regardless of how many marketplaces it lists on. This is where you edit the canonical record. See Inventory Hub.
  2. Per-marketplace tabs, one tab each for the channels you sell on. Each tab is a projection of the master constrained to that marketplace’s listing rules. Edits made in a marketplace tab feed back into the master where they overlap.
You move between them by clicking Inventory Hub (Common Inventory) in the top-bar quick links for the master view, or by opening the [Optimise] module and clicking the marketplace tab you want.

​
Marketplace tabs

The Inventory Hub’s tab strip currently includes: A marketplace tab only appears once you have configured at least one Marketplace Account for it under the [Configure] module’s Marketplace Accounts page. If you have no FNAC account configured, the FNAC tab still shows as a header but the data area is empty.

​
Multi-account per marketplace

Each marketplace tab supports multiple accounts. You can run two Amazon Seller Central accounts (a UK account and a US account, for example) and CloudHub treats them as distinct. The Marketplace Account dropdown at the top of each tab lets you scope the view to one account at a time. This is how brands operate Amazon Europe regional accounts (UK, DE, FR, IT, ES) as separate listings while still holding a single master SKU.

​
Merchant-demand additions in flight

These three are currently the most-requested marketplace additions from the CloudHub user base. They are scoped on the roadmap but not yet shipping:
  1. Temu, the cross-border Chinese discount marketplace. Several CloudHub merchants have asked for native Temu listing sync to ride the volume wave without manually managing the Temu seller portal.
  2. TikTok Shop, the social commerce surface. UK and US TikTok Shop have moved from novelty to material GMV in the last year and CloudHub merchants are routing volume through it.
  3. Tesco Marketplace, the UK supermarket marketplace. FMCG and grocery-adjacent sellers are asking for Tesco as their next channel after Amazon UK.
If you have a strong use case for any of these, log a ticket through your account manager so the priority queue reflects real demand.

​
ShipBob and the platform-level fulfilment connectors

CloudHub owns multichannel listings and orders. Where a CloudHub order gets shipped from a 3PL like ShipBob, the fulfilment leg is handled by the ShipBob platform connector. The order originates in CloudHub from the marketplace, then routes to ShipBob for fulfilment, with ShipBob writing the tracking number back to CloudHub which forwards it to the source marketplace. ShipBob is already live as a Vortex IQ platform-level connector; you do not configure it inside CloudHub itself.

​
Pages in this section

​
How [Optimise] connects to other CloudHub modules

  • A SKU created here flows through to the [Compete] repricing module if you set min / max prices and FBA Product flag.
  • A SKU’s quantity is read by the [Deliver] module when an order arrives, to decrement stock and trigger reorder if you have a threshold.
  • The Listing Status Monitor and FTP Price Change Log surface in the [Analyse] reports.
  • Stock movements are tracked in the [Locate] warehouse module.

​
Common questions

My SKU is in the master but not appearing on the Amazon tab. Two checks. First, is the SKU assigned to your Amazon marketplace account? See the Marketplace Account dropdown on the Amazon tab. Second, has the SKU been pushed via the listing flow? Master records exist independent of marketplace listings; they only show up on a marketplace tab once they have been listed there. Can I list a SKU on a marketplace where I do not have an account configured? No. You must add the marketplace account in [Configure] > Marketplace Accounts before the tab will accept listings. The eBay tab shows a category count for a category I do not sell in. That is data from a previous catalogue cleanup or a marketplace account that was migrated. The Graphical Dashboard’s eBay Category Count panel shows historic counts. Cross-check against the live eBay listings on the eBay tab to confirm. My TradeMe / Allegro / Fruugo tab is empty even though I have an account. Some marketplaces have an initial sync that takes a few hours after first connection. If it is still empty 24 hours later, check the [Configure] > Marketplace Accounts page for the connection’s Last Sync timestamp and any error markers.

​
Next steps