---
title: "Compare product revenue and units"
description: "Compare exact product revenue, paid orders, and units sold without reducing them to one score."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/revenue/compare-product-revenue-and-units"
format: inttegro-machine-docs/v1
language: "cURL"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/curl/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 547
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["get_product","get_product_analytics"]
estimated_tokens: 1127
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Compare exact product revenue, paid orders, and units sold without reducing them to one score. This cURL representation preserves HTTP paths and JSON wire names.

### Five questions

#### Q1. When should the reader use Compare product revenue and units?

Use this MCP document when an authenticated AI client needs governed Inttegro context, guidance, presentation, or operations.

#### Q2. What is authoritative on this page?

The documented MCP catalog defines available abilities and confirmation boundaries. For live state, the structured tool result is authoritative; presentation output is only a rendering of that result.

#### Q3. What page-specific constraint matters most?

Read operations do not authorize mutations. Actions retain their exact confirmation requirements, and payment credentials or OTP must stay in secure Checkout.

#### Q4. Can Inttegro MCP materially help with this task?

Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `get_product`, `get_product_analytics`; their exact roles and boundaries are listed below.

#### Q5. How should the reader verify the answer and continue?

Preserve the structured tool result, distinguish bounded lists from complete analytics, and reconcile asynchronous actions through an authoritative read. Continue with [get_product_analytics](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#get_product_analytics) when those concerns enter scope.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`get_product`](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#get_product) — read; no mutation confirmation. Gets one catalog product by ID with a compact, metadata-minimized projection.
- [`get_product_analytics`](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#get_product_analytics) — analytics read; no mutation confirmation. Ranks products or inspects one product by paid orders, units sold, and gross revenue for a selected period and currency.

## Document content

# Compare product revenue and units

Revenue and unit volume answer different questions. Keep both visible when comparing products with different prices or quantities per order.

### Prompt

> **Copyable prompt:**
>
> Compare the top products for the last 30 days in GHS by gross revenue, paid
> orders, and units sold. Show the exact values in a compact table and explain
> which products lead each measure. Do not calculate a composite score.

The agent uses [`get_product_analytics`](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#get_product_analytics). It reports the measures returned by Inttegro without treating revenue, orders, and units as interchangeable.

## Sample response: Product revenue and volume

The consultation leads revenue, while the event pass leads units sold.

- **Revenue leader**: prod\_consultation — GHS 14,250.00
- **Units leader**: prod\_event\_pass — 86 units
- **Paid-order leader**: prod\_event\_pass — 61 orders

* **Row 1**: Product: prod\_consultation; Gross revenue: GHS 14,250.00; Paid orders: 29; Units sold: 29
* **Row 2**: Product: prod\_event\_pass; Gross revenue: GHS 10,320.00; Paid orders: 61; Units sold: 86
* **Row 3**: Product: prod\_meetup\_kit; Gross revenue: GHS 8,960.00; Paid orders: 32; Units sold: 40

Any explanation for the difference should remain a hypothesis unless supported by product and price details returned by the catalog tools.