Review orders and revenue context
Use synchronized order records to understand customer value, product demand, and lifecycle outcomes without confusing order state with collected revenue.
What you’ll achieve
- Order and revenue analysis based on correct status, product, customer, and currency context.
Suivez le flux de travail
-
1
Open Data → Own Data → Orders
Select the connector and account, then filter or search by date, status, order identity, customer, or other available fields.
-
2
Check order state
Review created and updated times, financial status, fulfillment status, cancellation or refund state, currency, subtotal, discounts, tax, shipping, and total.
-
3
Inspect line items
Confirm products, variants, quantities, prices, discounts, and product links. Product-level behavior is essential for affinity, cross-sell, and replenishment logic.
-
4
Open the linked contact
Use the customer relationship to review consent, earlier activity, other orders, product affinity, and campaign interactions. Do not assume every guest order can be identified.
-
5
Interpret revenue carefully
Separate created orders from paid, fulfilled, canceled, refunded, test, and draft states. Use a consistent currency and status definition when comparing campaign outcomes.
-
6
Verify lifecycle triggers
For purchase, post-purchase, win-back, or replenishment workflows, confirm the intended event is recorded once and stop conditions prevent inappropriate follow-ups.
Verify your work
- A sampled order matches the commerce source totals and status
- Line items link to the intended products and contact where available
- Purchase-triggered workflows receive one correct event
If something doesn’t look right
An order is missing
Check connector permissions, sync time, source status, and account filter.
Totals do not match
Inspect discounts, tax, shipping, refunds, currency, and the reporting status definition.
A contact is absent
Guest or privacy-limited orders may lack a usable identity link.
Limitations and safeguards
Orders can update after creation; refunds, cancellations, fulfillment, exchange rates, and connector latency can change later reporting.