Skip to main content
The [Deliver] module is where every marketplace order lands, gets picked, packed, shipped, and confirmed back to the source channel. Where Optimise manages the catalogue, [Deliver] manages the lifecycle of an order from “the customer paid” to “the carrier scanned the parcel”. This page is the section landing for [Deliver]. It covers the Graphical Dashboard, the Pending Orders queue, and signposts to the deeper workflow pages.

​
How to open

  1. Click Services.
  2. Open the Order Management System [Deliver] module.
  3. The module sub-menu lists every page in [Deliver]: Graphical Dashboard, Pending Orders, Scan Pack Ship, Manual / Telephone Order, FBA Orders, Generate Manifest and Cancel Shipments, Order Export Status Monitor, PDF Print Log, Print Console Print Log.
The breadcrumb on every page reads Home > Deliver > (current page).

​
Deliver Graphical Dashboard

The Graphical Dashboard is the [Deliver] equivalent of the Inventory Graphical Dashboard. It is a summary of the order pipeline, broken down by stage and channel. Open it via Home > Deliver > Dashboard. The dashboard surfaces:
  • Orders by stage, the count at each step of your configured Order Workflow (e.g. New, Pending, Picked, Packed, Shipped, Cancelled). The stages themselves are configurable in [Configure] > Deliver Order Stages Settings.
  • Orders by marketplace, the same count split by Amazon, eBay, OnBuy, FBA, etc.
  • Late shipments, orders that have crossed their dispatch SLA without being shipped. This is the panel ops managers should watch most closely.
  • Cancelled orders, the cancellation count broken down by reason and marketplace.
  • Order age distribution, a histogram of how long orders have been in their current stage.
In the screenshot, the Deliver dashboard shows a “Please wait…” loading state because data was still being fetched at the moment of capture. Once loaded, the panels above populate with live data scoped to the active VendorDB.

​
Pending Orders

Pending Orders is the single queue across every marketplace of orders waiting to be processed. Open via Home > Deliver > Pending Orders.

​
Top filters

​
Columns

When the queue is empty for the selected account, the page displays “No Records Found.” beneath the filters. This is the desired state at end of day; an empty Pending Orders queue means everything is already in flight.

​
Why a unified queue matters

Different marketplaces have different SLAs (Amazon Prime is 24-48 hours, eBay Fast ‘N Free is 1 day, OnBuy is more relaxed). The unified queue lets a packing team work to a single FIFO order rather than tab-switching between four different seller dashboards. Pair it with the Scan Pack Ship workflow for the actual fulfilment leg.

​
Order workflow stages

CloudHub’s order pipeline is stage-driven. Each VendorDB has a configured set of order stages (the screenshot from the Scan, Pack and Ship export view shows examples like Picked, Dispatched, Cancelled, Dispatched Confirmed). The bulk-action strip carries buttons to move orders between stages: The exact bulk actions visible depend on your role and the [Configure] > Order Workflow setup for the active VendorDB.

​
Pages in this section

​
How [Deliver] connects to other modules

  • A pending order’s stock is decremented in Optimise the moment the order lands, preventing oversells across channels.
  • Cancellation events feed back to Optimise and the marketplace listings.
  • Tracking numbers and shipping costs flow into the [Analyse] reporting module (Late Shipments, Shipping Costs reports).
  • Warehouse stock movements happen in [Locate].
  • Carrier configuration, shipping rules, and document templates live in [Configure].

​
ShipBob and 3PL fulfilment

CloudHub orders that should be fulfilled by ShipBob (or another 3PL) follow this lifecycle:
  1. The order lands in CloudHub Pending Orders from the source marketplace.
  2. The order workflow routes it to the 3PL connector instead of the in-house warehouse.
  3. The 3PL receives the order, picks, packs, and ships.
  4. The tracking number is written back to CloudHub.
  5. CloudHub forwards the tracking to the source marketplace.
  6. The order moves to Dispatched stage.
The 3PL leg is owned by the platform-level connector, not by CloudHub itself. ShipBob is already live as a Vortex IQ connector; cross-link to its Nerve Centre tab for raw fulfilment KPIs.

​
Common questions

I have an order in the marketplace but it is not in CloudHub Pending Orders. Marketplaces poll on a schedule (Amazon every few minutes, eBay every few minutes, OnBuy slower). Wait one polling cycle. If still missing, check the marketplace account’s Last Sync timestamp and any error markers in [Configure] > Marketplace Accounts. Can I process a single order without using the picksheet? Yes. The Scan, Pack and Ship page has a Process Orders one by one tab for exactly that. An order is stuck on “Pending” stage with no Master Quantity. The SKU on the order is not in the master catalogue or has no quantity. Open the order, identify the SKU, and either add it to the master via Add a Product or replenish stock. The dashboard says “Please wait…” and never finishes loading. Almost always a data fetch issue. Hard-refresh the page. If it persists for a specific VendorDB, contact support with the VendorDB code. Can I split an order across two warehouses? That depends on the Order Workflow configuration. The standard workflow ships a single order from a single warehouse. A multi-warehouse split workflow is configurable in [Configure] > Order Workflow but is not the default.

​
Next steps

  • Run the Scan, Pack and Ship workflow for the orders in your queue.
  • Process customer-service-led orders via Manual and FBA Orders.
  • Configure your warehouse and stock locations in [Locate] (documented in a later batch).
  • Tune order workflow stages in [Configure] > Order Workflow.