Search pattern

Review the states

The short “Searching…” feedback appears when submitting a query. The unavailable URL is an explicit review state, not a simulated live-service incident.

Entry and results

1. Entry: Every current concept has a search icon. It opens an empty field with suggested-search pills, sample matches and a full-results submission. v12.d also offers Search from its menu. Escape closes the dialog and restores focus.
2. Results: One query covers products, pages and capabilities, projects and resources. Each result shows its type, market where relevant, title, useful context and destination.
3. Narrowing: Type and market filters narrow site-wide discovery. They do not replace the catalogue’s existing internal filters.
4. Product handoff: Products show real names and article numbers. They open the existing official product detail. The new catalogue wrapper and its return path remain production work.
5. Recovery: Empty results retain the query, suggest broader terms and offer clear-filter, catalogue and expert routes. Unavailable search offers retry and catalogue access.

What the prototype actually searches

The supplied sitemap labels, two existing concept case studies, resource entry pages and three verified Beauty catalogue products: Phoenix 10 ml (535998), Pot Sigma 15 ml (531564), and Mini rollette / Deo Roller 10 ml (72496). Results run locally. Other catalogue products are not indexed here, and empty results do not mean Stoelzle has no suitable product.

No stock, suitability or compliance claims appear. Resource results link to resource pages, not invented PDF files.

Implementation contract

• Sources: published editorial content and a read-only WordPress catalogue feed or search adapter. Agree access, field mapping and update frequency with the development partner.
• Record fields: stable source ID, canonical URL, title, type, language, BU, excerpt, optional thumbnail. Products add article number and approved technical metadata. Resource files add format and language only when verified.
• Ranking: exact article number first, exact product/page title next, then relevant text matches. Use a reviewed synonym list. Test against real queries before finalising ranking.
• Language: separate EN/DE indexes, with language availability and explicit fallback. Careers also require CZ/PL/FR handling. The current search demo is English only.
• Resilience: expose partial-source failure separately from zero results. Preserve working editorial results when the catalogue source is unavailable. Loading, retry and timeout behaviour need API integration tests.
• Navigation: retain query and selected filters in the URL. The wrapped catalogue should keep new header, navigation, breadcrumb and footer, plus a visible return-to-results path.
• Access and quality: keyboard operation, focus, result announcements, contrast and responsive layouts require a full WCAG 2.2 AA review. Test real-device performance and Core Web Vitals after implementation.
• Measurement: query, result type, selected result, no-result rate and downstream enquiry/application conversion. Confirm privacy and retention rules before logging search text.

Source records

• Phoenix product source
• Pot Sigma product source
• Mini rollette product source

Pattern requirement: supplied UX/UI Design Tender, 5 October 2026, page 4. Search is a Phase 1 cross-site pattern. AI-assisted catalogue search and catalogue transformation belong to Phase 2.