# Early bird without the busywork: let the price change itself — MijnEvent [Home](https://mijnevent.nl/en) / [Blog for event organizers](https://mijnevent.nl/en/blog) / Early bird without the busywork: let the price change itself tickets pricing dashboard # Early bird without the busywork: let the price change itself New: price periods per ticket type. Give your super early bird a name, a window and a discount — the price switches automatically. No separate ticket types, no manually moving leftover stock. [Jasper Koers](https://mijnevent.nl/en/author/jasper-koers) · 21 July 2026 · 6 min read In short - A single ticket type can now carry several named price periods — you choose the name, for example 'Super Early Bird' or 'Presale'. - The price switches automatically at the date and time you set; outside every period your regular price applies. - Capacity stays one pool: never again move the leftovers of an expired promotion to another ticket type by hand. Early bird pricing is the oldest trick in the events business, and it still works: whoever books early pays less, and you get certainty about attendance and cash flow sooner. But in most ticketing systems it is an administrative chore. Not anymore. # The problem: the ticket does not change, only the price Here is how it used to go. You have 1,000 tickets. You create an "Early Bird" ticket type with 80 seats at € 22.50 and a "Regular" type with 920 seats at € 25.00. The promotion ends on 20 August. And then the manual work begins: - deactivate the early bird, otherwise it stays on sale; - check how many actually sold — 20 out of 80; - work out that 60 tickets are left over; - add those 60 to "Regular", so you still sell 1,000 tickets in total. Forget that step and you sell 60 tickets too few. Miscount and you oversell. All of this while nothing about the ticket itself changed: same access, same spot, same night. Only the price was different for a while. # The fix: price periods on one ticket type Every ticket type in the dashboard now has a **Price periods** block. You give a period a **name you choose yourself**, a **start and end date** and a **discount or fixed price**: ![The Price periods form with two periods: Super Early Bird at 25% and Early Bird at 15%, with a live price preview](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/inline/prijsperiodes-modal.webp)*Two periods under the same ticket type. Below each one you immediately see what the visitor will pay.* You can pick a **percentage** (25% off the base price) or a **fixed price** (during this period the ticket costs € 18.00). Each row shows the result right away: *€ 9.00 → € 6.75 during this period*. No mental arithmetic to check whether your discount lands on a tidy amount. Chaining is fine: super early bird until mid-June, early bird until 20 August, regular price after that. Overlapping is not allowed — it would be unclear which price applies — and you get a clear message if it happens. # And then it runs itself This is the entire point: **once it is set up, you do nothing.** At midnight on the end date the promotion stops and the next price takes over. No ticket type to deactivate, no numbers to move, no alarm on your phone. The dashboard list shows at a glance which promotion is running: a badge on the ticket type and the promotional price with the regular one struck through beside it. ![The ticket types list showing the 'Early Bird active' badge and the struck-through regular price](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/inline/prijsperiodes-beheer-lijst.webp)*Two ticket types in the promotion, two at the regular price — visible straight from the list.* # What the visitor sees Your event page makes the promotion visible too, because a discount nobody notices earns you nothing. The ticket type shows your promotion name as a label, the old price struck through next to the new one, and the deadline — including what the ticket will cost afterwards: ![The event page with an Early Bird label, struck-through price and the line 'until 20 August · then € 9.00'](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/inline/prijsperiodes-shop.webp)*"Until 20 August · then € 9.00" — the visitor knows exactly where they stand.* That last line does more work than you would think. A visitor who knows the ticket gets more expensive next week is far less likely to postpone the decision. And because you pick the name yourself, it fits your event: "Early Riser", "Neighbourhood rate", "Members presale" — whatever you like. Everyone who cannot see the layout gets it read out as well: screen readers receive the full sentence "regular price € 9.00, now € 7.65 during Early Bird, valid until 20 August" instead of two loose amounts. [Accessibility](/en/accessibility) is not an afterthought here. # The fine print that is already handled - **Your capacity stays one pool.** That is the core of it: no separate stock levels to keep track of. - **An order in progress keeps its price.** The price is locked in when the order is created. If the period ends while someone is paying, their amount does not change. - **The order records which promotion applied.** Even if you rename or delete the period later, the old order still says it was a "Super Early Bird" — useful for your bookkeeping and your [statistics](/en/blog/statistics-and-csv-export). - **Discount codes stack.** A [discount code](/en/blog/create-discount-codes) is calculated over the price that applies at that moment. - **Free stays fee-free.** Set a period to 100% off and the ticket is free during that window — and MijnEvent never charges a platform fee on free tickets. # Common in running, rare in ticketing A curious detail: sign up for a marathon and a fee that rises per period is entirely normal. Endurance-sport registration platforms — Atleta, for one — have had it for years: several rates on a single registration that hand over to each other automatically once a date passes. In ticketing it never became common practice, for reasons nobody can quite explain. We checked 37 platforms: the entire Dutch self-service segment solves early bird with a separate ticket type and its own stock. Where it is possible, it usually hides inside a discount campaign or a pricing formula, or sits behind an enterprise plan. We felt the organiser of a village festival has just as much right to it as an arena — so with us it lives on the ticket type itself, in every plan. # When should you use this? A ladder of two or three periods works best for events that sell far in advance: festivals, parades, multi-day conferences. For a smaller event with a short sales window one early bird is usually enough — for instance the first two weeks after the announcement, when attention is highest anyway. It works in reverse too: set a period to a *fixed price higher* than your base price and you have a last-minute surcharge for the final week. Same control, opposite direction. No event set up yet? Start with [creating your first event](/en/blog/creating-your-first-event) — price periods are included in every plan, [pay as you go](/en/pricing) included. Frequently asked questions ## Frequently asked questions ## Do I still need a separate ticket type for an early bird? No, and that is the whole point. You create one ticket type at your regular price and hang price periods underneath it. The ticket itself does not change — only what the visitor pays for it. ## What happens to the remaining tickets when the early bird ends? Nothing — they stay in the same pool. If you sold 20 of 80 during the promotion, 60 are still available afterwards at the regular price. There is nothing to top up or move. ## What if someone is checking out exactly when the deadline passes? The price is locked in the moment the order is created. An order already in progress keeps its price; nothing changes underneath the buyer. ## Can I run several promotions back to back? Yes. Super early bird, early bird and then the regular price is a common ladder. Periods may not overlap — the system warns you if they accidentally do. ## Does a discount code still stack on top of the promotional price? Yes. A discount code is calculated over the price that applies at that moment, so over the promotional price. [ Back to blog ](https://mijnevent.nl/en/blog) MijnEvent ## Read more [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/automatic-membership-renewal-dutch-law.webp) memberships Jasper Koers · 27 July 2026 · 6 min read ## Automatic membership renewal: collecting fees within Dutch renewal law Automatic renewal saves your club a pile of chasing work, but the law has rules about cancelling. Here is how renewal works in MijnEvent, and how to keep it clean. ](https://mijnevent.nl/en/blog/automatic-membership-renewal-dutch-law) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/ontruimingsverslag-evenement-bewijsstuk.webp) safety MijnEvent · 27 July 2026 · 5 min read ## The evacuation record: why the day after your event matters for the next permit An evacuation — real or drilled — is only finished once it is on paper. What belongs in an evacuation record, why the municipality asks for it, and how to make the record write itself instead of reconstructing it afterwards? ](https://mijnevent.nl/en/blog/evacuation-record-event-evidence) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/knmi-weeralerts-veiligheidsplan.webp) safety MijnEvent · 27 July 2026 · 3 min read ## Weather monitoring in your safety plan: how KNMI warnings land in your alerts and logbook automatically Almost every safety-plan format has a 'weather monitoring' section — and almost nobody fills it in concretely. The Safety & Permit module pulls the KNMI warning code for your event location every hour and turns it into a demonstrable process. ](https://mijnevent.nl/en/blog/knmi-weather-alerts-event-safety-plan) MijnEvent ## Ready to get started? Create a free account and sell your first tickets today. [Start free](https://mijnevent.nl/registreer) [Pricing](https://mijnevent.nl/en/pricing)