Partners
Agree the implementation handoff
Confirm the following with your implementation contact before launch. Record the customer-specific agreement rather than assuming every installation has the same scope.
- Hosting and billing: backend resources belong to and are billed to the customer. Azure is preferred, but another compatible VM provider can be agreed. The storefront runs on Vercel, preferably in the customer's own team; see hosting and access.
- Domains: the operator supplies backend and administration domains and manages their protection. This does not require moving the customer's domain to Cloudflare. Agree the storefront domain and its DNS changes separately.
- Shop email: select a sender name, address and DNS contact; follow the email domain guide.
- Business setup: identify who approves catalog content, customer access, prices, shipping, payment options and legal content for the launch.
- Acceptance: agree who tests the customer journeys, resolves findings and authorizes launch. Record any limits or intentionally deferred functionality.
- Operations: agree support contacts, access management, backups, recovery, maintenance and release responsibilities. Service levels depend on the agreement.
Before handoff, make sure the responsible people have their required access and know how to report an issue. Share credentials only through the agreed secure channel.