SKU.md 1.0.0-beta

WooCommerce · 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

A static host, a small WordPress route, or a same-origin edge route can serve pre-generated files. Root-path control alone is not proof: verify HTTP 200, Markdown MIME, UTF-8, exact bytes, safe redirects, and exact 404 behavior.

Root-first workflow

1Generate and review the minimal /sku.md file.
2Publish exact bytes through a route you control.
3Run document, published, and graph validation.
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.

The brand perspective

Explore what SKU.md adds to your platform and where a small product-knowledge pilot can begin.

WooCommerce SKU.md integration

Platform evidence

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