Odoo’s paid service integrations were reorganized into shared bridge modules so related apps can reuse the same foundations more consistently. This is mainly an internal cleanup that improves maintainability and reduces future migration risk, with compatibility kept for existing code during the transition.

Stock movement scheduling now uses a single date field instead of keeping a separate expected date. This reduces duplicate information and makes stock, manufacturing planning, and inventory reports easier to maintain, while the previous scheduled date is no longer retained once a move is completed.

In community, the date_expected fields was duplicated with the date fields
except when the move was done. Merge both fields.
The only information lost is: we can't know what was the
scheduled date before processing move (put in done).
Indeed, the date becomes the actual move processing.

task-2246665
odoo/odoo#55379
odoo/upgrade#1586