Deploy Odoo Community Restaurant POS
Odoo 19 restaurant POS with QR self-ordering and per-outlet databases.
Just deployed
/var/lib/odoo
Postgres
Just deployed
/var/lib/postgresql/data
Deploy and Host Odoo Community Restaurant POS on Railway
Run Odoo 19 Community for restaurant point of sale and mobile self-ordering. Start with one outlet on a Railway HTTPS address. Operators serving independent restaurants can configure distinct outlet hostnames, administrator credentials, databases, and filestore directories within a shared deployment.
About Hosting Odoo Community Restaurant POS
- Odoo 19 Community with Point of Sale, Restaurant and Self-Ordering modules, pinned to the tested image digest.
- PostgreSQL 16 on Railway private networking.
- Persistent volumes for PostgreSQL and the Odoo filestore. Only Odoo receives a public HTTPS endpoint.
First login
Wait for the initial database and modules to finish installing. Open the Odoo service’s Railway HTTPS address, sign in as admin with the generated ODOO_ADMIN_PASSWORD from the Odoo service variables, and configure your business information and country-specific settings. Set up products, a restaurant floor and tables, a POS register, and the self-order mode you want. Open a register and place a disposable order before using the workflow with customers.
Additional outlets
Attach custom or wildcard domains to the Odoo service using a DNS zone you control. The first DNS label selects the database, so outlet2.example.com maps to outlet2. Add the labels to ODOO_ADDITIONAL_TENANTS as a comma-separated list. Set a unique ODOO_ADMIN_PASSWORD_<label> for each additional tenant, uppercasing the label and replacing hyphens with underscores. Redeploy to initialize the new outlets, then verify each HTTPS URL and login independently. Set ODOO_PRIMARY_HOST before first deployment if you want the initial database to take its label from a custom domain. Preserve an established label when planning a domain migration.
Railway creates one generated public hostname per service. Additional branded hostnames require the operator's DNS setup and certificate verification. Each outlet has its own database, users, and filestore directory. The application, PostgreSQL server, and infrastructure are shared.
Recovery, hardware, and cost
Back up both the database and its matching filestore. Rehearse a restore to an isolated target. This template does not schedule backups. Printer models, physical payment terminals, and integrations such as Mollie require separate setup and verification. This listing uses Odoo Community modules. Railway bills app/database compute and volume storage. Check the usage estimate for your plan and workload.
Common Use Cases
- Set up an Odoo register with a menu and table layout for a restaurant or café.
- Let dine-in guests open a self-order menu by scanning a table QR code.
- Host independently managed outlets with separate databases and logins on shared infrastructure.
Dependencies for Odoo Community Restaurant POS Hosting
Deployment Dependencies
- Odoo 19 Community and PostgreSQL 16 are included.
- Additional public outlet hostnames require DNS records and TLS certificates for a domain you control.
Why Deploy Odoo Community Restaurant POS on Railway?
Railway provisions the Odoo app, private database networking, persistent volumes, and an initial HTTPS endpoint in one deployment. Install with a single outlet, then configure additional hostnames when you are ready.
Maintained by RailGenius. Odoo Community is distributed under LGPLv3. This is an independent community template.
Odoo deployment documentation · Railway custom domains · Odoo licensing
Template Content
Postgres
postgres:16-alpine