Skip to Content

TDS Multi-Branch Self-Order

by
Odoo

$ 55.98

In-App Purchases
v 19.0 Third Party
Versions 17.0 18.0 19.0
You bought this module and need support? Click here!
Versions 17.0 18.0 19.0
TDS Multi-Branch Self-Order for Odoo

TDS Multi-Branch Self-Order

One Website entry — each branch's native POS kiosk Self-Order

Multi-shop restaurants need a public place to ask: "Which branch?" Odoo Self-Order is excellent per Point of Sale, but guests should not juggle many kiosk links. TDS Multi-Branch Self-Order adds a themed Website picker, then hands customers off to that shop's unmodified native kiosk Self-Order — same menu, kitchen path, stock and payments. No website_sale cart. No separate sale.order kitchen bridge.

Read this before you buy

This module is a Website multi-branch launcher for Odoo's existing POS Self-Order. It does not rebuild the kiosk UI, replace Kitchen Display, or ship its own Stripe/Apple Pay connector. Buy it if you already run (or will run) Self-Order kiosks per branch and need one public Website entry.

Ideal if you have

  • Several shops as separate pos.config
  • POS Self-Order (kiosk recommended) on those shops
  • Open POS sessions during online hours
  • Website installed

Not for you if you need

  • Full eCommerce / website_sale checkout
  • A Website-themed menu instead of the kiosk UI
  • sale.order → kitchen without POS Self-Order
  • Delivery logistics beyond native POS presets

One URL for every branch

Publish /order-online (menu included) or drop the Self-Order Branches snippet on any Website page. Guests pick Downtown, Airport, Mall … then continue.

Native kiosk, unchanged

After selection we redirect to /pos-self/<config>?access_token=… — the same Self-Order engine as your physical kiosk: products, cart, payment UI.

Correct kitchen & stock

Orders are pos.order on the selected POS. Prep Display, stock and payments stay branch-correct. No double posting through Website Sale.

How it works

1 — Guest opens Order Online

From the Website menu or a landing page. Branches you enabled for Website listing appear as cards (unavailable when the POS session is closed).

Website branch picker

2 — Order on that branch's native kiosk

"Order here" redirects into unmodified Odoo Self-Order for that pos.config. Landing, menu and cart are the standard kiosk experience.

Native Self-Order landing Native Self-Order menu

3 — Pay with that POS's Self-Order payments

If the POS has Self-Order online payment / supported terminals (e.g. Stripe), guests pay on the Self-Order flow (QR on kiosk mode). If not, Odoo uses the native pay-at-counter confirmation. There is no separate "pay now or cashier" picker invented by this module — it follows POS configuration.

Self-Order payment QR

Configuration

Prepare each Point of Sale

  • One pos.config per physical branch (own stock / payments as needed).
  • Self-Order mode: Kiosk (recommended) or Mobile; products available in POS.
  • Non-cash payment methods on kiosk; open a session and leave it Opened while online.
  • Optional: Preparation Display linked for kitchen QA.
  • Chart of accounts loaded so product income accounts exist before taking paid orders.

Enable Website Self-Order on the POS form

Tick Available on Website Self-Order, set public Website Branch Label and optional subtitle (address / hours). Publish via menu Order Online or the Website Builder snippet.

POS Website Self-Order settings

Features

  • Website branch picker page (/order-online) + Website Builder snippet + menu item.
  • Per-POS flags: online availability, public label, subtitle.
  • Guards: Self-Order kiosk/mobile mode + opened session required to enter ordering.
  • Clear unavailable page when a closed branch is requested.
  • Redirect to native Self-Order URL with access token — zero custom kiosk UI.
  • Uses each branch's native Self-Order payments (online payment / terminals) when configured.
  • No dependency on website_sale; designed for a pure pos.order path.

Operator tips

  • Keep POS sessions open during service hours; closed session = unavailable on Website.
  • Test Self-Order payments on staging (Demo provider / Stripe test) before go-live.
  • Hide a shop instantly by unticking Website availability — no need to delete the POS.
  • Do not paste raw kiosk access tokens in ads; the picker already handles safe redirects.

FAQ

Will the menu after branch pick look like my Website theme?

Only the picker follows the Website theme. Ordering uses the native kiosk Self-Order UI on purpose (same as in-store devices).

Does this create sale orders?

No. Flow stays on POS Self-Order / pos.order.

Apple Pay / PayPal / Stripe?

Configure Odoo Self-Order online payment / payment providers (e.g. Stripe) on each POS. This module does not add a separate payment gateway.

Requirements

  • Odoo 19.0 (Community or Enterprise). Built and QA'd on Enterprise with Self-Order / Prep Display.
  • Depends on website and pos_self_order (Point of Sale).
  • UI translations included: English (source), Arabic, Indonesian, Malay, Spanish, Simplified Chinese.
  • Recommended: POS Restaurant, Preparation Display, Self-Order online payment / Stripe as needed.
  • website_sale is not required.
TechNion Digital Solutions

TechNion Digital Solutions

Odoo implementation • Custom development • AI integrations

Not sure this fits your restaurants? Tell us how many branches and which Self-Order payments you use — we confirm fit before you purchase.

tnion.com  |  support@tnion.com  |  info@tnion.com  |  WhatsApp +62 811 8806 2282

Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Website (website)
• Restaurant (pos_restaurant)
• Discuss (mail)
• Point of Sale (point_of_sale)
• Inventory (stock)
• Invoicing (account)
Lines of code 253
Technical Name tds_website_pos_self_order
LicenseOPL-1
Websitehttps://tnion.com 
Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.