Potato Ledger for ShopifyShopify analytics that explains profit, not just sales.
Shopify analytics shows what happened. Potato Ledger explains what made money — revenue and cost mapped to the same governed contribution model, at a declared grain.
Who it is for
Shopify operators who want decision-grade contribution clarity rather than another dashboard layer. Calm, governed measurement instead of dashboard theatre.
How we use your data
We need historical order activity to calculate past trends and explain contribution. We do not need to know who individual customers are to do that.
- We request approved Shopify scopes only — including
read_orders, and read_all_orders where historical depth is required for forecasting. - We do not ingest customer names, email addresses, phone numbers, or shipping or billing addresses by default.
- Raw source evidence is kept separate from serving outputs. Analytical surfaces expose aggregated metrics, not personal identifiers.
How we measure
The billable unit is order activity: a unit accrues when an order sees a qualifying data change in the billing period and is processed through the Potato Ledger pipeline.
- Qualifying changes include order creation, materially relevant updates, fulfilment or dispatch changes, refunds, and return-related financial changes.
- We do not price on lifetime order count or static warehouse volume.
- The same order may contribute more than once across its lifecycle. Pricing follows activity in each period, not “one order, one charge forever.”
- Metadata churn, duplicate ingestion with no downstream change, and reprocessing caused by Potato Ledger defects are out of scope for default charging.
Published tariff (GBP)
Cumulative banded usage. Minimum monthly charge £20 applies when usage in the period would otherwise bill below that amount.
Unit rates by monthly order-activity volume| Monthly units (in band) | Unit rate |
|---|
| 1–1,000 units | 10p per unit |
| 1,001–100,000 units | 5p per unit |
Worked charges (illustrative)
Examples at published band rates; the minimum monthly charge can apply for low-usage months.
Monthly order-activity units → indicative charge| Units in period | Indicative charge |
|---|
| 100 | £20 |
| 1,000 | £100 |
| 10,000 | £550 |
| 100,000 | £5,050 |
Enterprise boundary. Pricing remains tied to measured operations above 100,000 monthly units, but recurring charges are reviewed as an enterprise line until a later governed tariff is adopted.
What you get
Productised delivery, not open-ended consultancy. Dashboards are how you read outputs; the contribution model is the governed truth layer.
- Governed measurement aligned to order activity in the period.
- Published GBP tariff bands with transparent worked examples.
- Clear boundary for enterprise review on very high monthly volume.
- Aggregated metrics by default; minimum required data only.