PartFinder keeps your fitment in its database. Every hour your team spends building that data is an hour invested in an asset you do not hold the keys to. ViewForge writes the same records as Shopify metaobjects, in your store, on your side of the line.
Your data. Your store. Tested at 12,000 SKUs.
Product data you can re-export from Shopify any day of the week. Fitment relationships are different: they take months to assemble, they encode knowledge your staff has and your competitors do not, and in a vendor-database app they live somewhere you cannot query. ViewForge writes them as Shopify metaobjects — native records, readable from the Storefront API, exportable through Admin GraphQL, still there after you uninstall.
A few hundred records behave. Tens of thousands do not, and the failure is usually the cascade query rather than the page. ViewForge has been load-tested past 10,000 fitment records on a single store, and runs in production on an independent tractor parts catalog of 12,000+ SKUs. The dropdown uses indexed SQL with normalized canonicalization, which is what keeps the fourth dropdown responsive when the third one has four hundred options in it.
Import from three suppliers over five years and your Make column has "Case IH", "Case-IH" and "CaseIH" in it. Every one of those is a separate storefront option showing a partial catalog, and every one of them is a shopper who concludes you do not stock their part. ViewForge normalizes case and punctuation so they collapse into one option, and fuzzy matching flags near-duplicates during import rather than after.
Most catalogs on PartFinder have fitment in two places: the app, and the product descriptions somebody wrote by hand years earlier. Smart Parse on the $49 Professional tier reads the second one, extracts structured records with confidence scores, and gives you a review queue instead of a data-entry project. It is often faster than exporting from the vendor.
The subscriptions are identical — $49 either way. What differs is who holds the fitment table at the end of the year — and whether the cascade still feels fast at 12,000 SKUs.
Install freeYes, with three differences that matter. ViewForge writes fitment to your Shopify metaobjects so you keep the data on uninstall; it ships 8 verticals beyond automotive with renameable dimensions; and the $49/month Professional tier includes Smart Parse, which extracts fitment from product titles and descriptions you already wrote. The storefront experience — cascading dropdowns, fitment badge, saved garage — is comparable.
PartFinder stores fitment in its own external database. ViewForge writes it as Shopify metaobjects, which are native records inside your store. The practical difference shows up on the way out: uninstall ViewForge and the fitment stays, queryable from the Storefront API and exportable through Admin GraphQL. With a vendor-database app, leaving usually means paying somebody to migrate data you thought you owned.
Yes. It has been load-tested past 10,000 fitment records on a single store, and an independent tractor parts retailer runs 12,000+ SKUs on it in production. The dropdown query uses indexed SQL with normalized canonicalization, so case and punctuation variants such as "Case IH" and "Case-IH" collapse into a single storefront option — which matters on catalogs that have accumulated supplier spellings over several years.
PartFinder is $49/month on a single tier. ViewForge is free to 50 products, $19/month for 1,000 products with CSV import and custom templates, $49/month for 5,000 products plus Smart Parse, and $240/month for unlimited with NHTSA VIN decode and ACES/PIES. PartFinder and ViewForge Professional are the same price, so the deciding factor is data ownership and import tooling rather than the invoice.
Export your fitment from PartFinder as CSV and map the columns in ViewForge’s importer, which is included from the $19/month Starter tier. Fuzzy matching flags near-duplicate values before they land. If the export is awkward, Smart Parse on the Professional tier can often rebuild fitment directly from your product copy instead. Once the coverage dashboard confirms the import, uninstall PartFinder — the metaobjects stay.
Fitment data is the most expensive thing in a parts catalog and the least portable. It takes months to build and it decides whether your search works. Storing it somewhere you can query, export and keep is not a preference — it is the difference between an asset and a rental. see ViewForge →