Skip to Content
Odoo model · Enterprise

urbanpiper.store.aggregator

UrbanPiper Aggregators and their related information for Online Food Delivery Stores. Defined in module pos_urban_piper; exists in Odoo 20. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.

  1. Odoo 16 not covered
  2. Odoo 17 not covered
  3. Odoo 18 not present
  4. Odoo 19 not present
  5. Odoo 20 pos_urban_piper

This is an Enterprise model: Odoo 16 and 17 Enterprise sources are not part of the data, so those versions show as not covered.

Odoo 19 to 20

Community + Enterprise All changes in this step

New model in Odoo 20.

All fields declared on urbanpiper.store.aggregator (9)

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 9 fields
FieldTypeLabelModule1617181920
company_idmany2onepos_urban_piperE
default_customer_idmany2one res.partnerDefault Customerpos_urban_piperE
delivery_provider_idmany2one pos.delivery.providerDelivery Aggregatorpos_urban_piperE
has_active_store_sessionbooleanpos_urban_piperE
is_onlinebooleanIs Online?pos_urban_piperE
payment_method_idmany2one pos.payment.methodUrbanPiper Payment Methodpos_urban_piperE
pricelist_idmany2one product.pricelistPricelistpos_urban_piperE
store_idmany2one pos.urbanpiper.storeUrbanPiper Storepos_urban_piperE
use_create_customerbooleanCreate Customerpos_urban_piperE

Related models

Inherits: pos.load.mixin

Linked by its relational fields: pos.delivery.providerpos.payment.methodpos.urbanpiper.storeproduct.pricelistres.partner

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.

Planning an Odoo upgrade?

Odoo app Check your own database: Studio Upgrade Checker Scans your Studio fields, views, automations and custom code for everything listed here before you upgrade. See it on the Odoo Apps store Odoo app Fix broken views: Studio View Repair Assistant Finds views that stopped loading after an upgrade and helps you repair the xpaths and fields they point at. See it on the Odoo Apps store Upgrade service Need the upgrade done? Book a call We move databases between major Odoo versions, port custom modules and validate the data. Book a call Free Free upgrade scan, we run it for you Send us a copy of your database or give us access and we report what will break on the target version. Ask for a scan