Reading order activity history

Edited

Overview

The order activity history is a chronological log of everything that's ever happened to an order: status changes, notes, refunds, reassignments, edits. It's the source of truth when reconciling disputes, auditing rep activity, or troubleshooting a webhook issue.

Where to find it

  1. Open an order under Sidebar > Orders.

  2. Scroll to the Activity section, usually below the line items.

  3. Newest events appear at the top. Click any row to expand for details.

Event types

  • Status changed — every transition (e.g., pendingcommitted) with old/new values.

  • Payment captured — Stripe webhook confirmation with charge ID.

  • Refund issued — full or partial refund with amount and reason.

  • Note added — internal or visible note with author and content.

  • Rep reassigned — old and new rep with timestamp.

  • Line item edited — quantity, price, or discount adjustments.

  • Email sent — receipts, reminders, manual sends.

How to use it

  • For sponsor disputes, scroll to the original creation event for context.

  • For revenue reconciliation, filter to Payment captured and Refund issued.

  • For team accountability, sort by author to see who made which change.

Tips & best practices

  • Combine activity history with the audit log under Settings > Audit log for chamber-wide visibility.

  • Export the activity history as JSON for legal or compliance archives.

  • If a webhook event looks missing, check the Stripe dashboard's events tab to confirm it fired.

FAQ

Can I delete an activity entry?
No. The log is immutable to preserve auditability.

How far back does history go?
Forever. Every event since the order was created is retained.

Are sponsor-side actions logged?
Yes — sponsor checkouts, refund requests, and self-service edits all appear with the sponsor as the author.

Related articles

  • Order status lifecycle

  • Adding internal notes to an order

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.