# Purchase frequency: formula and calculation example

> Divide valid orders in a defined window by the unique customers who bought in that same window.


**Average purchase frequency expresses how many orders each unique customer who bought placed during a defined window.** It uses valid orders in that window, not the monetary value of orders or the number of customers who made a repeat purchase.

**Purchase frequency = valid orders in the period ÷ unique customers with at least one order in that period.**

### Example: 420 orders in April

A store records 420 valid orders in April from 300 unique customers. Its average purchase frequency is **420 ÷ 300 = 1.4 orders per purchasing customer during April**.

The average does not mean every person placed 1.4 orders. It can hide different distributions:

| Distribution | Customers and orders | Total and average |
| --- | --- | --- |
| A | 180 customers placed 1 order; 120 placed 2 | 420 orders ÷ 300 customers = 1.4 |
| B | 280 customers placed 1 order; 20 placed 7 | 420 orders ÷ 300 customers = 1.4 |

Both stores have the same average, but the second group concentrates more orders among fewer people. Before deciding whether to send a replenishment reminder or review an offer for returning customers, examine orders per person and the product’s actual buying cycle. The average alone does not show when someone will buy again.

## Define which orders and customers count

Use the same period on both sides and count each unique customer once in the denominator. Decide whether to exclude canceled, duplicate, or returned orders, and keep that rule when comparing periods. In Google Analytics, `purchase` events use a transaction ID; `refund` events can be linked to that same transaction. If someone checks out as a guest or switches devices, the records may not recognize them as the same customer. [See GA4’s ecommerce documentation](https://developers.google.com/analytics/devguides/collection/ga4/ecommerce?hl=en).

Frequency counts **orders per purchasing customer**. [Average order value](/en/guides/average-order-value/) measures money per order, while [repeat purchase rate](/en/guides/repeat-purchase-rate/) counts what share of buyers are identified as returning. To find the average time between orders, you need each customer’s purchase dates; you cannot get it by dividing the days in the period by this frequency. The metric also does not, by itself, project customer lifetime or value.

*The orders, customers, and groups in distributions A and B are fictional. They show how two groups can have the same average and different compositions; they do not describe real stores.*

The cover is an AI-generated illustration.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
