Next.js Commerce — Product details

A large product image shares the screen with a compact buying panel: price, variants, and one add-to-cart action.

Public demo · 2026-09-04Open full image ↗

Why this pattern works

Use a stable product gallery next to explicit variant controls. Show unavailable choices and keep the purchase action close to the selected options.

Design notes

Surface: Product detail with color and size options
Navigation: Shared store navigation and search with cart entry at the top.
Layout: Large image gallery occupies the left two-thirds; title, price, variant controls, and action occupy the right.
Density: Generous gallery; compact aligned option groups.
Color: White background, black text, blue price and call to action.
Type: Large product title; compact uppercase group labels and readable pill options.
Pattern: Make option selection visible and show why the action is unavailable before valid choices are made.
States: Unselected size with a subdued add-to-cart control; unavailable color is visibly muted.
Don't: Do not preselect unavailable variants or present a disabled action without explaining what the shopper needs to choose.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Next.js Commerce — Product details
Source: https://demo.vercel.store/product/acme-geometric-circles-t-shirt
Swipefile reference: https://swipefile.design/ref/commerce-product/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Product detail with color and size options
- nav: Shared store navigation and search with cart entry at the top.
- layout: Large image gallery occupies the left two-thirds; title, price, variant controls, and action occupy the right.
- density: Generous gallery; compact aligned option groups.
- color: White background, black text, blue price and call to action.
- typography: Large product title; compact uppercase group labels and readable pill options.
- pattern: Make option selection visible and show why the action is unavailable before valid choices are made.
- states: Unselected size with a subdued add-to-cart control; unavailable color is visibly muted.
- dont: Do not preselect unavailable variants or present a disabled action without explaining what the shopper needs to choose.

Useful for: Use a stable product gallery next to explicit variant controls. Show unavailable choices and keep the purchase action close to the selected options.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Use a stable product gallery next to explicit variant controls. Show unavailable choices and keep the purchase action close to the selected options.

Next.js Commerce — Product details

Make it your own

Keep exploring