Get the catalog, buyer rules, and staff decisions ready before you build.

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 important actions that require approval

Connections and launch

• Separate verified, bespoke, and experimental connections
• Define the checks that must pass
• Keep payment setup, domain changes, and store launch decisions explicit

What a readiness result means

A readiness result is planning input. It is not customer proof, a capacity promise, or confirmation that every requested feature is active. Test stores are not customers.

Choose the smallest useful next step

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