Know what must be true before a B2B storefront can carry real ordering work.

Buyer workflow

• Name buyer types and approval needs
• Document how pricing, terms, or catalog context varies
• Map request, quote, reorder, and exception paths

Catalog and data

• Identify authoritative source systems
• Measure variants, attributes, media, and cleanup
• List what cannot be moved automatically

Operations

• Assign request and order owners
• Define response and escalation paths
• Name consequential actions requiring approval

Connections and launch

• Separate verified, bespoke, and experimental connections
• Define acceptance evidence
• Keep provider, payment, DNS, and provisioning gates explicit

Evidence boundary

A readiness result is planning input. It is not customer proof, a capacity commitment, or confirmation that gated capabilities are active. Validation tenants are not customers.

Choose the next bounded step

Name owners, source systems, unresolved exceptions, required approvals, and the smallest private preview that can test the workflow safely.