> ## 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 Operations Reports, Order Stages, Late Shipments, Shipping Costs > How to use the operational reports in 247CloudHub Analyse: Order Stages, Late Shipments, Shipping Costs, and Report Notifications for daily ops triage and SLA tracking. The four operational reports in 247CloudHub Analyse are what an ops lead opens every morning. They answer "where do orders sit, what missed SLA, what shipping really cost, and is the daily report still going to the right inbox." Together they replace the manual ops dashboard most multichannel teams used to maintain in a shared spreadsheet. ## Order Stages report Path: Home, Analyse, Order Stages. The Order Stages report shows a count of orders sitting in each stage of the configured workflow, one row per day in the date window. Default columns mirror the standard CloudHub stages but adjust to whatever your configured stages are under [Deliver Order Stages Settings](/vortex-apps/cloudhub/configure/workflows-and-pricing-rules#deliver-order-stages-settings). | Column | What it means | | ----------------- | ------------------------------------------------------------------------------- | | Just Arrived | Orders that have downloaded from a channel but not yet been routed for picking. | | Sent to Warehouse | Orders that have been allocated to a warehouse and are awaiting pick. | | Sent for Picking | Orders that are with a picker. | | Dispatched | Orders that left the warehouse. | | Backordered | Orders waiting on stock that is not currently available. | | Cancelled | Orders cancelled before dispatch. | | Refunded | Orders refunded post-dispatch. | Use cases: 1. **Daily standup.** A high `Just Arrived` count means the morning download is bigger than usual. A high `Sent to Warehouse` with a low `Sent for Picking` means picking is the bottleneck. A high `Backordered` count means inventory is the bottleneck. 2. **SLA enforcement.** If yesterday's `Just Arrived` is non-zero today, those orders did not move in 24 hours. That is a process miss to investigate. 3. **Marketplace performance defence.** Amazon and eBay measure dispatch on time. A back-stack of `Just Arrived` is the early warning that your account health metrics are about to slip. Common gotcha: the Order Stages report tracks the configured stages in your workflow profile. If you customised stages under [Order Workflow](/vortex-apps/cloudhub/configure/workflows-and-pricing-rules#order-workflow), the column set may differ. The categories are still pending, in-progress, complete, and exception, and the use case still applies. ## Late Shipments report Path: Home, Analyse, Late Shipment Summary. This report lists every order whose dispatch was later than the expected dispatch time defined by the configured workflow. | Column | What it means | | ---------------------- | --------------------------------------------------------------------------------- | | Date | The order date. | | Order No | CloudHub order number. | | Quantity | Units on the order. | | Expected Dispatch Time | The SLA dispatch deadline as calculated from order date and the workflow profile. | | Late By | How late the dispatch was, as a duration. | Use cases: 1. **Marketplace metrics defence.** Amazon Late Dispatch Rate is one of the few metrics that can suspend a seller account. Late Shipments lets you see exactly which orders triggered the metric, which marketplace they were on, and how much over the deadline they were. Critical for account health appeals. 2. **Carrier performance.** If a specific carrier shows up disproportionately in the Late Shipments report, that is a carrier conversation. Cross-check with [Shipping Costs](#shipping-costs-report) for the spend signal. 3. **Picking team performance.** Filter Late Shipments by warehouse and you can see whether one warehouse is consistently slower than another. Empty Late Shipments report = good news. It means every order in the window dispatched on time. Common gotcha: Late Shipments uses the `Expected Dispatch Time` from the workflow profile, not the marketplace SLA. If your workflow says 48 hours but Amazon Prime says next-day, the report does not flag the Prime miss. Verify your workflow SLA matches the strictest channel SLA you support. ## Shipping Costs report Path: Home, Analyse, Shipping Costs. The Shipping Costs report compares what you charged the customer for shipping with what you actually paid the carrier, by SKU. | Column | What it means | | ---------------- | ---------------------------------------------- | | SKU | Internal SKU. | | Product Name | Product name. | | No.of Orders | Order count in the window for this SKU. | | Shipping Charged | Sum of shipping revenue collected from buyers. | | Shipping Paid | Sum of shipping cost paid to carriers. | | Courier Name | Most-used courier for this SKU. | | Shipping Service | Service level (next-day, standard, etc.). | Use cases: 1. **Shipping margin audit.** Subtract `Shipping Paid` from `Shipping Charged` per SKU. Negative numbers are SKUs you are subsidising on shipping; positive numbers are SKUs where shipping is contributing to margin. Free-shipping SKUs need to compensate elsewhere. 2. **Bulky-item SKU pricing.** Bulky or heavy SKUs that consistently lose on shipping should either bake the cost into the unit price or be moved off "free shipping" tier promotions. 3. **Carrier mix optimisation.** Aggregate by `Courier Name` to see which carrier you are spending most with. Use that data in your annual carrier negotiation. The [Shipping & Carrier Configuration](/vortex-apps/cloudhub/configure/permissions-and-shipping#shipping-carrier-configuration) page is where you change carriers based on this analysis. Common gotcha: rows show only after a dispatch has confirmed both the customer charge and the carrier charge. Orders that are dispatched but pre-billed (some FBA orders, some marketplace-arranged shipping) may not appear, since the carrier cost is not visible to CloudHub. ## Report Notifications Path: Home, Analyse, Reports Notifications. This is the configuration page for scheduled emailed delivery of any of the Analyse reports. Each row is a recipient-report-frequency rule. | Column | What it means | | ---------------- | --------------------------------------------------------- | | Sl No | Row number. | | User Name | The CloudHub user who created the rule. | | Report | Which report (Sales, VAT, Returns, Late Shipments, etc.). | | Frequency | Daily, Weekly, Monthly. | | Time Of Day | When the email is sent, in the workspace timezone. | | Email Sent To | The recipient address. Comma-separate for multiple. | | Last Report Sent | Timestamp of the last successful send. | | Action | Edit and Delete links per row. | Add a new rule via the `Add Notifications` button at the top. Use cases: 1. **Daily ops digest.** Send Order Stages and Late Shipments to the ops lead at 08:00 every morning. The email arrives before standup. 2. **Weekly trade pack.** Send Sales and Fast Selling Products to the buying team every Monday at 07:00. The email is the agenda for the trade meeting. 3. **Monthly finance pack.** Send VAT and Returns to the finance inbox on the first of the month at 06:00. Self-serve reconciliation pack. Common gotcha: the recipient must be a valid email address. CloudHub does not currently support distribution lists by name; spell out the address. If a scheduled report stops arriving, check the `Last Report Sent` timestamp; if it is more than the frequency-cycle behind, edit the rule and re-save to re-arm the schedule. ## Cross-link to the rest of the AI OS | Need | Where to go | | ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | | Live ops KPI per channel | Nerve Centre, the connector card | | "Why are we late on Amazon dispatch this week?" | Vortex Mind, Decline Recovery Intelligence (or the late-shipment investigation playbook) | | "How many orders are stuck in Just Arrived right now?" | Ask Viq, plain-English query | | "Open a fix to investigate the recurring carrier-X late shipments" | Actions Kanban | ## Common questions **Can the Late Shipments report be customised to use a per-channel SLA?** Today, the SLA is set per workflow profile. If you operate with one workflow profile across all channels, the strictest SLA is the one to honour. For per-channel SLA, you can create separate workflow profiles in [Order Workflow](/vortex-apps/cloudhub/configure/workflows-and-pricing-rules#order-workflow) and assign per channel. **The Shipping Costs report is empty even though I dispatched orders. Why?** The most common cause: the `Shipping Paid` field is populated from carrier integration data. If your carriers are not integrated to CloudHub for billing data (only for label production), the report cannot show paid amounts. See [Shipping & Carrier Configuration](/vortex-apps/cloudhub/configure/permissions-and-shipping#shipping-carrier-configuration) for the data fields that need to be enabled. **Can I edit a Report Notification after creating it?** Yes. Use the Edit link in the Action column. The schedule re-arms from the next cycle. **Can I have one notification go to multiple recipients?** Yes. Comma-separate the email addresses in the `Email Sent To` field. ## Next steps * Continue with [Website Analytics](/vortex-apps/cloudhub/analyse-reports/website-analytics) for the webstore-side reports. * See [Customer Services](/vortex-apps/cloudhub/customer-services/index) for the live console where stuck orders are unblocked. * Configure your workflow stages under [Workflows and Pricing Rules](/vortex-apps/cloudhub/configure/workflows-and-pricing-rules).