Skip to Content
Odoo model · Enterprise

pos.store.timing

Pos Store Timings. Defined in module pos_urban_piper_enhancements; exists in Odoo 18, 19. 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 pos_urban_piper_enhancements
  4. Odoo 19 pos_urban_piper_enhancements
  5. Odoo 20 not present

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 17 to 18

Community only All changes in this step

Not covered: this step compares Community modules only and this model belongs to an Enterprise module.

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

Removed in Odoo 20.

1 views of this model removed
  • pos_urban_piper_enhancements.view_pos_store_timing_list
1 actions on this model removed
  • pos_urban_piper_enhancements.action_pos_store_timing
1 menus opening this model removed
  • pos_urban_piper_enhancements.menu_products_pos_store_timing

All fields declared on pos.store.timing (4)

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 4 fields
FieldTypeLabelModule1617181920
config_idsmany2many pos.configPoint of Sale accociated to this timingpos_urban_piper_enhancementsE
end_hourfloatEnding Hourpos_urban_piper_enhancementsE
start_hourfloatStarting Hourpos_urban_piper_enhancementsE
weekdayselectionWeek Daypos_urban_piper_enhancementsE

Related models

Linked by its relational fields: pos.config

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.