Next.js Commerce — Product search

CommerceSee it livedemo.vercel.store

A product grid sits between category navigation and sorting, keeping the merchandise as the main visual focus.

Next.js Commerce — Product search — captured interface — Page excerpt · scroll inside to explore

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

Commerce Search & discovery

Why this pattern works

Keep category choices and sorting close to results while leaving most of the screen for product imagery.

Design notes

Surface: Product search and category browse
Navigation: Global navigation and search above; collections at left and sort order at right.
Layout: Three-column product grid between two narrow text rails.
Density: Open spacing around large product images; small compact category links.
Color: Near-white base with black typography and a blue price badge.
Type: Product names use short, medium-weight labels; prices are contained in small high-contrast pills.
Pattern: Separate the shopper’s category choice from sort order so each has a predictable place.
States: Populated sample catalog. Search-empty and loading states are not shown.
Don't: Do not let filters compete visually with products, and preserve selected filters on back navigation.

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 search
Source: https://demo.vercel.store/search
Swipefile reference: https://swipefile.design/ref/commerce-search/
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 search and category browse
- nav: Global navigation and search above; collections at left and sort order at right.
- layout: Three-column product grid between two narrow text rails.
- density: Open spacing around large product images; small compact category links.
- color: Near-white base with black typography and a blue price badge.
- typography: Product names use short, medium-weight labels; prices are contained in small high-contrast pills.
- pattern: Separate the shopper’s category choice from sort order so each has a predictable place.
- states: Populated sample catalog. Search-empty and loading states are not shown.
- dont: Do not let filters compete visually with products, and preserve selected filters on back navigation.

Useful for: Keep category choices and sorting close to results while leaving most of the screen for product imagery.

## 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: Keep category choices and sorting close to results while leaving most of the screen for product imagery.

Next.js Commerce — Product search

Make it your own

Keep exploring