Order Tracking Page
Let customers check where their order is without emailing support.
What it adds
A per-order status page showing the order's current state and shipment progress, reachable by signed-in customers and by guests with an order number and email.
What your agent is told to do
5
What your agent is told to do
5-
1
Show the order's own state and its shipment progress as two separate things. An order can be paid and confirmed while nothing has shipped, and a delivered parcel does not close an order that has a second parcel outstanding.
-
2
Give guests a lookup that requires both the order number and the email on the order, and give signed-in customers direct links from their order history. The same page serves both, with the same information.
-
3
Present carrier progress as a small number of plain states with a timestamp on each, and label the most recent one as current. Do not render the carrier's raw event codes.
-
4
Reuse the app's existing Status Indicator System for the state treatments and, if orders arrive through Shopify Order Import or WooCommerce Order Sync, read status from those records rather than maintaining a second copy.
-
5
Do not put the order behind a bare guessable URL. Order numbers are sequential in most systems, so the page must require the second factor and must not confirm that a number exists when the email does not match.
Edge cases it handles
8
Edge cases it handles
8- A guest lookup must prove the requester knows both the order number and the email on the order, and must return the same response for a wrong email and a nonexistent order so the form cannot be used to discover which orders exist.
- An order can ship in parts. Show each parcel as its own tracked leg with its own items and its own progress, rather than collapsing them into one misleading status.
- Carrier feeds go stale, skip states, and occasionally move backwards. Show the last successful update time, never move a shipment backwards in the displayed timeline, and say the tracking has not updated recently rather than implying the parcel is stuck.
- Lookups must be rate limited per address and per order number so the form cannot be used to enumerate orders. Reuse the app's existing Rate Limiting rather than adding a counter here.
- Cancelled, refunded, and returned orders need their own copy and their own end state. A refunded order showing a delivery estimate reads as a system that has lost track of itself.
- The page must be safe to forward. Assume the link and its contents end up in a shared inbox, and keep full payment details and any unrelated customer data off it.
- An order placed minutes ago has no tracking at all. Say that fulfilment has not started yet rather than showing an empty timeline.
- Timestamps must render in the customer's time zone and locale, and delivery estimates should be a date range rather than a false-precision time.
Definition of done
9
Definition of done
9- A guest can find their order with the order number and matching email, and cannot with a mismatched one.
- Wrong-email and nonexistent-order lookups are indistinguishable in response and timing.
- Lookups are rate limited through the app's existing limiter.
- Split shipments appear as separate legs with their own items and progress.
- Stale carrier data is labelled with a last-updated time and never rewinds the timeline.
- Cancelled, refunded, and returned orders show state-appropriate copy and no delivery estimate.
- Order status is read from the app's existing order records rather than a duplicate store.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Feedback Widget
Feedback Widget
Let anyone report a bug or send a comment from the page they are looking at.
What it does
An always-available launcher that opens a short feedback form and submits it with page context attached.
How it works
- 1 Put a single persistent launcher in one corner of the app and open a compact form in place. Do not route the user to a separate feedback page and lose the context they were about to describe.
- 2 Attach the current URL, the app version, the viewport size, the signed-in account, and a short trail of recent client errors automatically, so the reporter does not have to describe where they were.
- 3 Show the captured context to the user before they send it, in a collapsible section, and let them remove it. Silent collection of screen state is a trust problem.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/feedback-widget
Interactive Transcript
Interactive Transcript
Put the transcript next to the player so clicking any line jumps playback to that moment.
What it does
A time-aligned transcript panel beside the audio or video player, with click-to-seek, a moving highlight, and in-transcript search.
How it works
- 1 Render the transcript from the timestamps the app already stores. If Voice Transcription exists, extend its output and its data model rather than producing a second transcript with its own timings.
- 2 Make every line a real seek target: clicking or pressing enter on a line moves playback to that time and keeps focus where the user left it.
- 3 Highlight the line currently being spoken and keep it in view as playback advances, using the player's own time updates rather than a separate timer.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/interactive-transcript
Relative Time Component
Relative Time Component
Show times as ages people can read, without losing the exact moment underneath.
What it does
One shared timestamp element that renders an age in words and carries the precise local date with it.
How it works
- 1 Find every place the app prints a date or a time — activity feeds, comment headers, audit rows, table cells, tooltips — and route them all through one component so the wording is identical everywhere.
- 2 Render from a machine-readable instant supplied by the server in a single unambiguous format, and do the conversion to the viewer's zone at display time rather than storing a formatted string.
- 3 Refresh the visible text on a schedule that matches its own granularity: something a few seconds old updates often, something two days old does not need to update at all.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/relative-time-component
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.