Embeddable VS ViewForge

Embeddable's answer

Software companies who care about the UX and loading speed of their customer-facing analytics.

ViewForge's answer:

Shopify merchants whose customers need to know whether a part fits before they will buy it — and who do not have an engineer on staff to build that themselves.

Concretely: auto and truck parts retailers, powersports and motorcycle dealers, tractor and agricultural parts sellers, marine and outboard suppliers, small-engine and power equipment stores, bicycle and e-bike component shops, printer supply merchants, and electronics accessory sellers.

Catalog sizes run from a few dozen products on the free tier up into the tens of thousands; it is running in production on a catalog of roughly 40,000 SKUs. The common thread is not the industry — it is that "does this fit my thing" is the question deciding the sale.

Embeddable's answer

Get the best of 'Build vs. Buy' in one stack-agnostic solution. Embeddable gives you full control over the frontend of your analytics experience, and handles the backend for you. No longer do you have to choose between a limited out-of-the-box solution, or building everything from scratch.

ViewForge's answer:

Three things. (1) Data ownership: ViewForge writes fitment as Shopify metaobjects native to your store — most competitors store fitment in their own database. (2) 8 verticals out of the box: auto, motorcycle, tractor, marine, power equipment, bicycle, printer, electronics — most competitors are automotive-only. (3) Smart Parse: extract fitment automatically from your existing product titles and descriptions instead of re-typing everything.

Embeddable's answer

Embeddable is from the team behind Trevor.io -- a popular internal BI tool which also allows you to embed dashboards into your app. We realised embedding dashboards from a BI tool into your app wasn't the 'dream solution', and building analytics from scratch was super expensive... so we built Embeddable from the ground up to enable teams to deliver fully-bespoke, highly-performant analytics in their apps for their customers in 10% of the time.

ViewForge's answer:

ViewForge came out of agency work. Normal View was building for a parts retailer running roughly 12,000 SKUs who needed fitment search, and every app we evaluated stored the merchant's compatibility data in the vendor's own database.

That is a strange trade when you look at it directly. Fitment data is genuinely expensive to produce — it is weeks of work — and the merchant would not own the result. It would belong to whichever app happened to be installed that year.

Shopify metaobjects made a different answer possible: write fitment as native structured data inside the merchant's own store. The theme reads it, the Storefront API queries it, Admin GraphQL exports it, and it is still there after an uninstall. That decision is what the rest of the app is built around.

Everything else came from real catalogs rather than a roadmap. Eight verticals exist because a tractor catalog is not Year/Make/Model. Smart Parse exists because that retailer had already written fitment into 12,000 product titles, and nobody was ever going to retype them.

Embeddable's answer

• Scalapay
• Adthena
• Irwin
• EtonX
• Resident Advisor
• Facilities Solutions Group (FSG)
• Multibrain
• Raydiant
• ThinkCERCA
• Tixly
• Softools
• Faheem App
• Just Move In
• Any Creek

Embeddable's answer

If you want full control over the UX of your customer-facing analytics experience, but don't want to invest months of developer time on building and maintaining a fully-custom build -- OR -- if you're using an embedded analytics too already that loads slowly and doesn't look and feel like the rest of your platform.

ViewForge's answer:

Data ownership. Fitment lives in your Shopify metaobjects, so uninstalling does not take your compatibility data with it. Convermax, EasySearch and PartFinder all keep it in their own databases, and getting it back depends on their export tooling on the day you cancel.

Cost at the low end. The search widget, the compatibility table on the product page and the saved-vehicle garage are all on the free tier, up to 50 products, with no expiry. EasySearch puts the table and the garage behind its $75/month Premium plan. Convermax starts at $250/month.

Automotive and non-automotive coverage. Eight built-in templates, and fully custom templates from $19/month, for catalogs that do not decompose into Year/Make/Model at all.

ViewForge's answer:

• TypeScript
• Shopify metaobjects, as the fitment data store
• Shopify theme app extensions for the storefront components: fitment search, saved-vehicle garage, compatibility table, product-page fit notice
• Shopify Storefront API, for querying fitment from the theme
• Shopify Admin GraphQL API, for writing and exporting fitment records
• NHTSA vehicle database, for VIN decoding
• ACES and PIES XML parsing, for automotive catalog import