Orders
Orders is the record of what people bought: one row per paid order, across every product and payment method.
The list
Section titled “The list”| Column | |
|---|---|
| #ID | The order number |
| Customer | Name and email |
| Product | What was bought |
| Paid | The amount. A discounted order shows the original price struck through; a free enrolment reads Free |
| Method | The payment provider, or Free |
| Type | Auto for a normal checkout, Manual for one you granted by hand |
| Date | When it happened |
Search by customer or product name. The filter button adds two more:
- Cost range — a minimum, a maximum, or both.
- Date range — orders between two dates.
Apply runs them; the button carries a badge with how many are active.
A single order
Section titled “A single order”Click a row for the full record:
- Product — what was bought, and for how much.
- Customer / Email — who bought it.
- Payment Method — how they paid.
- Coupon — the coupon used, if any.
- Access expires — when their access ends, for time-limited products.
- Traffic Source — where the buyer came from.
- User IP — the IP the order came from.
- Transaction ID — the provider’s reference, and what you quote in a payment dispute.
- Purchase disclaimer — the terms shown at checkout.
- Granted access — what the purchase actually unlocked.
Between Transaction ID and Traffic Source you have what you need for the two questions orders usually raise: “where did this sale come from” and “what exactly did this person pay for”.
Orders and the rest of the CRM
Section titled “Orders and the rest of the CRM”- The customer’s own record collects all of this under Payments / Invoices — see the contact record.
- What a purchase does — the access it grants, the tags it applies, where the buyer is sent — is configured per product, not per order. See after a purchase.
- Order placed is an automation trigger, which is how a purchase turns into a follow-up sequence.