Full Text Search
Repository-backed search already covers the main product identifiers and related master data, which is the implemented search foundation.
|
Nike Air Max 270 #1
SKU: NIKE-1001
|
Published |
|
Nike Air Max 270 #2
SKU: NIKE-1002
|
Published |
|
Nike Air Max 270 #3
SKU: NIKE-1003
|
Published |
How it works in the app
Search is implemented directly in repositories and search actions. Product search covers name, SKU, GTIN, slug, and external ID, while other modules expose their own search endpoints for categories, customers, templates, and more.
The product index also supports advanced filters and filter tags. In the webshop app there is additional normalization, tracking, analytics, and popular-term handling.
Included in the current implementation
Repository-backed product search
Advanced filter DTOs
Search endpoints across modules
Webshop search tracking and analytics
Need search pages that reflect the real repository and storefront search stack?
Indexed PIM already combines identifier search, advanced filters, and webshop search analytics without overstating what is not built yet.