Skip to content
SKU.md
Menu
English

SKU.md 1.0.0-beta

SHOPLINE · Delivery boundary · SKU.md 1.0.0-beta

Publish the minimal root catalog first. Add one optional product knowledge document only when every item cites a visible Source.

Open generator

Delivery boundary

File Library hosting plus a redirect can expose a file, but does not by itself prove an exact /sku.md Markdown response. Use a merchant-controlled headless or edge route for a strict candidate, then verify the live contract.

Root-first workflow

  1. 1Generate and review the minimal /sku.md file.
  2. 2Publish exact bytes through a route you control.
  3. 3Run document, published, and graph validation.
  4. 4Optionally add one same-origin product knowledge document with Source links.

ConformanceScope: document → published → graph

Root catalog

# 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)

Optional product knowledge

# UltraLight 2P Tent
> A lightweight two-person tent for three-season backpacking.

SKU.md: [1.0.0-beta](https://sku.md/spec/1.0.0-beta/)
Catalog: [Example Outdoor Gear](https://www.example-outdoor.com/sku.md)
Product: [Official product page](https://www.example-outdoor.com/products/tent)
Updated: 2026-08-11

## Facts
- Packaged weight is 1.35 kg. [Source](https://www.example-outdoor.com/products/tent)

What this guide does not claim

  • No platform login, credentials, private API, bulk crawl, or automatic publishing.
  • No native platform support or adoption claim.
  • Live price, stock, shipping, tax, cart, checkout, and orders remain with live systems.

Platform evidence

These sources describe platform capabilities. They do not document native SKU.md support.