Skip to Content
Odoo model

product.wishlist

Product Wishlist. Defined in module website_sale; exists in Odoo 16, 17, 18, 19, 20. Across the upgrade steps we tracked: 0 fields added, 1 removed, 0 renamed.

  1. Odoo 16 website_sale_wishlist
  2. Odoo 17 website_sale_wishlist
  3. Odoo 18 website_sale_wishlist
  4. Odoo 19 website_sale_wishlist
  5. Odoo 20 website_sale

Odoo 16 to 17

Community only All changes in this step

No change to this model's own fields in this step.

Odoo 17 to 18

Community only All changes in this step

No change to this model's own fields in this step.

Odoo 18 to 19

Community + Enterprise All changes in this step

No change to this model's own fields in this step.

Odoo 19 to 20

Community + Enterprise All changes in this step

Fields removed (1)

FieldTypeModuleNotes
stock_notificationbooleanwebsite_sale_stock_wishlistIts module (website_sale_stock_wishlist) is not in Odoo 20: removed, renamed or merged into another module.

All fields declared on product.wishlist (8)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 8 fields
FieldTypeLabelModule1617181920
activebooleanwebsite_sale
currency_idmany2one res.currencywebsite_sale
partner_idmany2one res.partnerOwnerwebsite_sale
pricemonetaryPricewebsite_sale
pricelist_idmany2one product.pricelistPricelistwebsite_sale
product_idmany2one product.productProductwebsite_sale
stock_notificationbooleanwebsite_sale_stock_wishlist
website_idmany2one websitewebsite_sale

Related models

Linked by its relational fields: product.pricelistproduct.productres.currencyres.partnerwebsite

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.