ParticleSearch Layout Settings: Choose an Experience, Then Fine-Tune the Surface

A shopper experiences search as one connected path. The modal establishes what the system understood. The full page creates room to compare and filter. The product card exposes the evidence needed to choose. The handoff must preserve that choice.

ParticleSearch experience presets coordinate those surfaces as a bundle. You can still adjust the modal or full page independently, but the dashboard then treats the result as a custom storefront because it no longer matches the complete preset.

A preset is useful because it prevents a dozen unrelated design decisions at the start. Once you have a real failure, move from the symptom to the responsible surface instead of changing everything at once.

If the right products are absent or badly ordered, layout is not the first repair. Inspect catalogue eligibility, query interpretation and ranking before making a denser grid display the same weak result set.

Product cards are where density becomes concrete. Vendor, descriptions, ratings, sale state, swatches and buying controls all compete for the same space, but the modal and full results page do not need identical information.

Keep a field when it helps distinguish plausible products. Remove it when it repeats the title, adds untrusted catalogue data or pushes price, availability and the next action out of view. A card setting does not repair incorrect product data; it only decides whether that data is shown.

A result can look correct and still fail after the click. When a card represents a particular option, the product page or cart must preserve that same product or variant, price and availability. If the shopper still needs to choose size, colour, pack or compatibility, the card should make that unfinished decision clear.

This is why quick add is not merely a visual preference. Test it on products with one simple purchasable choice and on products with meaningful options. If the action cannot preserve the card’s promise, keep the product-page choice in the path.

Do not evaluate a preset only on desktop. On a narrow screen, suggestions stack, filters move into a drawer and card actions compete with product information. The layout still needs to answer the same question: what result is this, why is it plausible and what happens next?

Confirm that the query stays visible, applied filters can be recognised and cleared, card labels do not depend on hover, and returning from a product does not erase the shopper’s place.

ParticleSearch groups the experience preset, modal layout, full-page layout and product-card controls in the storefront settings workflow. That gives the merchant one place to preview a real query, compare surfaces and revise the presentation without treating every change as a separate theme project.

It does not repair incomplete catalogue fields, decide which attributes matter to your buyers or prove that a layout improves commercial outcomes. The merchant still needs representative queries and a published-store check. The product’s job is to keep the controls and verification path connected.

Every visible field also creates an operating obligation: catalogue completeness, translated labels, mobile and accessibility QA, theme compatibility, and a replay after a material change. If the candidate is already correct and only one theme-owned defect remains, a focused native repair may be cheaper and easier to reverse than changing the whole search presentation.

For the underlying design judgement, use the ecommerce search layout guide. To inspect the complete buyer-facing flow, continue with ParticleSearch storefront search. Use the search filters guide when narrowing is the weak surface, and protect the release with ParticleSearch golden queries.