Plan Shopify collections around the product groups buyers need to enter, then use filters for the criteria that narrow those groups. Give each filter a clear meaning, comparable values and a confirmed data source. Review the proposed choices against the actual catalog and theme before building the navigation.
Prepare a small collection tree and a filter field dictionary. Together, they show where a buyer starts, which differences they can inspect and where missing information still prevents a reliable choice.
Which buyer choices should define the collection tree?
Start with the questions people ask while selecting a product. Use sales conversations, approved product materials and existing-site evidence when available. If the team proposes a question without customer evidence, record it as a planning assumption.
Ask which product family the buyer recognizes first and which conditions change the shortlist afterward. A question such as “Do you have desks?” suggests an entry group. “Which desk widths are available?” suggests a distinction within that group. Internal series codes can remain useful references, but a code alone may leave a new visitor unable to recognize the offer.
Our buyer-question sitemap guide assigns responsibilities across the whole website. Here, the narrower job is to organize the product-browsing part of that plan.
What should a collection do, and what should a filter do?
A collection gives the visitor a product set to browse. Shopify's collections documentation explains grouping products and linking collections through store menus. A filter refines the products shown within a collection or search result.
Use the proposed collection label to answer “What group am I looking at?” Use a proposed filter to answer “Which of these meet this condition?” In the planning example below, Desks is a collection destination, while desk shape and width are candidate filters. The distinction keeps the navigation from becoming a separate branch for every combination of attributes.
Some criteria can justify their own collection when the business has a distinct browsing purpose and enough relevant content. Record that reason. Do not create a new destination solely because the source spreadsheet contains another column.
What does a small collection tree look like?
Consider a hypothetical office-furniture supplier with desk, seating and storage ranges. These names describe an illustrative catalog, not GRC products or a customer deployment. The starting tree gives each range an identifiable destination; the Desks destination then exposes relevant refinements.
Follow the tree into Desks, then inspect the separate filter area. The branches represent proposed navigation labels and destinations, not a prescribed Shopify collection structure.
The example does not require buyers to follow one fixed route. Someone arriving directly on Desks still needs a useful page title, product context and clear refinement controls. Keep the chosen values visible so the buyer can understand which restrictions are affecting the displayed set.
How should filter fields make products comparable?
Define a field before choosing its visual control. Specify what it measures or describes, the allowed values, the source and what to do when the value is absent. Two similar labels are not enough if the underlying product information uses different meanings.
The dictionary below is a planning example. It does not create Shopify fields or prove that a particular filter control is available. Scroll sideways on a phone to read all four columns.
| Buyer-facing field | Meaning and value convention | Source to confirm | Missing-value decision |
|---|---|---|---|
| Desk shape | Agreed terms such as Straight or Corner, applied consistently. | Approved product classification and an owner for unusual designs. | Ask the owner; do not infer shape from a series code. |
| Overall width (mm) | The same overall dimension, expressed in millimetres for every comparable offer. | Current dimension drawing or approved specification, including the relevant configuration. | Keep the width unknown until confirmed; do not enter zero. |
| Top material | Approved material names with a consistent level of detail. | Verified specification for the product or option being displayed. | Do not substitute an appearance or finish name for material. |
| Finish name | The supplier's approved names, with any proposed display grouping documented. | Current finish list and the product-to-finish relationship. | Retain the gap; a similar color does not establish an identical finish. |
Keep product-level and option-specific facts aligned with the offer being shown. If a dimension changes with the selected configuration, an apparently simple product-wide value may mislead the buyer. Ask the implementation team to confirm an appropriate data source and supported control.
How do you handle units and missing information?
Preserve the original reference, then normalize values that measure the same thing. In this hypothetical data check, Desk A is recorded as 120 cm wide and Desk B as 1200 mm wide. Both convert to 1200 mm. This comparison is valid only after confirming that both values describe the same overall dimension and configuration.
Inspect the two conversion paths in the diagram. The third path stays unresolved because no width was supplied.
A width filter should not split those equivalent values merely because the source uses different units. It also should not treat an unknown width as a match for a buyer's space limit. Record which products need confirmation and how the website will communicate that gap.
The dictionary defines the comparison; it does not promise a range slider or automatic unit conversion. The actual storage type, source and filter behavior need a separate implementation check.
What must the Shopify implementation support?
Shopify's Search & Discovery filter guidance states that storefront filters require a compatible theme. Creating a filter in the app does not make it visible in a theme that lacks support. Check the selected theme and current collection controls before committing to the brief.
Ask the implementation team to trace each proposed label to its actual source and current product values, then inspect the rendered result. Renaming a filter label does not clean or change its source data. The planning tree should also be checked against the collection model available in the store's Admin.
At desktop and phone widths, review the filter's name, available values, selected state and a way to remove a restriction. Confirm that the displayed products correspond to the chosen condition. This is a proposed implementation review, not a claim that GRC's current service website has a product catalog or these controls.
What should happen when a selection has no results?
Check why the set is empty before interpreting it as a lack of suitable products. A combination may have no matching product, a required value may be missing, or the proposed data mapping may be wrong.
Shopify documents that filter values depend on the products in the current collection or result, and that empty values can be hidden or moved to the end. Review the chosen setting with actual catalog examples. A display setting cannot establish a missing product fact.
Try a known match, an incompatible combination and a product with a required field missing. Verify that selected restrictions are understandable and removable, and that clearing them returns the expected broader set. Any empty-state wording should explain the actual condition and offer a relevant next step without promising an unverified alternative.
What should you review before building the navigation?
Bring the collection tree, a small representative product sample, the filter dictionary and source references to the review. Walk from an entry group to a shortlist, then open the product detail that supports the comparison. Mark unresolved labels, inconsistent units, missing facts and unsupported controls.
Our homepage planning guide covers how the first visit routes people toward relevant detail. Use the agreed collection names consistently across those entry links and the product-browsing brief. A walkthrough can check clarity and behavior; search visibility, inquiry quality and business outcomes require separate evidence.
GRC's Shopify website services include page architecture, theme implementation and handover. Discuss your project with the tree, sample data and open questions to review the requirements and appropriate next step.
