// new here
New to PowersportOS
Start here if you're not sure what the platform is or what's bundled in it.
docs
Documentation
Concept docs for the PowersportOS platform, what the moving parts are and how they fit together. These are deliberately conceptual: the operational how-to docs (configuring your own catalog, mapping a Shopify store, the day-to-day clicks) live inside the customer portal at app.powersportos.com once you have an account.
// core concepts
Core concepts
How the data model fits together. The pieces that make the operator portal make sense.
// for developers
For developers
Public API surfaces a Shopify theme, a stock-feed cron, or a customer integration would call.
browse
All topics
Every doc, grouped by area. Topic pages are short and link to deeper material where useful.
Overview
Core concepts
- What is YMM Year / Make / Model fitment matching and why submodel precision matters in powersport.
- Fitment data model Year ranges, wildcard submodels, per-fitment position and notes.
- Lifecycle status & replaced-by Draft / Active / Deprecated / Discontinued and the successor-SKU pointer.
- Brand subscriptions How retailers subscribe to a brand and get the catalog activated.
- Multi-Store (parent / child tenants) One brand, several Shopify stores, parent and child tenants, shared catalog, per-store pricing.
- Reseller stock network Manufacturer product pages showing nearby resellers with stock, opt-in, precision-respecting, Haversine-sorted.
- Upstream Inventory Supplier publishes warehouse stock once, every subscribed buyer sees it live. Inbound pipeline, in-app order flow with PDF + email, EAN-13 labels at dispatch.
- SKU aliases Mapping alternate identifiers (POS codes, distributor SKUs, legacy supplier numbers) onto canonical parts.
- Label printing ZPL + PDF labels generated from your catalog. Distributor-specific templates pull the right alias automatically.
- Internal YMM Lookup Year/Make/Model search inside the operator portal, same vehicle filter your customers see, available to your staff without leaving the platform.
- PIM-Light: structured product data Multi-image, dimensions + EAN, multi-OEM refs, HTML descriptions, category tree, bin location, lifecycle status. Enough PIM to feed Shopify with rich product pages.
- Data ingest CSV upload, direct API, and per-provider adapters. How brand data lands in the central catalog, how the brand-permission gate works, what gets normalised, and what stays as-is.
- Shopify product push Write PowersportOS catalog into a merchant's Shopify store, one click or bulk. Custom-App credential model, per-tenant push profile, variant-group products, stock-feed loop guard.
- Channel Communications Manufacturer / distributor / data-provider publishes once; subscribed dealers receive blog posts, product releases, operational alerts, and force-delivered safety recalls. Adapter pattern, 48h recall SLA, DSA Article 6 hosting.
- Dealer map Per-tenant Dealer records with full address, Mapbox rendering, geocoding on import, country filtering. Same data model serves manufacturer / retailer / distributor.
Platform
- The bundled stack What ships with a PowersportOS subscription, backend, storefront theme, and paid hands-on onboarding.
- Asset storage (images + manuals) Hetzner Object Storage bucket with versioning, presigned uploads, automatic CSV-import asset caching. Customer catalogs survive supplier URL rot.
- Audit log Append-only record of admin mutations: tenant lifecycle, user management, API-key rotation, brand subscriptions, Shopify install state.
- Security posture What's defending PowersportOS, transport, auth, storage, host, audit log. Prospect-friendly summary.
- CSV import format Column shape, year-range syntax, encoding, quoting, the data shape PowersportOS ingests.
For developers
- API overview Tour of the public API surfaces, public-tenant and integrations.
- Storefront API: YMM chain The /years → /makes → /models → /vehicles → /parts cascade that powers the YMM widget.
- Storefront API: product detail /parts/:partNumber + /categories, the endpoints product pages call for enrichment, plus SKU alias resolution.
- Storefront API: dealers & stock locator /dealers, /dealers/stock, /config, the store-locator widget and the find-this-part-nearby widget.
- Integrations API: stock & location-stock /stock-feed and /location-stock, server-side bulk update endpoints for POS / ERP / WMS push.