L1
SKU.md · stable knowledge
Catalog discovery and source-backed product facts published by the merchant.
SKU.md 1.0.0-beta
Publish one small Markdown file at /sku.md. Add source-backed product knowledge only when it helps. Live price, inventory, shipping, and checkout stay with live commerce systems.
The first useful release is the root file. Product knowledge is a separate, optional next step.
Enter a public storefront. Review the detected merchant name, summary, website, and one public catalog link.
Copy or download the Markdown, then place the exact file at the root /sku.md path on your own domain.
Check the published URL for the exact path, HTTP 200, allowed content type, UTF-8, safe redirects, and valid content.
Optional next step: add one product knowledge document for a product page when every fact can cite a visible Source.
This frozen root template contains only the merchant identity, official website, and one public catalog entry.
Read Specification# Example Outdoor Gear> Lightweight outdoor equipment for hikers. SKU.md: [1.0.0-beta](https://sku.md/spec/1.0.0-beta/)Website: [example-outdoor.com](https://www.example-outdoor.com/) ## Catalog- [All products](https://www.example-outdoor.com/collections/all)Use each layer for the information it can truthfully own.
L1
Catalog discovery and source-backed product facts published by the merchant.
L2
Current offers, price, availability, fulfillment, and market-specific product state.
L3
Capabilities for cart, checkout, payment, authorization, and order state.
Start with the smallest route that matches what you need now.
Follow a public-page publishing guide for Shopify, WooCommerce, SHOPLINE, or BigCommerce.
Add source-backed facts for one canonical product page without copying live offer state.
Use the validator, Agent Skill, MCP service, or Reference Consumer.
Generate the minimum, review every line, publish it at /sku.md, and validate the live response.