The store has more orders than the profile has purchases? Compare scope and status first. DropUI does not count every created order as a purchase for analysis.
Which purchases qualify
A purchase must be linked to the right person and store, with order status Completed and payment Paid. Records with a recorded return in fulfillment are excluded.
Future orders and records outside the available 730-day history do not count. An order awaiting payment or merely created does not increase qualifying purchase count.
Compare summary scopes
| Location | Scope |
|---|---|
| Purchase profile and ordinary segment purchase rules | Qualifying purchases in the available store history |
| R in RFM | Latest qualifying purchase in available history for the selected currency |
| F and M in RFM | Qualifying purchases in the last 365 days for that currency |
The profile total therefore need not equal M. Read the RFM definitions before comparing different tables.
What recorded value means
The summary uses order value including shipping. Currencies appear separately; do not add PLN and EUR as if they were one sales amount.
Partial refunds are not automatically deducted from this summary. Recorded value is not margin, profit or revenue attributed to a particular campaign.
Anna bought serum for USD 149 and cream for USD 89: USD 238 in total and USD 119 on average. Her third order, unpaid DEMO-1046 for USD 149, does not increase her purchase count. That is why her order list has three records while her purchase profile shows two purchases.
Investigate a specific difference
- Open Orders for the correct store.
- Find the order and check date, payment, fulfillment and currency.
- Check the associated contact.
- Compare store update time with analysis calculation time.
A missing contact link is different from an order-status issue. Check identity matching and synchronization separately.
Report a specific order number and the summary you are comparing. Do not alter store statuses simply to produce the expected count.

