Fixed-date, holiday, recurring and evergreen timers; a sticky bar across the top or bottom of the\nscreen; WooCommerce product, cart and checkout timers with coupon expiry; and pricing tables whose\nsale prices switch themselves on and off with a timer. Everything described here is included.<\/p>\n\n
One timer engine drives every placement, so you learn it once and put it anywhere: inline in a post,\nin a sticky bar across the top or bottom of the screen, on a WooCommerce product page, in the cart,\nand at checkout.<\/p>\n\n
Fixed date.<\/strong> One real deadline, the same moment for every visitor, in your site's timezone, so a\nsale that ends at midnight ends at your<\/em> midnight.<\/p>\n\n Holiday sales.<\/strong> One timer for your whole sale year. It counts down to each occasion by itself,\nforever, and shows nothing in between.<\/p>\n\n Recurring.<\/strong> Resets on a schedule (hourly, daily, weekly or monthly) for a standing weekly offer.<\/p>\n\n Evergreen.<\/strong> A personal deadline for each visitor, starting when they first arrive and remembered\non their own device. You choose when it appears (straight away, after they have been reading a\nwhile, or when they come back) and whether it ever restarts.<\/p>\n\n Pick Black Friday, Cyber Monday, Christmas, New Year, Valentine's, Easter, Halloween, Boxing Day,\nBack to School or Summer, and the dates are worked out for you every year. That includes the awkward\nones: Easter moves with the lunar calendar, and Black Friday is the day after the fourth Thursday of\nNovember, which is not always the last. A holiday campaign stays correct year after year without you\nediting it.<\/p>\n\n Show a timer on the product page, in the cart and at checkout. Name a coupon and it is applied while\nthe sale window is open and removed again when the window closes, so an ended sale does not keep\ndiscounting. You can also have a dated timer take away the add-to-cart button when it reaches zero,\nso a real deadline really closes the offer. On a site without WooCommerce the store settings simply\nstay switched off.<\/p>\n\n Counter, departure board, dials, meter, precision, statement, neon, odometer, progress ring,\ndraining bar, digital and split flap, in compact or prominent, all responsive. Start from a\nready-made look and adjust it, or set everything yourself: your own colours, a panel behind the\ntimer, corner rounding, spacing, the heading above or below the digits, and your own wording for\nthe unit labels in any language. Everything shows on a live canvas while you set it up, on a mock\nof your own page, so you always see what you are going to get.<\/p>\n\n Place a timer with the block, the Elementor widget, the WPBakery element or the shortcode. Every\none renders through the same code, so they cannot drift apart.<\/p>\n\n One table, two prices. Give any row a sale value beside its everyday one, connect the table to a\ntimer, and the sale prices appear while that timer runs and go back on their own when it ends. No\nduplicate table to build, and nothing to change back on the day.<\/p>\n\n A sale is not always a discount, so every field has its own optional sale version: the price, the\nwording under it, the badge, and what is included. Change only the badge if that is the offer.<\/p>\n\n Buttons can send somebody to a link you choose, add a WooCommerce product to the cart, go straight\nto checkout, or go to checkout with a coupon applied while the sale is on. The table works with no\ntimer attached at all, if a pricing table is all you need.<\/p>\n\n Choose how many tiers, pick a starting look from the carousel, choose its colours, then adjust\nanything you like. Ten looks and ten colour schemes<\/strong>, which is a hundred tables rather than\ntwenty near-identical cards: no two looks are the same shape in another colour, because colour is\nits own control. Each card in the picker shows the real table rather than describing it.<\/p>\n\n Every tier can carry the lines real pricing pages use, each as its own field rather than improvised\nin a badge: a saving like \"50% off\" or \"$39 off\", a per-day equivalent like \"less than a coffee a day\", a\nstrapline under the name, and small print under the button. Each is optional and renders nothing\nwhen empty. The badge itself can sit inside the card, straddle its top edge as a ribbon, hang above\nit as a tab, or run across the corner as a flag, and the recommended tier can take a glow.<\/p>\n\n Underneath, the layout is set by two separate controls rather than one combined list of styles.<\/p>\n\n How the tiers sit together<\/strong>: spaced apart, touching with no gaps, on one continuous sheet\ndivided by hairlines, set wide apart so each stands alone, or with the recommended one drawn taller\nand filled so it stands out of the row.<\/p>\n\n How each card is built<\/strong>: a bordered panel, a filled header band carrying the name and price, no\nbox at all, a coloured spine down the side, a rate card with the price above the name, a price on a\ntab across the corner, or a capped header with a point aimed at the tier.<\/p>\n\n Those two multiply, so the combinations are yours rather than a list somebody wrote out.<\/p>\n\n The panel<\/strong> the table sits on: none, a flat ground, a soft wash, or a dark one that re-cuts its\nown text colours so it stays readable rather than merely going dark.<\/p>\n\n How the price is set.<\/strong> The familiar bold number; a light, wide, quiet register for a brand that\nwould rather state a price than sell one; one large enough to carry a page on its own; or the plan\nname leading with the price small underneath.<\/p>\n\n How the recommended column is marked<\/strong>: a coloured border, a lift, drawn larger, a filled bar\nacross the top, or inverted to a dark ground while the others stay light. Whichever you choose, it\nis also announced to a screen reader, so the recommendation is never carried by colour alone.<\/p>\n\n One accent colour<\/strong> driving the badge, the ticks, the button and the border together, rather than\nfour pickers that can disagree with each other.<\/p>\n\n A price means very little on its own and a great deal beside two others, which is why a pricing\ntable exists at all. Stacking the tiers on a phone means they are read one at a time, and the\ncomparison becomes an act of memory.<\/p>\n\n So there is a third layout for narrow screens. Every tier stays on screen: the one being read takes most of the\nwidth and the others narrow beside it, still showing their name and price, and a tap or a swipe\nopens another. It works with any number of tiers, it is announced properly to a screen reader, and\nif the script never arrives the table falls back to the ordinary stack rather than breaking.\nStacking and sideways swiping are both still there if you prefer them.<\/p>\n\n An evergreen timer is a real per-visitor deadline only if the offer it points to genuinely expires\nfor that visitor. If the price never changes when the timer reaches zero, the timer is not telling\nthe truth, and repeat visitors notice. The plugin gives you the honest configuration; using it\nhonestly is your call.<\/p>\n\n Download every campaign, its style, schedule, expiry action and your bar settings as one file. Keep\nit as a backup before a risky edit, restore it after a reinstall, or upload it on another site to\ncopy a whole season across.<\/p>\n\n\n No. A timer is drawn from data already in your WordPress database, so a countdown never waits on\nanother server and cannot fail because one was unreachable.<\/p><\/dd>\n An evergreen timer's per-device state (when that visitor first saw the timer, and its restart\nbookkeeping) is kept in that visitor's own browser storage. Your campaigns are stored in your\nWordPress database alongside your other settings.<\/p><\/dd>\n No, and this is why the markup ships with no digits in it. The remaining time is worked out in the\nbrowser on every page view, so a fully cached page still shows the correct countdown rather than\nwhatever the number was when the cache was written.<\/p><\/dd>\n They correct themselves too, which matters more, because a stale price is a promise your checkout\nwill not keep. A pricing table ships both its everyday and its sale values, and the browser picks\nthe right ones against the same deadline the timer counts to. So a page cached in the middle of a\nsale stops showing sale prices the moment the sale ends, and a page cached before one starts\nshowing them the moment it begins. You do not need to exclude the page from your cache, and the\nprices do not flash or move on load.<\/p><\/dd>\n You choose per campaign: hide the timer, show a message in its place, or send the visitor to another\npage. A redirect only applies to someone who was watching when it reached zero. Arriving at a page\nwhose timer already finished never redirects you.<\/p><\/dd>\n Yes, and it is part of the free plugin. The bar can carry a message, a live timer and a button, and\nit defaults to a thin strip at the top on phones and the bottom on desktop, both configurable. A\nvisitor can close it, and it stays closed on their device for a week. You can also have the bar step\naside by itself after a few seconds, or slide away while somebody reads and return when they scroll\nback to the top.<\/p>\n\n It can follow the visitor across every page, or only the pages you pick, so a sale that applies to\npart of the shop stays where it belongs. And on a site with accounts you can hide it from anyone\nsigned in: a countdown speaks to somebody still deciding whether to buy, and a member who has\nalready paid reads the same bar as pressure to buy what they already own.<\/p><\/dd>\n Yes. Every timer picks its own placement: a bar across the whole site, or free standing on the pages\nyou choose, where you can also put it on your product pages, the cart and the checkout. The list of\ntimers shows where each one appears, so you can see at a glance which timer is on your bar.<\/p><\/dd>\n Only for the store placements. The inline timers, the block, the builder elements and the sticky bar\nall work on any site. With WooCommerce inactive the store settings are switched off and nothing else\nchanges.<\/p><\/dd>\n The block editor, Elementor, WPBakery and the classic shortcode. One renderer serves all four.<\/p><\/dd>\n\n<\/dl>\n\n\nA built-in holiday calendar<\/h4>\n\n
WooCommerce<\/h4>\n\n
Twelve styles, in every builder<\/h4>\n\n
Pricing tables that follow the sale<\/h4>\n\n
A pricing table that looks like your brand<\/h4>\n\n
Side by side on a phone, not stacked<\/h4>\n\n
Honest about evergreen timers<\/h4>\n\n
Your settings are yours<\/h4>\n\n
\n
Does rendering a timer depend on any external service?<\/h3><\/dt>\n
Where is visitor data stored?<\/h3><\/dt>\n
Will a timer break if a page is cached?<\/h3><\/dt>\n
What about pricing tables on a cached page?<\/h3><\/dt>\n
What happens when a timer reaches zero?<\/h3><\/dt>\n
Can I put a timer in a bar across the screen?<\/h3><\/dt>\n
Can I choose where each timer appears?<\/h3><\/dt>\n
Do I need WooCommerce?<\/h3><\/dt>\n
Which builders are supported?<\/h3><\/dt>\n
1.2.7<\/h4>\n\n
\n
1.2.6<\/h4>\n\n
\n
1.2.5<\/h4>\n\n
\n