Updating

Before updating

1. Confirm the installed version in the documentation header or package.json.
2. Review the update instructions supplied with the download and note any backend, rule or configuration changes.
3. Export or back up Firestore.
4. Retain Firebase Storage files and a copy of the current deployed dist.
5. Store .env.development, .env.production, functions/.env, .firebaserc and provider secrets securely.
6. Record deliberate source and branding customisations.
7. Pause Taking orders if the update could interrupt checkout.

Apply the update

1. Extract the new release into a separate folder.
2. Compare the new .example files, Firebase rules and indexes with the installed release.
3. Create new private environment files and copy only the required private values into them.
4. Reapply deliberate customisations through a source comparison.
5. Run npm ci and npm --prefix functions ci.
6. Run npm test, npm run typecheck and npm run build.
7. Deploy with the same host and optional-provider choices used by the live installation.
8. Clear the host cache only when the host has not published the new hashed assets.

Do not overwrite private environment files, provider secrets, Firebase Storage, production data or business-created content. Keep the previous source and build until verification is complete.

Verify and reopen ordering

1. Open the storefront and /admin in a private browser window.
2. Confirm administrator login, business settings, products and images.
3. Place a complete collection or delivery test order.
4. Move the order through every valid status.
5. Test each enabled payment and messaging provider.
6. Re-enable Taking orders after all checks pass.

Roll back

If the frontend fails, republish the previous dist. Follow any update-specific rollback instructions supplied with the download; do not reverse a schema change by guessing. Restore data only from a verified backup and retain evidence of the failed step for support.