Order History and Reorder

Let customers browse past orders and rebuild one into the cart in a single action.

moderate User Accounts

What it adds

A per-customer list of past orders with their contents and documents, plus a control that adds a previous order's items back to the cart.

What your agent is told to do

1
List orders newest first with the details people scan for: date, total, item count, a thumbnail or two, and the current fulfilment status. Detail belongs on the order page.
2
Make reorder add items to the existing cart rather than replacing it, and show the resulting cart so the customer can review before paying.
3
Report what happened during a reorder. Say which items were added, which were unavailable, and which changed price, in one summary rather than a stack of separate alerts.
4
Reuse the app's existing PDF Export for invoices and receipts rather than generating documents a second way in this screen.
5
Do not copy the original prices or totals into the new cart. Reprice everything at today's catalogue prices, because the alternative is charging a price the business no longer offers.

Edge cases it handles

Products get discontinued, deleted, or go out of stock. Add what is available, skip the rest, and name each skipped item with the reason instead of quietly returning a shorter cart.
Repricing means the reorder total will often differ from the original. State the difference plainly before checkout rather than letting the customer discover it on the payment screen.
Long histories need pagination, and returning from an order detail page must restore the page, filters, and scroll position the customer left. Losing those on back navigation makes the list unusable.
Orders placed as a guest belong to the customer once they have an account with that verified email. Claim and merge them, and never attach an order on an unverified email match.
Refunded and cancelled orders must keep their invoices and receipts downloadable, showing the refund rather than disappearing from the history.
Variants change. If a previously purchased variant no longer exists, do not substitute a different one silently; flag it and let the customer choose.
Order documents contain a customer's address and purchase history. Authorise every download against the signed-in customer, not against knowledge of the document URL.
A customer clicking reorder twice must not double the quantities. Make the action idempotent for the duration of the request and disable the control while it runs.

Definition of done

A customer sees their past orders newest first with status and totals.
Reorder adds available items to the existing cart and shows the result before checkout.
Unavailable and discontinued items are named as skipped with a reason.
Cart lines are priced at current prices and any difference from the original order is stated.
Pagination, filters, and scroll position survive navigating into an order and back.
Guest orders appear once the account's email is verified.
Invoices and receipts remain downloadable for refunded orders and only to their owner.
The feature matches the existing design system.
No existing functionality is broken.

Related features

User Roles

Member Directory

Account Linking

How it works

1

Copy the link

Grab the Markdown instruction URL for this feature.
2

Give it to your AI

Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
3

It inspects, then implements

Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.