How to Keep Your POS in Odoo.sh From Crashing When Stores Open
Every morning, when store cashiers start their shift, the first thing they do is open their Point of Sale in Odoo. So far, everything seems normal. But in implementations on Odoo.sh, starting several registers at the same time often causes load spikes that crash the server and leave cashiers waiting in frustration.
The problem is not a minor one: each POS must authenticate the user, download products, customers, taxes and even images before recording the first sale. If we are talking about 20 or 30 registers connecting at once, the flood of HTTP requests can be devastating for the database.
The good news is that you do not need to touch the server configuration or break the business logic. There are simple adjustments within Odoo 18 itself that reduce the load and let your cashiers open their POS without delays or crashes.
Reducing the product load
One of the main factors causing slowness is the number of products preloaded in each session. If you do not optimize this part, your POS will try to synchronize thousands of references that are not even sold in the store.
- Mark only the products that are actually sold in your business as Available in POS.
- Archive old or unused products so they do not interfere with synchronization.
- Use POS categories to keep the catalog organized.
- In Odoo 18, enable deferred product loading, so products are downloaded only when they are searched for.
Optimizing customers in POS
By default, Odoo downloads all registered contacts, which becomes unsustainable if your database is very large. This means the POS loads customers who may never buy in the store.
- Enable the Search customers online option so the cashier can look them up in real time.
- Preload only frequent customers, if the business requires it.
This way you prevent each POS from handling thousands of unnecessary contacts and allow fast searches when they are really needed.
Images and resources
Another factor that slows down the POS startup is high-resolution images. Each simultaneous download of visual resources increases the load and slows the start.
- Use thumbnails instead of large images.
- Disable the option to show large images if it is not essential for the register's operation.
Conclusion
On Odoo.sh you cannot assign dedicated workers to longpolling or directly modify the file
odoo.conf. But that does not mean you have to resign yourself to suffering crashes every morning.
By applying these functional adjustments in Odoo 18 you will achieve:
- Fewer products and customers preloaded on each register.
- Optimized images and lighter resources.
This way your operation stays stable, the daily cash closing is not affected and your cashiers can work without interruptions.