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.13.0 June 2026

Upstream Inventory v1

SUPPLIER tenant type. Factories and warehouses upstream of the merchant run on a stripped sidebar (Dashboard, Inventory, Customers, Labels, Settings, Help). No central-catalog activation, no storefront features; the supplier publishes inventory to downstream buyers and processes their orders.
Shared-pool inventory. One inventory row per SKU in the warehouse. Updates propagate live to every subscribed buyer at the same moment, no per-buyer allocation or reservation. The supplier maintains "what's in the warehouse", not "what I have promised to whom".
Inbound batch pipeline. Track stock the supplier expects to receive: ORDERED → IN_PRODUCTION → IN_TRANSIT → RECEIVED. One-click transactional Receive moves the status and increments the SupplierPart qty in the same database transaction. Buyers see totalled incoming qty + earliest ETA on their stock view.
Buyer-placed orders. Submit qty + unit price per line in the Place-order tab. PDF order document generated server-side (pdfkit, A4) and emailed to the supplier's portal users. Status workflow PENDING → CONFIRMED → IN_PRODUCTION → FULFILLED, live across both sides as the supplier updates it.
Central catalog linking. SupplierPart can link to a central catalog Part by partId; labels then print with full rich data (brand, name, EAN, country of origin). Three link states (linked, loose, orphan) with a relink chip when the central Part is removed. Resolver canonicalises across direct match, OEM cross-references, and tenant-scoped SKU aliases.
Supplier Dashboard. Landing page on every supplier login: six stat counts (customers, subscribed parts, inventory parts, out-of-stock, overdue inbound, pending orders) plus three attention lists (overdue inbound batches, pending orders awaiting confirmation, low-stock SKUs subscribed buyers can see going to zero).
Supplier 76 × 25 mm label template. Purpose-built shipment label with EAN-13 retail barcode + canonical MPN. Joins the existing template registry, resolvable against SupplierPart data via the same partResolution pipeline as every other surface.

v0.11.0 May 2026

Analytics & Data Network, Phase 0

Self-hosted Umami at analytics.powersportos.com. Cookieless, no consent banner required, disclosed in the Privacy Policy. Tracks the public marketing site only; admin and customer portal run without analytics by design.
Admin /analytics page. Visits, visitors, pageviews, bounces, total time, and a live-now count, with period switcher (24h / 7d / 30d / 90d). An operator surface for monitoring traffic to the public site, not customer-facing reporting yet (that's a later phase).
Pageview time series for charting (hourly granularity for 24h, daily otherwise) plus top-N metrics across URL, referrer, browser, OS, device, country, and custom event.
Backend proxy at /api/admin/analytics/* behind requireAuth. Service-credentials login cached for 23h, response cache of 60s so multi-tab opens don't hammer Umami. Returns 503 with a clean error when the env vars aren't configured.
Phase 0 framing. The marketing-site track is the simplest cookieless surface to wire up first. Per-tenant analytics in the customer portal and network-aggregate views across tenants are the next phases, see the Analytics & Data Network spotlight above.

v0.10.0 May 2026

Channel Communications (multi-kind message bus)

Multi-kind message bus. Manufacturer, distributor, and data-provider tenants publish once and route to opted-in retail / reseller / hybrid / standard tenants through a per-source subscription graph that parallels brand subscriptions. Four post kinds in v1: BLOG_POST, PRODUCT_RELEASE, OPERATIONAL_ALERT, RECALL.
Author surface. Compose drawer with title, kind, summary, HTML body (server-sanitised), canonical URL, hero image, free-form categories, edit-scope policy (LOCKED / MINOR / FULL). Inline SKU markup ([[sku:NNN]]) resolves to subscriber-specific part titles at delivery time.
Subscriber surface. Sources tab to pick authors (mode, category filter, schedule offset, rate cap), Targets tab to add Shopify blog publish-targets, Inbox tab with Pending / Scheduled / Published / Failed views and drawer-based approve / edit / decline actions.
Force-delivered safety recalls. RECALL bypasses category filters, rate caps, mute states, and queue mode; persists a red banner across the subscriber portal; emails the technical / billing contact via Resend in parallel; obligates owner / admin to acknowledge within 48 hours with full forensic trail (userId + role + IP + UA).
Adapter pattern from day one. ContentPublishAdapter interface ships with a Shopify Admin GraphQL adapter (articleCreate / articleUpdate / articleDelete + canonical URL as metafield). Future adapters (WordPress, intranet CMS, generic HTTP webhook) plug in without touching the core.
Legal + compliance. Click-through Channel Author Terms and Channel Subscriber Terms (owner / admin only, IP + UA captured), DSA Article 6 hosting-service classification, voluntary transparency report at /legal/transparency, eight portal help articles. Encrypted-at-rest Shopify credentials (AES-256-GCM) for outbound writes.

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.