Daily updates from Odoo
Tuesday, August 19, 2025
3 changes · master
New functionality added to Odoo
The Point of Sale delivery integration now supports Wolt as an additional food delivery provider. This gives restaurants using Odoo more choice in connecting their delivery operations to external platforms.
Original PR description
Following this commit: - Integrated Wolt as delivery provider in pos_urban_piper. task-4882282 Forward-Port-Of: odoo/enterprise#88222
The Adam Equipment scale driver is now available as a separate module and must be enabled explicitly in Point of Sale settings. This prevents unrelated serial devices from being mistakenly detected as scales, reducing setup confusion for customers using IoT boxes and FDM devices.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/221326 Upgrade PR: https://github.com/odoo/upgrade/pull/8142 Before this commit, the Adam Equipment serial scale driver was included by default on the IoT box. However, this causes issues as there is no way to detect the presence of one of these scales automatically. This caused any unidentified serial device to be registered as an Adam scale, leading to much confusion with customers, especially regarding setting up an FDM. After this commit, the Adam driver is moved into its own module, and a checkbox added to the PoS settings to enable it. This way, only customers who actually need the driver will get it, and everyone else can benefit from not having it wrongly detect devices. task-4954021
Adds a new integration that lets restaurants and other appointment-based businesses offer bookings through Google Maps Reserve. Odoo can share availability, receive new or changed bookings via the IAP service, and keep Google updated when schedules change.
Original PR description
The new appointment_google_reserve module allows to make your restaurant (or other booking based service) available to book via Google Maps Reserve. See: https://www.google.com/maps/reserve…
The new appointment_google_reserve module allows to make your restaurant (or other booking based service) available to book via Google Maps Reserve. See: https://www.google.com/maps/reserve https://developers.google.com/actions-center/verticals/reservations/e2e/overview The integration works alongside with the IAP server, that plays the middleman between the client server and the Google servers. It is split in three main concepts: 1. The Feed files uploads See: https://developers.google.com/actions-center/verticals/reservations/e2e/integration-steps/export-feeds The Google Reserve Service is based on data coming from "feed files", which are manually uploaded once per day via a HTTP call to the IAP servers. IAP servers will take care of the Merchant and Service feed files based on the merchants that registered for this service. The merchant/service registration happens via a HTTP call to the IAP server when an appointment.type is configured accordingly. This is simply done on the appointment.type form by specifying the "merchant" (which is a physical address and some contact details). The same merchant could be re-used between several appointment.types, for example if a hotel allows booking rooms (1 appointment.type) and massages (with a second appointment.type): the merchant is the hotal (same physical location) and the services are both appointment.types. The availabilities for all these services are uploaded to the IAP server with a HTTP call when the IAP server requests them. (See IAP commit message / documentation for more details). 2. The Booking Server See: https://developers.google.com/actions-center/verticals/reservations/e2e/integration-steps/implement-booking-server Once a end-user books something from Google Maps Reserve, they (Google) will hit a certain endpoint on the IAP server with the booking details. IAP then needs to relay this information to the merchant (client)'s, acting as a proxy. The information is then stored accordingly, for example as a new calendar.event record on the related appointment.type. The same principle is applied to other necessary concepts; modify bookings, cancel bookings, ... 3. Real-time API updates See: https://developers.google.com/actions-center/verticals/reservations/e2e/integration-steps/real-time-api-updates This is in a way the same thing as the booking server, but the other way around. Whenever something happens that modifies availabilities for an appointment, including: - Creating a booking directly in the backend - Creating calendar leaves for the appointment resources - Modifying opening hours - ... We need to update the availabilities on Google's side. In that case, the communication is thus initiated by the client server, that contacts IAP. IAP acts as a proxy again by relaying this information to Google. =============================================================================== Limitations: - Only works for auto-assign mode appointment types - Payment and sales related flow are not implemented. Task-3083812 Forward-Port-Of: odoo/enterprise#92457 Forward-Port-Of: odoo/enterprise#82234