Specifications
A table of properties per product: diameter, material, capacity, whatever your trade measures. One definition, filled per product, shown as a table and usable as a filter.
Shopify app Coming soon
The filters your shop cannot build on its own.
Shopify filters what it already knows: price, availability, variants. Everything that makes a technical product findable, the diameter, the thread, the volume, the vehicle it fits, has to become a field first. Specfinder creates those fields, gets your values into them, and turns them into filters your customers can actually use.
The app is finished and running. It is going through Shopify's review before it appears in the App Store. Want to know when it is there? Write to us.
What it builds
Compatibility
Which part fits which vehicle or device. A picker on the collection page, a yes or no on the product page, both fed from the same data.
Part numbers
OEM numbers, cross references, your own SKU. Searchable, so a customer who arrives with a number off an old part finds the new one.
Documents
Data sheets, manuals, certificates. Attached to the product, listed on the page, not buried in a description.
The order of things
Eight steps, and the app tells you where you stand.
The same list lives inside the app, except there it reads your shop instead of reciting a manual. What is missing there is really missing.
- 01
Create the fields
Specifications, compatibility, part numbers and documents need definitions in your shop. A theme is not allowed to create them, an app is. Afterwards they are yours, with or without us.
- 02
Pick your trade
A starter pack brings the labels that are common in your field. You can take several and change every row later.
- 03
Get values onto your products
Either through the import with a spreadsheet, or by hand on the product. The import shows what would happen before it writes anything.
- 04
Derive the filters
Your maintained values become filterable fields. Numbers turn into ranges, and you define no thresholds.
- 05
Prepare vehicles
If you sell parts, your vehicle data is precomputed once so the picker can show more than fifty entries. Shops without vehicles skip this.
- 06
Add the filters in Search & Discovery
A derived filter only takes effect once it is set up there. Shopify passes over a filter it does not know, without a word, and returns the full collection instead of an empty one. In Search & Discovery go to Filters, then Add filter, and pick Product metafield as the source.
- 07
Drag the blocks onto your pages
In the theme editor use Add section, then Apps. We never touch theme code, which is also why we cannot see which blocks you placed.
- 08
Translate the filter names
If your shop speaks more than one language, your filter names sit in Localization and want to be translated there, otherwise a French customer reads English filters.
Nine blocks for your storefront
App blocks, added in the theme editor. No code is written into your theme, which means removing the app removes them cleanly.
Specification table
The properties of one product, as a table.
Comparison table
Two or more products side by side, on the same rows.
Product finder
Filter down to the right article by properties.
Compatibility picker
Vehicle or device first, matching parts after.
Does it fit?
A yes or no on the product page, for the vehicle already chosen.
Part numbers
OEM numbers and cross references, listed and searchable.
Documents
Data sheets and manuals, attached to the product.
Product details
The longer descriptive fields, structured instead of one text block.
Quick view
The key values without leaving the collection page.
What it costs
Free tier, and one price above it.
Free: the specification table, the fields, deriving filters, and entering values by hand. Not a trial, and it does not expire.
29 USD per 30 days: all blocks of a trade pack, and the spreadsheet import for bulk work.
The fields and the values stay yours either way. They live in your shop as metafields, not in our database, so an app you stop paying for cannot take your catalogue with it.
What it does not do
- It does not invent your data. The app builds fields and filters; what goes into them is your catalogue knowledge, entered by hand or imported.
- It does not set up Search & Discovery for you. That is a Shopify app with its own settings, and a filter has to be added there before it appears in your shop.
- It puts no script in your storefront. The blocks are app blocks in the theme editor, and nothing is injected behind your back.
- It does not touch theme code. That is also its limit: we cannot see which blocks you placed, so the guide cannot confirm step seven for you.
- It does not translate your filter names for you. A filter name is the merchant's own text, and rewriting it in another language without being asked would be rewriting your shop.
Where it is blind
The app reads your catalogue through the Admin API, so it sees what your shop holds, not what your page renders. If your theme hides a field, the app still counts it as present. And when your products change after a run, the derived filters go stale: new products are missing from them, and a product whose composition changed may still carry the old claim. The app watches for that and writes to you, but it does not silently recalculate, because a new value changes the vocabulary and that needs a full run.
Questions people ask first
Why can Shopify not do this already?
It can filter price, availability and variant options. A property like thread size or fits this vehicle is not a variant, it is a fact about the product. Shopify has metafields for that, but nothing that creates them, fills them and turns them into filters. That gap is the app.
Does it change things in my shop?
Yes, and that is the point. It creates metafield definitions and writes values to your products, because filters cannot exist otherwise. It never writes to your theme, and every import shows you what it would do before it does it.
What happens to my fields if I uninstall?
They stay. Definitions and values are metafields in your own shop, not rows in our database. The blocks disappear with the app, the data does not.
Do I need a developer?
No. The fields are created by the app, the values go in through a spreadsheet or by hand, and the blocks are dragged in through the theme editor. The one step that trips people up is Search & Discovery, and the guide walks through it.
Does it slow my store down?
The blocks render with your page and load nothing from third parties. Nothing is injected into your theme, and there is no script that runs everywhere just in case.
My filters were right, now they are not. Why?
Because your catalogue moved after they were derived. A new product has no derived values and is missing from every filter, and a changed recipe can leave an old claim standing. The app notices, marks the derivation as stale and writes to you at most once a day. One run puts it right.
Does it work with my theme?
The blocks are standard app blocks, which every Online Store 2.0 theme supports, Dawn and Horizon included. Where a theme offers no app block slot on a template, the guide says so instead of pretending.
Your data
The app reads your catalogue and writes fields back into it. What it keeps for itself is small on purpose: which trade packs you set up, how many rows an import processed, when filters were last derived. Product data is fetched, used and dropped. Hosting, database and mail delivery run at Scaleway in Paris.