Managing Customers

Every email address that's ever made a purchase becomes a customer record in Customers. Storra builds the record automatically — there's no separate "create customer" flow — and updates it on every subsequent purchase, refund, or support ticket.

The customers list

The Customers page is a sortable table:

• Email — primary identifier
• Username — Minecraft username (most-recent if multiple were used)
• Orders — count of paid (non-refunded) orders
• Lifetime spend — sum of paid order totals
• Last activity — most-recent purchase or visit
• Status — Active, Banned, or Anonymized

Click any row to open the customer detail page.

Filtering & search

• Search — matches email, username, or order ID prefix
• Status filter — Active / Banned / Anonymized
• High value — quick filter for top-1% spenders
• At risk — customers with refunds + chargeback history
• Recent — bought in the last 30 days

Customer detail page

Each customer page shows:

Identity

• Primary email (the one they checked out with)
• Linked Minecraft username + UUID
• Linked Discord account (if connected)
• Country code (resolved from their last-known IP)
• First / last purchase dates
• Account-level dispute history (chargebacks, abandoned baskets)

Orders timeline

Reverse-chronological list of every order, with status badges (paid, refunded, failed) and quick links to each order's detail page. Click an order to refund, redeliver, or view delivery logs (see Orders & refunds).

Support tickets

If you have storra.support installed, the customer's support history shows here as a stack of tickets. Quick triage from the customer page without bouncing to Support.

Notes (private)

The Notes box is staff-only — visible to owners + admins on your team but never to the customer. Use it for context that should travel with the customer:

• "VIP — donated $500 to our charity drive"
• "Refunded once after a delivery failure on our end — be generous on retries"
• "Asked nicely about a custom rank, follow up after launch"

Notes auto-save as you type. Edits are audit-logged with the editor's name.

Banning a customer

Click Ban, enter a reason. The customer:

• Can no longer create new orders (checkout returns "This account has been restricted")
• Can still log into existing orders to download files / view receipts (we don't strip access to things they've already paid for)
• Can no longer open new support tickets

Use bans for: chargeback abuse, fraud, harassment of staff, repeated TOS violations on your server. Less serious offenders are usually better handled with a polite refund + decline-future-orders note.

Unbanning

Click Unban on a banned customer's page. Their account immediately returns to Active. Order / refund history is unchanged.

Customer mergers

Future If a customer changed emails (gmail → custom domain), you'll currently see two customer records. The merge tool to combine them is on the post-launch roadmap.

GDPR / privacy operations

Export data (Subject Access Request)

Click Export data on the customer page. Storra generates a JSON archive containing:

• Customer record (email, username, country, signup metadata)
• Every order with line items, prices, gateway transaction IDs
• Every refund
• Every support ticket + reply
• Abandoned baskets (last 90 days)
• Gift cards issued + balance / redemption history
• Connected Discord account ID
• Webhook events that referenced the customer

Download arrives as a single ZIP. Email it to the customer to fulfill an Article 15 SAR within the GDPR-required 30-day window.

Anonymize (Right to Erasure)

Click Anonymize, then confirm. Storra:

• Replaces email with anonymized-{order_id}@deleted.storra.xyz
• Replaces username + UUID with [anonymized]
• Strips IP from order records
• Strips support-ticket message bodies (replaces with [anonymized at customer request])
• Keeps aggregate data: amounts, currency, gateway transaction IDs, order status, refund status

Anonymization is irreversible. You cannot rebuild the record after anonymizing.

Why doesn't Storra just delete?

Hard-delete would orphan financial records and break tax/audit trails. GDPR Article 17 specifically allows retention for legal compliance. Anonymization satisfies the spirit of erasure (no link back to a person) while keeping the legally-required ledger.

Exporting all customers

The Customers page has a Export CSV button (top-right). Generates a CSV with email, username, country, order count, lifetime spend, and last-activity. Download is rate-limited to once per hour to prevent accidental data dumps.

FAQ

Why can't I add a customer manually?

Customer records are derived from purchases. There's no concept of a "customer who hasn't bought anything" — that's just an email. If you want to send promotional emails to a list, use a separate ESP (Mailchimp, Resend) and import the list there.

What about customers who never buy but visit a lot?

Storra doesn't track unpurchasing visitors as customers. For storefront analytics (visitors, conversion rate), use the Analytics page (or wire up GA4 via the Essentials app's tracking integration).

Can I see what packages a customer is most likely to buy next?

Not currently — recommendation engines aren't shipped at launch. The Upsells feature handles the "you might also like" rail at checkout based on basket contents.

Two customers used the same Discord account — how is that handled?

Discord links are stored per-customer-record, not enforced unique across customers. If both customers genuinely bought, both records get the link. If you suspect account sharing, leave a note on each and reach out.