Surfaces
Shop Orders
Shop order management, payment review, buyer-visible updates, internal notes, and fulfillment state.
First created Last updated
Overview
Shop Orders is the operator workspace for ecommerce-style order management. It is similar to the attendee rego page in that staff can find a record, review payment state, inspect details, and update the buyer. It is separate from attendee registration approval: confirming a shop payment does not create or approve a rego.
Dashboard route
/ems/manage/shop-orders?id=:eventId
Order list
The list can be filtered by payment status, order status, and fulfillment status. Export CSV downloads the currently filtered order result set for operations or accounting review.
Each row shows order reference, buyer name/email, total amount, fulfillment method, linked-rego marker, payment status, and order status.
Payment review
| Action | What it does | Check first |
|---|---|---|
| Confirm | Marks payment confirmed and moves the order to paid. | Verify payment proof, reference, payment account, and amount. |
| Reject | Marks payment rejected and records the review note. | Include a clear reason so the buyer can resubmit. |
Payment review sends buyer notification hooks when configured. It also keeps shop side effects separate from registration rows.
Detail view
The detail panel shows:
| Section | What to inspect |
|---|---|
| Items | Item snapshot, quantity, unit price, category, source type, and item fulfillment status. |
| Timeline and notes | Buyer-visible updates and internal non-buyer notes. |
| Claim history | Release records, lookup method, staff account, claimant name, and notes. |
Use internal notes for staff-only handling context. Use buyer updates when the buyer should see the status message in their order timeline.
Status updates
Operators can move orders through ecommerce-style states such as paid, preparing, ready for pickup, released, fulfilled, shipped, delivered, cancelled, rejected, voided, and exception. Status changes also synchronize fulfillment status and operational timestamps where applicable.
| Status group | Operational meaning |
|---|---|
| Preparing | Staff are gathering or packing the order. |
| Ready for pickup | The order can be released on the claim page. |
| Shipped or delivered | Delivery fulfillment has moved beyond packing. |
| Released or fulfilled | Pickup or claim is complete. |
| Cancelled, rejected, voided, exception | Stop fulfillment and review payment, stock, or support context. |
Attendee-facing flow
Buyers can browse the public event shop, use a persistent cart, checkout with profile-prefilled details where possible, submit payment proof/reference, and review their shop order timeline from the transactions area. Cart and checkout totals are calculated by the API; browser state is advisory only.
Common mistakes
- Do not confirm a shop payment from a screenshot alone if the receiving account and amount do not match.
- Do not use buyer-visible updates for staff-only notes.
- Do not mark ready for pickup unless the physical order is actually ready to release.
- Do not treat shop orders as attendee registrations. They may link to a rego, but they do not replace rego management.