The whole story of every sale. What happened, when, and who did it.
Order #4821
Every event, with its actor
Payment Initiated
Sep 28, 2:32 PMCustomer
Payment Completed
Sep 28, 2:33 PMSystem
Order Shipped
Sep 28, 2:33 PMSystem
Order Completed
Sep 28, 2:34 PMSystem
Who placed it
mara@northaven.co$3,240.00$3,240.00 LTV
- Every event
- with who did it, and when
- Drafts
- kept out of your numbers
- A timeline, not a status field
- Payment captured, delivery issued, refund requested: each event is a row with an actor and a timestamp, and every one of them opens up to be read.
- Drafts stay out of the way
- Abandoned checkouts are kept as drafts and excluded from the views meant to show real sales, so the numbers you work from are not quietly inflated.
- Crypto invoices inline
- An on-chain order shows its invoice, its address and its confirmations in the order itself, so nobody has to keep a block explorer open in another tab to follow it.
- Refunds that reconcile
- Refunds are recorded against the original capture rather than as fresh rows, so revenue, payouts and the customer's history all stay in agreement.