API key: A value that allows software to connect to a service. Firebase Web App keys identify the project but are not treated like server passwords. Payment and messaging secret keys must remain private.
Blaze plan: Firebase pay-as-you-go billing. It includes usage allowances, then charges for usage above applicable allowances. Budget alerts notify you but do not stop charges.
Build: The command that converts the source files into the optimized dist folder that a website host can publish.
Cloud Functions: Trusted backend code running in Firebase. It validates orders, protects totals and communicates with optional providers.
Environment file: A local text file such as .env.development or .env.production containing the settings used when Ordio is built.
Firebase project: The Google-owned workspace containing Authentication, Firestore, Storage and Cloud Functions for your installation.
Firestore: The database where Ordio stores business settings, products, customers and orders.
Hosted checkout: A payment page operated by the payment provider. Ordio sends the customer to that page and receives a secure result.
Provider: An optional external service such as Stripe, PayPal, Paystack, Yoco, Meta WhatsApp or Google Maps.
Security rules: Firebase files that decide which signed-in user can read or change specific data and uploaded files.
SPA rewrite: A hosting rule that returns index.html for routes such as /admin. Without it, refreshing a route may show a 404 page.
Storage: Firebase file storage used for logos, hero images and product images.
Webhook: A secure server-to-server notification. Payment providers use webhooks to confirm payment independently from the customer's browser.