The shared catalog, fitment, stock, and intent layer underneath European powersport retail. One source for the whole chain to read from and write to.
What we are
PowersportOS sits underneath the storefronts. We do not broker transactions. We do not run inventory. We are the shared catalog, fitment, stock, and intent graph that every European powersport storefront can plug into and read from. Brands publish once. Dealers consume automatically. Manufacturers finally see the network they are blind to today.
The data asymmetry
Dropship arrangements expose every transaction to the manufacturer automatically. Stock-holding arrangements expose nothing. We close that gap without forcing retailers to give up the margin or autonomy of holding stock.
How it works
Brands and distributors push their catalog into PowersportOS in whatever shape it lands. We normalize it. Subscribed dealers receive the cleaned data the moment it's available, on their Shopify storefront, on their YMM widget, in their portal, through our APIs. No re-typing between steps in the chain.
Brands & distributors
CSV, JSON, XML, custom feeds. We accept the shape you can produce.
the shared layer
PowersportOS
Dealers & their channels
YMM widgets, dealer maps, product pages, stock APIs, integrations.
The problem
Brand exports to spreadsheet. Distributor edits the spreadsheet. Dealer imports the spreadsheet. Fitments break, descriptions drift, OEM cross-references get lost, the next revision starts the cycle over. PowersportOS removes the spreadsheet.
today
with PowersportOS
Who it's for
PowersportOS works differently depending on whether you publish data, distribute it, or sell against it. Three pages, three pitches, one platform underneath all of them.
Stock-holding distribution is a black box today. PowersportOS lights it up. Sell-through velocity per SKU per region. Inventory aging across the network. Search-to-sale ratio. The four data points an S&OP team would build a dashboard around, if the data existed.
The HQ view of a fully-owned retail chain. Distributed across independent resellers who keep their autonomy. Save your network four days per brand onboarding and add a real-time channel for product releases, MSRP changes, and safety recalls.
Subscribe to brands, get pristine catalog data flowing to your Shopify storefront. Submodel-precise YMM, dealer locator, stock integrations, label printing, internal lookup. Stop typing fitment data at midnight.
Running a multi-location chain or a brand-managed catalog as a data provider? Retail chains and data providers have their own paths.
Everything powered by the same data
Each module below exists because the data model already knows the answer. YMM works because we already store submodel-precise fitments. Dealer maps work because we already model dealer entities. Reseller stock works because the catalog is multi-tenant. The modules are consequences of the data layer, not features bolted on.
Fitments are stored at the (year, make, model, submodel) granularity from the moment they land. The widget on a dealer's storefront is reading the same fitment row a distributor uploaded.
Per-tenant dealer entities with full addresses, geocoded on import, country-filtered on the storefront. Same model serves single-store retailers and pan-European chains.
Manufacturer product pages query "find this part nearby" against the same catalog dealers subscribe to. Opt-in, precision-aware, Haversine-sorted.
One-click write of catalog rows into a dealer's Shopify products. Variant groups become multi-variant products. Per-tenant push profile decides what overwrites versus what stays.
Brands publish blog posts, product releases, sales-stops, safety recalls once. Routes through the brand-subscription graph to every subscribed dealer's storefront via the same Shopify Admin adapter as product push.
Per-store stock for retail chains via a single API endpoint. Customer-facing widget shows nearest-store availability. Same data model that powers single-store stock for solo dealers.
Public, stable, X-API-Key-authed endpoints for the data the storefront and the merchant's own systems need. Same data, different consumers.
YMM, dealer map, stock locator pre-built as sections, wired to the public API with a tenant key. Onboarding installs and configures it.
The hard parts
Building shared data infrastructure in an industry that has historically traded data in spreadsheets is hard. Here are the four objections we get most, and how we think about each.
network effects
"These platforms only become valuable when many people use them. Until you have critical mass, the value proposition is thin."
A multiplier, not the bet.
Customer one gets the best YMM widget, dealer map, and PIM in powersports the day they sign. The reseller stock graph and shared catalog growth land on top of that, not under it. The platform is valuable to a single isolated dealer; the network is the accelerator, not the survival mechanism.
data quality
"Everyone in this industry says they have clean fitment data. Reality is always messier than the pitch deck."
It's the problem we exist to solve.
The shared catalog isn't a storage layer, it's a cleaning layer. Year-range expansion, OEM ref validation, ISO country-of-origin mapping, image mirroring to durable storage, sanitized HTML descriptions, lifecycle status with replaced-by pointers. Quality is the product, not a side-effect. More on data quality
vendor discipline
"Tech is rarely the hard part. Getting fifty suppliers to actually update their data correctly is the hard part."
Doing the cleaning is the work.
Realistic input is CSV, JSON, occasionally an Excel file a sales engineer made in 2018, sometimes XML feeds that drift every quarter. We treat that as the brief, not the bug. CSV importers expand year ranges; per-provider adapters land per relationship; brand-permission gating keeps reads scoped. Once the network has gravity we can raise the bar on what we accept. Until then, doing the cleaning is the work. Ingest architecture
adoption
"Powersport retail isn't exactly known for being fastest on digital transformation."
A slow vertical is why the bundle exists.
Correct, and we know it. PowersportOS ships as a bundled package (backend, theme, paid hands-on onboarding) rather than as a DIY integration kit. Customers run their existing Shopify storefront; we plug into the end they already understand. The distributor track turns one signed partner into hundreds of referrals we'd otherwise need to find one at a time.
Data ownership
The central catalog is maintained by Umbr AB under EU jurisdiction. Tenant data is yours: full export, full deletion, no claim by the platform. Whoever creates the data owns it.
One central source of truth for catalog, fitment, and vehicle data. Tenant-specific data (your prices, stock, proprietary SKUs, custom vehicles) stays in your space. The two layers are clearly separated, never duplicated, and you own your half outright.
Hosted in EU data centres, processed under GDPR, accessible via export anytime.
// Central catalog · maintained by PowersportOS, shared Part { partNumber: "55716014" brand: "Alphatrac" name: "Air Filter Sportsman 850" fitments: [Vehicle, Vehicle, ...] } // Your tenant space · your data, your half CatalogItem { part: Part // reference, not copy price: 420 stock: 18 }
We work closely with a small group of dealers, brands, and distributors before opening the platform more broadly. If your business fits one of the audience pages, get in touch.
