The website shows a blank page
Likely cause: A production environment value is missing, the build is stale or a JavaScript asset was not published.
Resolution: Run both configuration validators, rebuild, redeploy and confirm the browser can open the generated asset URLs. Use a private window to avoid stale cached files.
Contact support when: The production build passes, all assets return HTTP 200 and the page still fails with a reproducible console error.
A command is not recognized
Likely cause: Node.js is not installed, the terminal was open during installation or the command is running outside source.
Resolution: Reopen the terminal, open source, then run node --version and npm --version. Node.js must be 22.12 or newer.
Dependency installation fails
Likely cause: The network, npm registry access, local cache or unsupported Node version interrupted installation.
Resolution: Confirm the Node version and internet connection, then run the documented npm ci command again. Do not delete the supplied lockfiles or apply forced dependency upgrades.
Configuration validation fails
Likely cause: The named environment file is missing, has a .txt extension or contains an empty required value.
Resolution: Compare it with the supplied .example file. Firebase Web App values are under Project settings > General > Your apps > SDK setup and configuration.
Firebase reports permission denied
Likely cause: The CLI is using the wrong project, rules were not deployed or the account does not have the required role.
Resolution: Run npm exec --yes firebase-tools@15.24.0 -- use, confirm .firebaserc, redeploy rules and sign out and back in after a role change.
Images do not upload
Likely cause: Storage is not enabled, Storage rules are stale, the account is not an administrator or the source image cannot be processed.
Resolution: Confirm Storage is enabled and rules are deployed. Sign in as the administrator and use a current JPEG, PNG or WebP image under the documented upload limit.
Orders do not appear in administration
Likely cause: The storefront and administration are using different Firebase projects or business IDs, or the order is an incomplete online checkout.
Resolution: Confirm both use the same Firebase values and VITE_INSTALLATION_BUSINESS_ID=default. Complete a manual order and refresh Orders.
Payment return or webhook is not received
Likely cause: The webhook URL, signing secret, provider Function or production website URL does not match the deployed environment.
Resolution: Compare the provider dashboard endpoint with Payments, confirm the required secret and redeploy that provider. Repeat the sandbox checklist before using live keys.
An optional provider secret is requested during deployment
Likely cause: The deployment command includes a provider such as --providers=whatsapp.
Resolution: Enter the requested credential only when you intend to deploy that provider. Payment gateways are included in the normal deployment. Use --providers=whatsapp only when WhatsApp is configured.
WhatsApp does not send
Likely cause: The event is disabled, credentials are absent, the sender is not approved or a WhatsApp template is unavailable.
Resolution: Check Settings, the business alert number, provider secrets and deployed provider list. Confirm provider approval and test with a valid international number. Ordering continues when messaging is unavailable.
First setup reports an internal error
Likely cause: The setup Functions were deployed in a different region from the website configuration, or an earlier setup attempt left incomplete business data.
Resolution: Confirm that FUNCTIONS_REGION in functions/.env matches VITE_FIREBASE_FUNCTIONS_REGION in both website environment files, then run npm run deploy again. Ordio uses europe-west1 by default and can safely resume an interrupted first setup.
The website opens /sign-in or /admin returns to sign in
Likely cause: Business setup has not been completed, or the first administrator account was created before setup was interrupted.
Resolution: Open /sign-in. If the first administrator is already signed in, Ordio resumes business setup with that account. Otherwise, create the first administrator and complete the setup form. After setup succeeds, Ordio opens /admin.
The storefront shows closed
Likely cause: Taking orders is off, the current time is outside weekly hours or the configured timezone is incorrect.
Resolution: Check all three values in Settings, select Save changes and refresh the storefront.
Refreshing /admin shows page not found
Likely cause: The host is not rewriting application routes to /index.html.
Resolution: Use the supplied host configuration or add the SPA rewrite described in Choose a host, then redeploy.
Customer phone verification fails
Likely cause: Phone Authentication, the SMS region or the production authorized domain is missing.
Resolution: Check Authentication > Sign-in method, the SMS region policy and Authorized domains in Firebase Console. Enter the hostname without https:// or a path.
Saved configuration does not appear
Likely cause: The setting was not saved, a cached build is open or the wrong project is deployed.
Resolution: Select Save changes, confirm the success label, refresh in a private window and verify the active Firebase project.
When contacting support, use the template under Support. Never send passwords, private keys, service-account files or provider secrets.