Skip to main content
CloudHub is built around a multi-account model. A single user login can have access to several distinct trading entities, each identified by a VendorDB code, and you switch between them on the fly. This is how brand groups, multi-entity retailers, and 3PL operators run several distinct businesses on one CloudHub login without cross-contaminating data. This page explains the VendorDB model, how to switch between them, and what reloads when you do.

​
What a VendorDB is

A VendorDB is the unit of trading-entity isolation in CloudHub. Each VendorDB is a separate database tenancy that holds:
  • The master SKU catalogue.
  • The marketplace account credentials (Amazon, eBay, OnBuy, Cdiscount, FNAC, etc.).
  • The warehouse and stock locations.
  • The repricing profiles.
  • The order workflow.
  • The user permissions and the user list.
  • The accounting and reporting data.
Two VendorDBs share nothing operationally. A SKU in 247C1007 is not visible from 247C1035. A pending order in one is not in the queue of the other. This is intentional. It is the segregation that makes CloudHub safe to use across many trading entities.

​
VendorDB code naming

VendorDB codes follow a pattern of 247C plus a four-digit identifier, plus a human-readable trading entity name. Examples from a real environment:
VendorDB CodeTrading Entity
247C1005Channels Ahead Demo Store
247C1007The Monogram Group Limited
247C1035Five Diamond Trading Limited
247C1038Devils in the Detail
247C1041Rejel Automotive Parts Ltd
247C1050W.C.Maunders Ltd
247C1051Champion Dreams Limited
247C1060Netprice Direct, CH
247C1061Test
247C1062Krispy Kreme UK Ltd
SellerDB247commerce (the demo / sandbox tenancy)
The codes are issued by 247Commerce when a new entity is provisioned. They are not editable from inside CloudHub.

​
How to switch VendorDB

  1. Click the 247 avatar in the top-right of the navigation bar. The dropdown menu appears.
  2. Click Switch VendorDB at the top of the menu.
  3. The Switch VendorDb Details modal opens in the centre of the screen.
  4. The modal shows a single field: VendorDb Code, with a dropdown that defaults to the currently active VendorDB.
  5. Click the dropdown. A scrollable list of every VendorDB you have access to appears, with the codes and entity names laid out as in the table above.
  6. Click the VendorDB you want to switch to. The dropdown closes with that VendorDB displayed.
  7. Click the blue Change button.
CloudHub reloads with the newly selected VendorDB as active. You land on the CloudHub dashboard for the new entity.

​
What reloads when you switch

Everything that is scoped to a trading entity reloads with the new entity’s data. That is essentially the entire app:
  • The dashboard’s Sales Report, Lifetime KPIs, Fast Selling Lines, Count of Orders, and Sales Revenue pie all redraw for the new entity.
  • The Inventory Hub shows the new entity’s master SKU catalogue with its own marketplace tabs.
  • Pending Orders, FBA Orders, Manual Orders, Scan Pack Ship, and the courier manifest queue all reload.
  • The Repricing dashboards, competition analysis, and rule sets reload.
  • Reports, warehouse, and configure pages reload.
  • The footer “Licensed to” caption updates to show the new entity name.
The only things that do not change are your user identity (you are still signed in as the same person) and your access entitlements (the list of VendorDBs you can see).

​
Cancelling without switching

The modal has a small x in the top-right and grey-out behind it. Click the x or click outside the modal to close it without changing the active VendorDB.

​
When to use Switch VendorDB

  • End of day reconciliation, after closing the books on one entity, switch to the next and repeat.
  • 3PL operations, switching between client tenancies as you action each one.
  • Brand-group oversight, the parent operations team checks each brand’s pending order queue in turn.
  • Demo / sandbox, switching to the SellerDB 247commerce sandbox to try a feature without touching production data.

​
Common questions

Can I open two VendorDBs in two browser tabs? Yes. CloudHub stores the active VendorDB in your session, and a second browser tab uses the same session. Switching VendorDB in one tab will affect the other on the next page load. If you need true side-by-side, use two different browsers (or one browser plus an incognito window) and sign in twice. Why is a VendorDB I expect to see missing from the dropdown? You do not have access. Permissions to VendorDBs are granted at the user-record level by a super-admin. Ask your CloudHub admin or your 247Commerce account manager to grant access. The dropdown only shows one entry: SellerDB 247commerce. You only have access to the demo VendorDB. If you should have access to a live trading entity, contact your account manager. New CloudHub deployments often start in the demo VendorDB and are migrated to a production VendorDB once the marketplace credentials are validated. I switched VendorDB but the URL still shows my old one in the address bar. The URL caches the route, not the active VendorDB. The active VendorDB is in your session. Click any link in the navigation to refresh the route to the new VendorDB context. Can I rename a VendorDB code or entity name? Not from inside CloudHub. The codes are issued by 247Commerce. To rename a trading entity, contact your account manager. I see a VendorDB labelled “Test”. What is that? That is a test tenancy, often used by 247Commerce internal staff or by a customer who has been given a sandbox to validate a workflow. Do not run live operations against it; it is not connected to real marketplace accounts.

​
Next steps

  • Edit your profile or password on Edit user and password.
  • Open the new VendorDB’s dashboard.
  • Set up new marketplace accounts for the active VendorDB via the [Configure] section (documented in a later batch).