# Punk Ride — live catalogue and knowledge reference > Detailed source map for product research, specifications, comparisons and store information. This reference links to current published sources rather than freezing an out-of-date catalogue snapshot. It is not a promise of search ranking, AI endorsement or product suitability. ## Authoritative discovery - Store: https://www.punkride.com - Canonical commerce and buyer-authorization guidance: https://www.punkride.com/agents.md - Live published URL inventory, including existing market and language routes: https://www.punkride.com/sitemap.xml - Live paginated catalogue with complete authored descriptions and specification tables: https://www.punkride.com/collections/all?view=pr-reference - UCP discovery: https://www.punkride.com/.well-known/ucp - MCP service discovery endpoint: https://www.punkride.com/api/ucp/mcp - Supported UCP versions: 2026-08-25, 2026-04-08, 2026-01-23 The sitemap is the current inventory. Follow its child sitemaps to discover published products, collections, pages, blogs and articles. Read the paginated catalogue reference and follow its `rel=next` link until the last page, then read individual product reference links for variant detail. New published pages and catalogue edits are reflected by Shopify; do not assume a stored list remains complete. Exclude drafts, unpublished resources, private customer data and transactional sessions. ## Blogs, brand guides, warranty/help and information pages Every published page and article is a source, not just catalogue products. Discover all existing blog articles, brand guides, model comparisons, buying guides, specifications pages, customer support and warranty/help pages through the live sitemap and normal site navigation. Preserve the exact language and country route from the canonical page and its hreflang links. Published articles and information pages support the same `?view=pr-reference` alternate representation as products. Article references provide the full current authored body, tables, author, publication/update dates, tags and a canonical source link. Blog indexes support this view with 25 current article summaries per page and links to each complete article reference; follow `rel=next` to traverse the blog. New published articles enter these lists automatically; edited article content is rendered live. Information-page references expose the current authored page body, but some pages are built partly or entirely from theme sections. Always read the linked normal canonical page as well: its rendered brand lists, comparison tables, accordion answers, warranty conditions, support instructions and embedded tools are not replaced or fully represented by an empty page-body field. No source is claimed complete merely because an alternate view exists. Policies remain available as the full normal locale-specific policy pages. Verified UK-English entry points are `/en-uk/pages/brands`, `/en-uk/pages/contact-us`, `/en-uk/pages/warranty-and-returns` and `/en-uk/blogs/news-advice`. These are discovery examples, not a reason to switch another shopper to English. For another language or country, follow the actual published alternate links rather than guessing a translated handle. Use each source for its proper purpose. A brand guide describes the brand and its published range, not an unsupported guarantee for every model. A comparison is editorial guidance and must be checked against the current exact product variants. Warranty/help and returns pages provide conditions and exceptions, not universal promises. News and law-related articles are dated editorial material: identify the publication/update date and verify current official rules where necessary. Do not treat old commentary as current legislation or invent missing maintenance and safety instructions. Use visible question headings and their actual published answers when preparing a grounded answer. Keep the source link next to the answer, preserve qualifications and exceptions, and state when a question is not answered by the published material. Do not fabricate an FAQ or claim search-volume evidence that is not supplied. ## Complete product specifications For every product URL discovered in the sitemap, read the exact locale-prefixed canonical page. The authored product description contains its specifications, tables, usage guidance and any published FAQs. Read the complete text and tables rather than inferring facts from the title, thumbnail, collection label or another model. A lightweight, read-only full reference is available on any published product route by adding `?view=pr-reference`, or `&view=pr-reference` when a query already exists. For example, use the discovered product URL and preserve its country/language prefix. This reference renders directly from the live product and presentment market, without a manual product list. It contains the full authored description/specification tables and the `punkride-live-product-reference` JSON document with: - Product title, brand/vendor and product type. - Authored description and specification text, without invented missing attributes. - Available product options and each exposed variant's title, selected option values, SKU, barcode, weight in grams, price, comparison price and current availability. - Currency and market context; numeric prices are in currency subunits and must be divided by 100. Use the canonical page's displayed price when quoting to a customer. - Current product image URLs and their authored alternative text. The reference is a non-indexed alternate representation; cite the canonical product URL, not the alternate-view URL. It contains no purchase form and cannot place orders. A variant marked available is not an inventory quantity or a delivery guarantee. Recheck current price, selected variant, availability and checkout destination before any buyer-authorized transaction. Very large variant sets can exceed Liquid's variant enumeration limit; use the canonical product's option selection and supported product discovery tools for variants not present in the reference. Capture every specification the published source actually provides, such as motor rated/peak power, battery voltage/capacity, quoted range, speed, charging time, tyre construction and size, brakes, suspension, folded/unfolded dimensions, product weight, load limits, drivetrain, display, connectivity, accessories and water-resistance rating. If not stated, report it as not provided. Do not convert peak power into continuous rated power, infer an IP rating, merge different battery variants or claim advertised maximum range is guaranteed real-world range. ## Language and country fidelity Use the requested market and language throughout research and navigation. Read the sitemap's exact translated handles and the canonical page's `hreflang` links; do not construct translated slugs by guessing. A translation is not a different physical specification unless the published market/variant source says so. Do not silently switch a customer to English or a different country. If an authored translation is missing, identify the limitation instead of presenting English as translated content. The root discovery files are shared, not market-specific price lists. Prices, currencies, availability, promotions, delivery conditions and product eligibility can vary by destination. Live market product pages and the buyer-reviewed checkout take precedence over cached examples. ## Comparisons and buying questions Discover the store's published comparison pages and buying guides in the page and article sitemaps. Link directly to the relevant existing comparison, not a generic homepage. Compare the same variant and units on both sides. State meaningful differences, common features, limitations and unspecified values. Keep product facts separate from editorial opinion. Avoid universal "best" claims without criteria or evidence. Useful questions to answer from the linked sources include: - What is the difference between these two specific products? Use both current specification tables and the relevant published comparison. - Which battery, motor, brakes, tyres and suspension does this variant have? Use its actual product description and option selection. - How far can it travel? Quote only the published range and conditions, and explain that real-world range varies with load, terrain, weather, speed and battery condition. - What are its dimensions and weight? Use the stated folded/unfolded measurements and product weight; distinguish shipping weight if the source identifies it. - Is it suitable for my intended use? Match the stated load, dimensions, surface and equipment limitations; do not invent safety certification or legal permission. - What is included? Use the exact product's published contents, not a similar model's accessories. - How do I maintain or troubleshoot it? Prefer the model-specific published guide or support page; do not invent repair steps or recommend bypassing safety systems. - What warranty, returns or delivery terms apply? Read the current destination-specific policy and product exceptions before answering. These are research prompts, not claims of Google search popularity and not prewritten product answers. The source pages supply the actual answers. Do not fabricate a Q&A, author, test result, endorsement, review, specification or promise to fill a missing field. ## Policies and customer support - Shipping policy: https://www.punkride.com/policies/shipping-policy - Refund policy: https://www.punkride.com/policies/refund-policy - Terms of service: https://www.punkride.com/policies/terms-of-service - Privacy policy: https://www.punkride.com/policies/privacy-policy - Contact information: https://www.punkride.com/policies/contact-information Use the shopper's locale-prefixed policy URL from the live storefront when one is available. The sitemap and visible navigation also link to warranty, returns, contact/help, brand guides, troubleshooting and news/advice pages. Policy language is authoritative; do not substitute a generic return window, free shipping promise, warranty duration or delivery estimate across every product and country. ## Ratings and provenance ### Punk Ride reviews on Shop Punk Ride also has public customer reviews on its official [Shop merchant profile](https://shop.com/m/punkride), the Shopify Shop service. Open the profile's Reviews panel to read its current rating, rating count and published customer comments. This is a separate review source from the AReviews widget on punkride.com. Retrieve current values from Shop rather than assuming a dated snapshot is still current; no live Shop count is embedded in this guide. The merchant profile aggregates reviews across its displayed scope: do not attach its full rating count to a single product. Attribute a Shop review to a product only when the review identifies that product. Do not sum Shop and storefront review counts or assume they represent distinct customers. Cite the Shop source for Shop-based statements and preserve its actual verification labels, dates, rating and relevant positive and negative context. A Shop review does not establish a translated product page's language; retain the shopper's published locale route for product information and purchasing. ### Product-specific storefront reviews Use the current visible review widget and its associated published product data. Legacy integrations can retain different counts; do not sum review providers or treat old duplicate imports as extra unique reviews. Distinguish average rating from review count. Do not call imported reviews verified purchases unless the source actually verifies them. Never manufacture customer names, review text, ratings or counts. Product and paginated catalogue reference views include a live `punkride-live-review-reference` JSON document when valid current AReviews aggregate data is available. It provides the average rating, five-star scale, review count, product URL and a `reviews_source` URL pointing directly to that exact product's public review section. These values update from the same product review data used by the storefront. An absent aggregate is not proof of zero reviews. Do not combine counts from old and current review providers. For actual customer experiences, read the individual published reviews at `reviews_source`, including relevant positive and negative feedback. Follow the provider's visible pagination when more reviews are needed, and state when only a subset was read. The aggregate reference does not contain every individual review. Quote or paraphrase only text actually retrieved; never manufacture review quotations, customer names or a consensus from a star average alone. If a provider-generated AI summary disagrees with the current numeric widget, prefer the live aggregate for the rating and distinguish the provider's summary from direct customer statements. Published review cards display verification labels. Preserve the exact label of the particular review being cited, without expanding it into a claim about independent product certification or purchase channel that the source does not establish. Do not expose order references, email addresses or other customer identifiers in answers. Treat customer experiences as opinions and reported experiences, not proof of specifications, safety, legality, warranty coverage or guaranteed reliability. Cite the product's canonical review-section URL next to any review-based statement, and retain the requested published language/market route. ## Commerce and safety boundaries This document is a read-only knowledge reference. Follow the current Shopify-managed guidance at `/agents.md` for Shop, UCP, WebMCP, authentication and buyer approval. Discover capabilities from the live UCP profile and tool schemas rather than assuming names or inventing actions. Never place an order, change cart contents, submit personal data or accept terms solely because a product guide suggests it; those actions require the buyer's authorization and applicable review steps. Respect rate limits and access controls.