HomeModulesPoint of SalePOS Happy Hour | Recurring Time-Based Pricing for Pricelists
POS Happy Hour | Recurring Time-Based Pricing for Pricelists
Point of SaleAuraOdoo Verified

POS Happy Hour | Recurring Time-Based Pricing for Pricelists

Weekly recurring price rules: Mon-Thu 15:00-18:00, not a single fixed date

Technical Specifications & Compatibility

Technical Module Name
Supported Odoo Versions
v19.0
License
Point
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
586 lines (Python / XML / JS)

Overview & Description

Point of Sale POS Happy Hour Recurring time-based pricing for Odoo pricelists: Monday to Thursday, 15:00 to 18:00 — not a single fixed date range. Happy hour, lunch menu, early bird or a late-night rate, applied automatically in the Point of Sale and everywhere else the pricelist is used, with a live badge that tells the cashier what is running. Odoo 19.0 Odoo 20 Community Enterprise Version 19.0.1.0.0 OPL-1 Depends on point_of_sale only 7 Days, each its own switch 1 Field added to a rule 46 Automated tests 0 Extra dependencies Module Overview Odoo can price a fixed date range. It cannot price a Tuesday afternoon. The gap in the pricing engine A pricelist rule in Odoo carries a validity period — a start date and an end date. That is one fixed window: from the 3rd of March at 14:00 until the 9th at 18:00. There is no hour of the day and no day of the week anywhere in the pricing engine. So 20% off house drinks, Monday to Thursday, 15:00 to 18:00 simply cannot be expressed — which is exactly what a happy hour is, and a lunch menu, and an early-bird rate, and a late-night surcharge. What this module adds A price window: days of the week plus a time range, saved as a record you define once and attach to as many pricelist rules as you like. Change the hours in one place and every rule follows. The window is checked in the same place the standard engine checks the validity period, so every caller gets it — the till, quotations, the website. A rule with no window behaves exactly as it always did. Existing databases are unaffected. A rule without a time window never reaches the new check, so pricing you already rely on continues to behave identically — there is a dedicated regression test that proves it. Key Features A scheduling primitive the pricing engine was missing, and the till-side honesty that has to come with it. Price Windows Recurring, not one-off Days of the week plus a time range, repeating every week — the thing a single start-and-end date can never express. Defined once, used many times One window drives any number of pricelist rules across any number of pricelists. When the hours change, you change them in one record. Any days, to the minute Each of the seven days is its own switch — weekdays only, weekends only, Tuesdays only. And 15:30 to 18:45 is as valid as 15:00 to 18:00. Crosses midnight correctly 22:00 to 02:00 is a late-night rate. One o'clock on Saturday morning belongs to Friday night's window — including whether Friday itself is switched on. Readable schedule Every window shows its own summary — Mon Tue Wed Thu, 15:00 to 18:00 — so nobody has to decode seven checkboxes to know when it runs. Guarded against silent no-ops A window with no days ticked, or one that starts and ends at the same time, is refused on save rather than saved and never running. In the Pricing Engine One field on the rule Time Window, sitting beside the standard validity period, because it answers the same question. Nothing else about the rule changes. Every caller gets it The window is filtered where the standard engine filters the date range, so the till, quotations, sales orders and the website all honour it without any of them being patched. Any price computation Fixed price, percentage or formula — whatever the rule already computes. The window only decides whether the rule applies, never what it works out. Stacks with the validity period A window narrows a rule, it does not replace the date range. A summer promotion that also runs only in the afternoon is two settings on one rule. Specificity is untouched Product rules still beat category rules, which still beat global ones. Adding a window does not reshuffle the order in which rules win. No cliff outside the window Outside the hours, an ordinary untimed rule applies as normal — the price does not fall back to the bare sales price because the timed rule stopped. At the Till Prices apply live, offline included The window is evaluated in the browser, so a till that has lost its connection keeps pricing correctly, like the rest of the Point of Sale. A badge that says what is running Which window is on and how many minutes are left, in the Point of Sale header. A price that moves with no explanation is how a cashier stops trusting the till. Amber before it closes The badge changes colour a configurable number of minutes before the end, so the cashier can tell a customer that the offer is about to finish. Start and end notices The till announces when a window opens and when it closes, so a change in price is always something the cashier saw coming. Several windows at once When more than one is running, the badge shows the one nearest to ending plus a count of the rest — the useful figure, not a list. Cheap and optional One check every thirty seconds with no server round trip, and the whole badge can be switched off per Point of Sale. Business Benefits What a bar, cafe or restaurant actually gets from it. Fill the quiet hours Price the mid-afternoon, the early evening or the last hour differently, and let the schedule run itself week after week. Nobody has to remember No manager switching a pricelist on at three and off at six, and no discount left running all night because someone forgot. One place to change the hours Move happy hour half an hour later and every rule that uses it moves with it — across every pricelist and every shop. The same price everywhere Because the rule is filtered inside the pricing engine, the website and a quotation quote the same figure the till charges. Fewer arguments at the counter The cashier can see the offer is running and how long is left, so "but the sign says happy hour" has an answer on screen. Late-night rates that work A window crossing midnight is handled properly, so a 22:00 to 02:00 price is a setting rather than a workaround with two rules. Safe to trial Nothing changes until a rule is given a window, and clearing that one field puts the rule back exactly as it was. Nothing extra to run One dependency, no external libraries, no scheduled job driving prices, and no third-party service. Screenshots Setting a window up, and what the cashier sees when it runs. Screenshot placeholder A price window Days as toggles, a time range, the readable schedule and a live indicator showing whether it is running right now. Screenshot placeholder Time Window on a pricelist rule The new field beside the standard validity period, on an otherwise ordinary percentage rule. Screenshot placeholder The running badge in the till Happy Hour running in the Point of Sale header with the minutes remaining, turning amber as the end approaches. Screenshot placeholder Timed Price Rules Every timed rule across every pricelist in one list, with the ones currently running marked. Workflow Four steps, and only one of them is new. Step 1 — Define the window Point of Sale → Configuration → Price Windows → New. Name it Happy Hour, set 15:00 to 18:00, tick Monday to Thursday. Step 2 — Add a rule Open a pricelist and add a rule exactly as you always have: 20% off, a fixed price, or a formula, on a product or a category. Step 3 — Attach the window Set Time Window on that rule to Happy Hour. That is the only new step in the whole workflow. Step 4 — Sell The price applies only inside the window, in the till and everywhere else, and the cashier sees a badge while it runs. Set your cashiers' user timezone to the shop's. Both the server and the till read the Odoo user's timezone, never the machine's clock, so that a shop PC set to another region cannot price a sale differently from the rest of Odoo. Configuration A window record, one field on a rule, and two till settings. The price window — Configuration → Price Windows Field What it does Default Window The name the cashier sees on the badge. Translatable. Required From / To The time range, to the minute. The start is inside the window, the end is not. 15:00 – 18:00 Mon … Sun Seven independent switches, one per weekday. Mon – Fri Schedule Read-only summary of the days and hours, so nobody decodes checkboxes. Computed Running Now Live indicator on the window and on every rule using it. Computed Company Windows belong to a company and are isolated by a record rule. Current Archived Archiving stops the discount immediately, including on tills that cached it. Active On the pricelist rule Time Window The window this rule obeys. Empty means the rule behaves exactly as before. Per shop — Settings → Timed Pricing Setting Default Show Running Windows On Warn Before End 10 minutes Setting the warning to zero disables the amber state and leaves the badge itself in place. Two shortcuts live in the settings. One takes you straight to Price Windows, the other to Timed Price Rules — every rule with a window, across every pricelist, in a single list with a live Running column. Technical Details How it hooks the pricing engine, for the person who has to maintain it. Module Technical name pos_happy_hour_aura Version 19.0.1.0.0 Category Sales / Point of Sale Licence OPL-1 Dependencies point_of_sale External libraries None New model pos.price.window Models extended product.pricelist.item, pos.config, pos.session, res.config.settings Automated tests 46, across window logic and pricing Implementation Filtered where core filters The window check sits in the same place the standard engine applies the validity period, which is why every caller inherits it instead of each one being patched. One clock, two halves The server converts through the Odoo user's timezone and the till reads the same user timezone in the browser, so they cannot disagree about when a window runs. Inclusive start, exclusive end 15:00 is inside the window and 18:00 is not, so a single moment can never belong to two consecutive windows at once. Fails closed, never open A rule whose window is missing from the till's data is treated as switched off. An archived window is dropped from tills that cached it. Rules cannot be orphaned A window still driving rules cannot be deleted by accident, so a price cannot quietly lose its schedule. Zero cost when unused A rule with no window never reaches the check at all, so an existing database pays nothing for the feature. Test coverage Window logic Weekday matching, the exact boundaries, and the midnight wrap including which day an after-midnight moment belongs to. Timezones Conversion through the user timezone, so a window means the same thing on the server and in the browser. Pricing Inside, outside, archived, stacking with the date range, and rule specificity left intact. Regression guard A dedicated test proving untimed rules are completely untouched by the module. Compatibility Where this module runs. Item Supported Notes Odoo 19.0 Yes Built and tested for 19.0. Odoo 18.0 and earlier Not in this build Contact support if you need a backport. On-Premise Yes Drop the module in your addons path and update the app list. Odoo.sh Yes Add it to your repository and let the build install it. Odoo Online (SaaS) No Odoo Online does not allow custom modules to be installed. Sales and eCommerce Yes Quotations and the website use the same pricing engine, so they honour windows too. Restaurant mode Yes Works alongside pos_restaurant; floors, tables and orders all price through the pricelist. Multi-company Yes Windows carry a company and are isolated by a record rule. Offline till Yes Windows are evaluated in the browser, so pricing survives a lost connection. Supported Editions The module depends on point_of_sale only, so both editions are covered. Community Edition Fully supported Every feature works on Community, including the till badge and the administration lists. Enterprise Edition Fully supported Same behaviour on Enterprise, alongside the Enterprise Point of Sale applications such as restaurant and self-order. Installation A standard Odoo module install. No configuration files to edit. Download the module and copy the pos_happy_hour_aura folder into your Odoo addons directory. Restart the Odoo service so the new addon is picked up. Enable developer mode, then go to Apps and choose Update Apps List. Search for POS Happy Hour, remove the Apps filter if needed, and click Install. Check that your cashiers' user records have the shop's timezone set, under Settings → Users. Create your first window under Point of Sale → Configuration → Price Windows, then set Time Window on a pricelist rule. Point of Sale must be installed first. This module depends on the standard point_of_sale application and Odoo will install it automatically if it is missing. Frequently Asked Questions The questions that come up first, and the answers that usually settle them. Only for one fixed stretch of time. A validity period runs from one moment to another and then stops — it has no concept of a weekday or an hour of the day, so it cannot repeat every Monday to Thursday afternoon. That is precisely the gap this module fills. Yes. The window is applied inside the pricing engine itself, at the same point the validity period is applied, so anything that asks the pricelist for a price honours it — quotations, sales orders and the website included. Yes, and it is handled properly rather than by splitting it in two. Set 22:00 to 02:00 and one o'clock on Saturday morning belongs to Friday night's window — so if Friday is ticked and Saturday is not, that sale is still discounted. The Odoo user's timezone, on both the server and the till — never the operating system clock of the machine. That is deliberate: a shop PC set to the wrong region would otherwise price a sale differently from every other part of Odoo. Set the cashiers' user timezone to the shop's and the two halves can never disagree. The timed rule simply stops applying, and the next matching rule takes over as it normally would. The price does not collapse back to the bare sales price unless there was no other rule to begin with. Yes, and that is the point of making it a record. One window can be attached to as many rules as you like across as many pricelists as you like. Change its hours once and every one of them moves together. Archive the window. The discount stops on the server at once, and the window is dropped from tills that had already cached it — so an open session stops discounting too. Yes. The window is evaluated in the browser from data the till already holds, with no server round trip, so pricing keeps working offline like the rest of the Point of Sale. No. A rule with no time window never reaches the new check, so an existing database prices exactly as it did before. There is a test in the suite whose only job is to prove that. Point of Sale managers configure them; cashiers can only read them, which is what the till needs to price correctly. Windows are also isolated per company by a record rule. Changelog Release history for Odoo 19.0. Version 19.0.1.0.0 Initial release Recurring price windows: seven independent weekday switches plus a time range, to the minute, with midnight-crossing support. A Time Window field on pricelist rules, filtered where the engine filters the validity period so every caller obeys it. Live badge in the Point of Sale with minutes remaining, an amber warning state, and start and end notices. Administration: a Price Windows list with a Running column, and a Timed Price Rules list covering every pricelist. Guards against silent no-ops, orphaned rules and archived windows left running on cached tills. Multi-company record rules and access rights: cashiers read, managers configure. 46 automated tests across window logic and the pricing engine, including a regression guard for untimed rules. Support Written and maintained by Aura Odoo Tech. Email Questions, problems or a feature you need — write to us directly. odooaura@gmail.com Website More Odoo modules, documentation and customisation services. www.auraodoo.tech Included Free installation help, bug fixes and compatibility updates for the Odoo 19.0 release line. Before you write in: the module ships a user guide and a technical guide alongside the code, covering every setting, the timezone rules and how the pricing hook works if you intend to extend it. POS Happy Hour Odoo 19.0 · pos_happy_hour_aura · depends on point_of_sale only Odoo 19.0 19.0.1.0.0 OPL-1 Community & Enterprise Copyright 2021-2026 Aura Odoo Tech. All rights reserved.

Key Capabilities & Features

  • Fill the quiet hours Price the mid-afternoon, the early evening or the last hour differently, and let the schedule run itself week after week.
  • Nobody has to remember No manager switching a pricelist on at three and off at six, and no discount left running all night because someone forgot.
  • One place to change the hours Move happy hour half an hour later and every rule that uses it moves with it — across every pricelist and every shop.
  • The same price everywhere Because the rule is filtered inside the pricing engine, the website and a quotation quote the same figure the till charges.
  • Fewer arguments at the counter The cashier can see the offer is running and how long is left, so "but the sign says happy hour" has an answer on screen.
  • Late-night rates that work A window crossing midnight is handled properly, so a 22:00 to 02:00 price is a setting rather than a workaround with two rules.
  • Safe to trial Nothing changes until a rule is given a window, and clearing that one field puts the rule back exactly as it was.
  • Nothing extra to run One dependency, no external libraries, no scheduled job driving prices, and no third-party service.
  • Filtered where core filters The window check sits in the same place the standard engine applies the validity period, which is why every caller inherits it instead of each one being patched.
  • One clock, two halves The server converts through the Odoo user's timezone and the till reads the same user timezone in the browser, so they cannot disagree about when a window runs.
  • Inclusive start, exclusive end 15:00 is inside the window and 18:00 is not, so a single moment can never belong to two consecutive windows at once.
  • Fails closed, never open A rule whose window is missing from the till's data is treated as switched off. An archived window is dropped from tills that cached it.
  • Rules cannot be orphaned A window still driving rules cannot be deleted by accident, so a price cannot quietly lose its schedule.
  • Zero cost when unused A rule with no window never reaches the check at all, so an existing database pays nothing for the feature.
  • Download the module and copy the pos_happy_hour_aura folder into your Odoo addons directory.
  • Restart the Odoo service so the new addon is picked up.
  • Enable developer mode, then go to Apps and choose Update Apps List.
  • Search for POS Happy Hour, remove the Apps filter if needed, and click Install.
  • Check that your cashiers' user records have the shop's timezone set, under Settings → Users.
  • Create your first window under Point of Sale → Configuration → Price Windows, then set Time Window on a pricelist rule.
  • Recurring price windows: seven independent weekday switches plus a time range, to the minute, with midnight-crossing support.
  • A Time Window field on pricelist rules, filtered where the engine filters the validity period so every caller obeys it.
  • Live badge in the Point of Sale with minutes remaining, an amber warning state, and start and end notices.
  • Administration: a Price Windows list with a Running column, and a Timed Price Rules list covering every pricelist.
  • Guards against silent no-ops, orphaned rules and archived windows left running on cached tills.
  • Multi-company record rules and access rights: cashiers read, managers configure.
  • 46 automated tests across window logic and the pricing engine, including a regression guard for untimed rules.
  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.

Screenshots & Previews

1 image available
POS Happy Hour | Recurring Time-Based Pricing for Pricelists screenshot 1
Expand Preview
The AuraOdoo Quality Guarantee
100% Tested

Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.

Clean Architecture

Built according to official Odoo guidelines and PEP 8 standards with zero bloat.

Dedicated Support

Free installation assistance and quick bug turnaround from our team.