Product Collection
Sticky filter sidebar, sort toolbar and product grid — with the facets dropped rather than stacked on mobile, so a shopping page does not open as a form.
The post-purchase screen, with navigation restored and a rail that shows what to buy next rather than what was just bought.
app/order-confirmation-page.tsxnpx hoverlab add order-confirmation-page
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
A confirmation is on its way to you@example.com
Order numberORD-4821-9930
Estimated delivery
–
We will email a tracking link as soon as it ships.
Merino Crew Sweater
Stone · M
×1
£89.00
Cotton Oxford Shirt
Sky · L
×2
£130.00
The real page, rendered in your current theme — every section below is a live block, not a screenshot.
Only want one section? Open it and copy that block instead — browse Orders & Reviews.
Want the whole project rather than this one screen? A template ships every route, the theme tokens and the layout.
/**
* The post-purchase screen.
*
* Navigation comes back here — the opposite of the checkout. The sale is
* done, and the useful next action is browsing again, so the header returns
* and the confirmation block ends with a link back into the shop.
*
* The product rail below is "you might also like" rather than "recently
* viewed": showing someone the item they just bought, three seconds after
* buying it, is the most common own-goal on this screen.
*/
import * as React from 'react'
import { OrderConfirmation } from '@/components/order-confirmation'
import { ProductRail } from '@/components/product-rail'
export default function OrderConfirmationPage() {
return (
<div className="min-h-screen bg-background text-foreground">
<header className="border-b border-border/60">
<div className="mx-auto flex h-16 max-w-5xl items-center justify-between px-4 sm:px-6">
<a href="/" className="flex items-center gap-2 font-semibold tracking-tight">
<span
aria-hidden
className="flex h-8 w-8 items-center justify-center rounded-xl bg-primary text-primary-foreground"
>
A
</span>
Acme
</a>
<nav aria-label="Main" className="flex items-center gap-5 text-sm">
<a href="/" className="text-muted-foreground transition-colors hover:text-foreground">
Shop
</a>
<a
href="/account/orders"
className="text-muted-foreground transition-colors hover:text-foreground"
>
Orders
</a>
</nav>
</div>
</header>
<main>
<OrderConfirmation />
<div className="mx-auto w-full max-w-5xl border-t border-border/60 px-4 py-12 sm:px-6">
{/* Not "recently viewed" — they just bought that. */}
<ProductRail heading="You might also like" />
</div>
</main>
</div>
)
}
components/ — each block page has its own copy button.app/order-confirmation-page.tsx. The imports already point at @/components/…, so they resolve with no edits.The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
Sticky filter sidebar, sort toolbar and product grid — with the facets dropped rather than stacked on mobile, so a shopping page does not open as a form.
Gallery, sticky buy box, details accordion and reviews — ordered by what a shopper needs before they can decide.
Editable lines beside a sticky summary, so the total and the checkout button survive a scroll through four quantity changes.
Address and payment with the site navigation stripped and the order summary moved above the form on mobile — both aimed squarely at completion rate.
Order history in the settings shell rather than a second sidebar layout — an account area and a settings area are the same shape.
The page between a listing and a product detail, with the two questions a comparison table alone cannot answer: will it fit, and can I actually have it.
Checkout for the buyer who will not fill in a form: wallet buttons above the fields, and the address a wallet returns shown and changeable before the charge rather than after it.
For the customer with an order number and no account — a lookup, an arrival range rather than a promised date, and the review form where the "how did we do" email actually lands.