Sync POS orders across multiple sessions

by ,
Odoo          
v 8.0 Third Party 50

400.00 €

You bought this module and need support ? Click here !
Technical name pos_multi_session
LicenseGPL-3
Websitehttps://yelizariev.github.io
Read description for v 12.0 v 11.0 v 10.0 v 9.0
Required Apps Point of Sale (point_of_sale)
Sales Management (sale)
Online Billing (account_voucher)
eInvoicing (account)
Warehouse Management (stock)
Included Dependencies
Technical name pos_multi_session
LicenseGPL-3
Websitehttps://yelizariev.github.io
Read description for v 12.0 v 11.0 v 10.0 v 9.0
Required Apps Point of Sale (point_of_sale)
Sales Management (sale)
Online Billing (account_voucher)
eInvoicing (account)
Warehouse Management (stock)
Included Dependencies

Sync POS orders across multiple sessions

E.g., create order in POS1, expand it in POS2, get payment in POS3.

Usage

Note. To use the module, you need to be sure that your odoo instance support longpolling, i.e. Instant Messaging works.

Open "Point of Sale → Configuration → Point of Sales" and create or open some Point of Sale record.

Set Multi-session value (create new one if need) and untick "Allow payments" if current POS is used only to create orders. Set the same Multi-session for other "Point of Sale", which should be synced.

Start POS session on all POSes:

  • login as user1 on computer1 ⇒ start session on POS1
  • login as user2 on computer2 ⇒ start session on POS2
  • etc

When you start to create order in POS1(user1) session, you can see how items are displayed in the synced session POS2(user2). Moreover, items added at the corresponding POS are marked as "added by POS1", "added by POS2" and etc.

The synced POS2(user2) session will be displayed as follows:

Sync POS orders across multiple sessions

Longpolling

Check following resources about activating longpolling:

In short, you need to start server with non-zero workers parameter::

openerp-server --workers=2 ...

and configure nginx:

location /longpolling {
    proxy_pass http://127.0.0.1:8072;
}
location / {
    proxy_pass http://127.0.0.1:8069;
}

Domain switching

There is a rare case, when you need to clear browser data after installation: if you use this module on a website domain, that was previously used by another database with this module installed. E.g. main_company.example.com was used by database1 and then the domain starts to handle another database2. In that case browser data has to be cleanned on all devices before first use.

Please log in to comment on this module