| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Point of Sale (point_of_sale) • Inventory (stock) • Invoicing (account) |
| Lines of code | 2788 |
| Technical Name |
pos_sales_sync |
| License | OPL-1 |
| Website | https://techpro.al |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Point of Sale (point_of_sale) • Inventory (stock) • Invoicing (account) |
| Lines of code | 2788 |
| Technical Name |
pos_sales_sync |
| License | OPL-1 |
| Website | https://techpro.al |
Offline POS Branch Sales Sync
Standalone synchronization dashboard for offline remote POS branches and a central Odoo database.
Versions
19.0
This release is built for Odoo 19.0. Module version: 19.0.1.0.0.
Centralized Sales Review
Import sales from offline branch POS databases into the central Odoo Sales application as draft Sales Orders. Back-office users can review imported orders before confirmation and invoicing.
Branch-by-Branch Control
Configure each POS branch separately with its own connection, default customer, salesperson mapping, warehouse, pricelist, receive schedule, and master-data selection.
Master Data Sending
Send selected products, customers, taxes, and POS payment methods from the central database to branch POS databases. The wizard supports changed-record filtering, manual selection, searchable record loading, preview, queueing, and immediate send with result logging.
Failure Visibility
Failed sync requests are stored with plain-language error messages, suggested fixes, payload details, retry actions, and operational status. Users can retry failed records from the dashboard or log views.
Main Features
- Central-only module: no custom module installation is required on branch POS databases.
- Standalone Offline POS Sync application, menu, dashboard, logs, and POS location management.
- Manual and scheduled receiving of branch POS sales.
- Draft Sales Order creation for imported branch sales review.
- Remote user mapping to central salespeople.
- Per-branch sync frequency and start date/time to avoid all branches syncing at the same moment.
- Controlled master-data pushing with selected records and changed-only logic.
- Duplicate prevention through stored remote identifiers and sync logs.
- Encrypted storage of branch connection passwords/API keys.
- Security group for controlling which users can access the module.
Typical Use Case
A company operates multiple branch POS databases that may work offline or over unstable connections. The central database periodically receives branch sales and sends controlled master data to keep POS locations aligned without forcing live dependency on the central database during selling.
Requirements
The central Odoo database must have this module installed. Each branch POS database must be reachable through the configured Odoo XML-RPC URL when synchronization runs, and the configured branch user must have access to the required POS, product, contact, tax, and accounting records.
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