What's coming. What just shipped.

PowersportOS ships every few weeks. This page is the public view: features we're actively building toward (in roughly prioritised order, no committed delivery dates), plus a snapshot of what landed in recent releases. If something on the Coming list would tip a decision for you, register interest at the bottom. We read every submission and use it to inform priority.

Coming up

Features we're building toward.

Listed in current priority order. Subject to change as customer conversations refine the picture. If a feature on this list is the difference between "interesting" and "yes I'd switch", let us know via the form below. Concrete prospect interest moves things up the queue.

data-network

Analytics & Data Network

Coming

PowersportOS sits at the chokepoint where catalog content, fitment data, stock levels, and end-customer search intent converge across the European powersport reseller network. Every tenant running the bundled stack passively contributes to a dataset that nobody else in the industry is structurally positioned to assemble, while getting tools they actively want for their own day-to-day operations in return. In effect, the same intelligence and coordination that a fully-owned retail chain has internally, distributed across independent operators who keep their autonomy. As more tenants join, the platform automatically becomes more valuable for everyone already on it.

Why this position is structurally rare

Distributors see B2B sell-through to resellers, not what end customers actually search for. Manufacturers see sell-through to distributors, two or three steps removed from the buyer. Shopify Analytics is per-store, cookie-gated in the EU, and policy-bound against cross-merchant aggregation. ACES, PIES, and TecDoc distribute catalog content; they don't capture consumption. The only position that can see last-mile demand signal across many competing resellers is a shared vertical platform that those resellers voluntarily plug into. PowersportOS is that position.

What each part of the chain gets

Manufacturers: the data points an S&OP team would build a dashboard around if the data existed. Sell-through velocity per SKU per region (how fast does a part move from dealer shelf to customer). Inventory aging across the network (which SKUs are sitting still, before return requests reveal the overstock). Search-to-sale ratio per SKU (hot demand vs idle curiosity). Regional demand patterns (what is moving in the Nordics vs Southern Europe, ahead of distributor-channel feedback). All across the independent-reseller network, not just dropship arrangements where the data flows for free.
Distributors: aggregate stock per region across their reseller network, brand-coverage grid, search-trend signal, sell-through-rate visibility. The strategic intelligence layer the larger ones have been trying to build internally for years.
Retailers: cookieless analytics on their own storefront, zero consent banner, plus visibility into which parts are trending across the network so they can stock the right inventory. Crucially, this also closes the data-visibility gap between dropship and stock-holding operating models, letting stock-holding resellers compete with dropship on operational signal without giving up the margin or control that comes with holding inventory.
End customers (indirectly): better content because brands have a reason to keep it pristine, smarter cross-sell, fitment data that stays current.

You stay in control of your contribution

Every tenant decides what they share. Default is private; aggregate views require explicit opt-in per tenant. Aggregates use k-anonymity techniques so individual tenant data cannot be reverse-engineered from the total, and no per-tenant attribution ever appears in cross-tenant views: reseller A can never infer reseller B's stock or sales from any aggregate they have access to. We aggregate business data (catalog membership, search interest, stock totals), never end-customer-attributable activity. Documented in full in our Privacy Policy and DPA.

Honest about where we are

With a handful of tenants, network aggregates aren't valuable yet. The dataset compounds with each opted-in tenant, and the value to manufacturers and distributors scales with that. We are not claiming the dataset is dense today. We are claiming the position is the right one to build it from, and the layer that scales in value with each new participant is one no other vendor in the chain is structurally positioned to replicate. The early tenants who opt in are the ones who shape what the network looks like when it matures.

Status

Phase 0 shipped May 2026: self-hosted cookieless Umami analytics for the public marketing site, surfaced inside the PowersportOS admin. Per-tenant analytics in the customer portal is the next phase. Network aggregates roll out after that, in order of feasibility from existing data: catalog-coverage stats and YMM search trends first, view-popularity and stock aggregates next. Sales-velocity data unlocks earlier than expected because the Shopify connector already shipped for outbound product push (May 2026) can pull order events via the same customer-managed credential with one additional read scope, so the last-mile signal does not require building a separate ingestion pipeline.

Coming

b2b

B2B pricing tiers

Customer-group pricing (Shopify customer tags wired through to per-group pricing), per-customer custom price lists, net vs gross display toggle based on signed-in customer state, tax-exempt flags per customer or order, bulk-discount tiers (quantity breaks), login-gated catalog visibility for B2B-only SKUs, saved carts and re-order from order history.

Why it matters: 30-60% of a typical powersport retailer's revenue is B2B to repair shops, dealers, and fleets. Today retailers reach for Shopify Plus (€2000+/mo) or stitch together apps like Sufio B2B / Wholesale Club / Bold. We can bundle the core B2B story into the platform itself.

Coming

garage

Customer garages

End customers save their own vehicles (year, make, model, submodel) to a personal garage. On return visits, the storefront only surfaces parts that fit their saved vehicles, with no need to re-pick YMM every session. Multi-vehicle profiles, share-with-mechanic links, optional email notifications when new parts land for saved vehicles.

Why it matters: dramatic stickiness for retail customers (a one-time setup yields years of personalised browsing). Repeat-purchase patterns improve for everyone in the chain: retailer, manufacturer, distributor. Differentiator vs. flat catalog stores.

Recently shipped

What landed in the last few releases.

PowersportOS uses semantic versioning. Patch releases land continuously; minor releases bundle a coherent batch of new features. Here's the last three; for the full minor-release feature notes back to v0.2.0, see the release notes.

v0.17.0 July 2026

Product data expansion

Three dimension levels on every part. Bare product (the article itself), retail package (what Shopify shipping reads), master box (case pack from the supplier). Existing weight / length / width / height columns keep their historical role as package-level; the two new sets sit alongside without disrupting anything already published.
Master-box quantity + weight-calc helper. Case-pack qty is a first-class field on every part. A small "calc" button next to master-box weight pre-fills packageWeight × qty × 1.05 when the supplier does not publish an authoritative number; operators can accept or override. Manual entry stays primary because tare weight, dunnage, dividers, tape typically add 3-15% that unit-weight math cannot know about.
Dimensions tab in the Part editor. Three-column layout groups the three dimension levels side-by-side, so operators can see and edit all levels in one glance. Rolled out to admin, portal My Parts, and managed Parts surfaces from the same shared editor component.
CSV importer + exporter carry the new columns. Round-trip compatible: export a CSV, edit the new columns in Excel, re-upload, everything lands. Column-mapping wizard's fuzzy-match automatically picks up the new target headers so ERP exports with slightly-different names still line up.
Public API stripping. Bare-product and master-box values are stripped from public storefront responses. Competitive info (case-pack quantity, wholesale packaging math) stays internal.

v0.16.x July 2026

Import-UX sprint

Column-mapping wizard on every CSV import surface. Central catalog (admin), managed parts (data provider), My Parts (retailer), Dealers (retailer). Source CSVs never need to match our template's column names anymore. Fuzzy-match auto-suggests a target column per source column, samples of real values show under each source header, "Ignore this column" as a first-class option, and required-field enforcement blocks commit until every required target has a source mapped.
Save mapping as a named preset. Per-user, per-tenant, per-importer library. Map your ERP's export once, name it, next month's re-import loads the preset in one click and goes straight to the Review step. Presets don't cross users (a preset captures "how MY source formats its CSVs") but can be extended to team-share later without a breaking migration.
2-digit-year expansion toggle. Off by default with a hard warning surface. When on, source values like 02 and 02-06 in the years column are rewritten to 2002 and 2002-2006. Fixed window rule (00-89 becomes 2000-2089, 90-99 becomes 1990-1999) so the same 2-digit value always resolves to the same 4-digit year regardless of when the import runs.
Dry-run preview before commit. Every import now runs through a preview step showing per-action counts (will create / will update / skipped / skipped-out-of-scope) plus the first 20 categorised rows so the operator can eyeball the intent before anything writes. Batch-only: no per-row curation, fix problems in the source CSV.
Low-resolution image warning. Product thumbnails on admin and portal Parts lists overlay a warning badge when the primary image's longest side is below 600px. Catches the "someone uploaded a thumbnail by mistake" case without blocking anyone from doing it deliberately.
R&G Racing delta + weekly full-sweep. Delta sync (typically under 10 minutes per run) fetches only changed products via updatedAfter cursor. Weekly full-sweep does deletion detection: parts not seen this pass get soft-deprecated (DEPRECATED status), retailer catalog rows preserved. Both scheduled via Coolify Scheduled Tasks, monitored via Better Stack heartbeats.

v0.15.0 July 2026

Data-provider adapter release

First per-provider ingest adapter live. Around 6,600 products, 977,000 fitments, and 22 brands landed in the central catalog through an automated pull from a UK aftermarket brand's dealer API. Downstream retailers see this data through the same normalised shape as any CSV-uploaded row. Additional adapters roll out per relationship as data-provider partnerships come online.
Data ingest admin surface. Adapter cards with Requests / Vehicles / Categories / Brands / Products counters, expandable per-run error diagnostics, and a Run-now dialog that reads supported run types from each adapter. Every run is captured in an audit table (SyncRun) with per-entity counters and full error JSON for after-the-fact analysis.
Four consistent run types. bootstrap (taxonomy setup, 1-3 min), product-bootstrap (full catalog import, several hours because upstream rate limits and asset rehosting dominate), brand-sync (brand-metadata refresh only, under a minute), retry-failed-categories (targeted retry that reads the last failed run's errors and re-attempts only the affected endpoints).
externalRefs pattern. JSONB column with GIN index on Part and Vehicle for adapter-agnostic external-ID storage. Each adapter writes its own keys under the same column: a future adapter drops in without a schema migration.
Column-mapping wizard, first cut. Managed-parts CSV importer got a two-step wizard (Map → Review) with source-column samples and fuzzy-match auto-suggest, so onboarding data providers no longer had to rename headers in Excel first. v0.16 rolled this out to every other CSV importer and added the preset library.
Admin UX standardisation. Every list page across admin and customer portal now uses a shared PageHeader and left-aligned PageToolbar pattern with a dropdown that collapses Import / Export / Template into one button. Search boxes rendered as proper outlined inputs across every DataGrid instead of the near-invisible underline default.

Want any of these? Tell us.

Concrete prospect interest moves things up the queue. Check the features that would matter to you, add context if useful. We'll get back to discuss timing, scope, and what would unblock you specifically. Quick form, real reply.

Or email info@powersportos.com directly if a form is not your thing.