Apply batch or bulk updates to multiple events

This help document describes the Events Bulk Update tool in the Corsizio manager dashboard. It explains what the tool can do, how to use it, and what its limits are.

Table of contents:

1. What this feature is
2. Important prerequisite: know the event settings first
3. Access and permissions
4. Step-by-step: how to get there and use it
5. Actions available per type of setting
6. Automatic behavior to be aware of
7. Full list of settings that can be changed
8. Restrictions and limitations
9. Common questions

1. What the feature is

The bulk update tool lets an account user change the same setting (or a set of settings) across many events at once, without opening and editing each event one by one.

It works in three steps on a single page:

1. Filter the list of events you want to work with.
2. Configure one or more changes ("setups") that should be applied to those events.
3. Review the exact before/after result calculated for every event, and submit the events you want to update.

Nothing is saved until you press Submit Changes on an individual event card. The tool always shows you a preview of what would change on each event before anything is written.

When to use it

Typical situations:

• Seasonal price adjustments — increase all prices by 10%, or set a new price on all "Adult" price categories for the upcoming term.
• Schedule shifts — push a series of events out by 7 days, or move all registration close dates 2 days later.
• Publishing a whole term — set the published status of a filtered group of events at once.
• Re-assigning people or places — swap an instructor across many events, or change the location of a whole series.
• Turning features on/off in bulk — enable waiting lists, enable/disable offline payments, enable feedback emails, hide events from the portal site.
• Renaming a series — append, prepend, or find-and-replace text within the event names (e.g. replace "Spring 2026" with "Fall 2026").
• Notification housekeeping — replace a staff member's email in the notification recipients of many events.
• Tidying add-ons and early-bird pricing across a group of events.

When not to use it

• When you need to change something that is not in the supported settings list (see section 7) — for example the event description, cover photo, custom form fields, or the dates breakdown. Those must be edited on the event itself.
• When only one or two events are involved — editing them directly is faster and safer.
• When the events differ so much from each other that a single rule does not fit all of them. The tool applies the same setup to every event you submit, and it can only be reviewed per event.

2. Important prerequisite: know the event settings first

The bulk update tool changes the same settings that exist in the event creation/edit form — it does not explain them.

Each setting in the bulk tool has only a short one-line description. The full meaning, dependencies, and consequences of every event setting are documented in the event creation flow and in different help docs.

Before using bulk updates, you should already be comfortable with the event form, in particular:

• How pricing works (price categories, variable amounts, discountable flags, early-bird price and date).
• How add-on items work (required, variable, discountable, limited units, quantity).
• How spots, waiting list, and their enable flags relate to each other.
• How registration open/close dates relate to the event start and end dates.
• How payment options (online, offline, deposit) and their "before" dates behave.
• How reminder, feedback, and notification emails are triggered.

If you are unsure what a setting does, you should look at that setting on a single event first, verify the outcome there, and only then apply it in bulk.

3. Access and permissions

• Where: manager dashboard → Events list.
• Who: only account users with the Admin or Editor role. Viewers and facilitators cannot use it. (Account owners have admin-level access.)
• Feature availability: the "Bulk updates" menu item and toolbar button only appear when the bulk update feature is enabled for the account. If a customer cannot see the option at all, the feature is not enabled on their account — this is not a browser or permission problem on their side.
• Divisions: if the account uses divisions, an editor can only load and update events that belong to a division they have access to. A submit will be rejected with a permission message if the event is outside their divisions.
• Terminology may differ per account. If the account renamed "Events" to "Classes" or "Attendees" to "Participants", the labels in the tool follow that naming.

4. Step-by-step: how to get there and use it

Getting to the tool

1. Open the Events list area of the manager dashboard.
2. In the toolbar at the top, click the Bulk updates button, or open the Actions dropdown and choose Bulk update multiple events.
3. The bulk update page opens with three numbered sections (STEP 1, STEP 2, STEP 3).

Use the Exit button (top right or bottom right) to leave. If any change setups are configured, an "Exit now? Are you sure?" confirmation is shown, because setups are not saved when leaving the page.

STEP 1 — Select and apply filters

This step decides which events appear in the list below. It does not change anything.

Available filters:

After adjusting filters, click Apply Filters. The card is outlined in amber and shows "Filters changed and need to be applied" until you do. Reset returns to the default filters.

The list loads 50 events at a time; use Load more at the bottom to append the next batch. When the end is reached, a note says so and suggests changing the filters to see a different set.

The filters carry over the selection that was last used on the main Events list, so the bulk page usually opens on a familiar set of events.

STEP 2 — Configure and apply a set of changes

This is where the actual change rules ("setups") are built. Each setup is one instruction, such as Increase "Price: Amount" for all price categories by 10%.

To add a setup:

1. Select a setting — start typing in the search box. It matches both the setting name and its description, so typing "waiting", "early", "deposit", or "portal" narrows the list quickly. Each entry shows an icon for its value type and its one-line description.
2. Apply to (only for price categories and add-on items) — choose whether the change targets all items of the list, a specific position (#1 through #6), or all items whose label matches exactly (case-insensitive) a label you type.
3. Select an action — the available actions depend on the type of the setting (see section 5).
4. Enter the value — a text box, number/amount box, date picker, dropdown, or recipient selector, depending on the setting. Some actions ask for an extra field (e.g. Replace asks for the original text to look for; Add/Subtract on a date asks for the unit).
5. Click Apply Setup. The setup is added to the numbered list at the top of the card, and the preview in STEP 3 is recalculated immediately.

Managing the list of setups:

• Use Insert a new setup item to add another one. There is no limit on how many you add.
• Setups run in the order they are listed (#1, then #2, …), each building on the result of the previous one. Use the up/down arrows to reorder them, and the × to remove one.
• The same setting can be set up more than once — for example subtract 5 and then add 2 — and the results combine into a single final change.
• Clear removes all setups and starts over.
• If a setup automatically brings another setting along with it, a grey hint below it says so (e.g. Also sets "Limited Spots: Enabled" on the events that need it). See section 6.

STEP 3 — Submit changes to the desired events

The header bar of this step summarizes: the total number of items in the filtered list, how many items have changes, and how many items were left out (blocked by a rule).

Each event is shown as a card with:

• Its status tag (published / registration state), a Has Dates Breakdown tag when applicable, and the attendee count.
• Name, date range, location, price categories, and add-on items.
• Links to Manage details (opens the event in a new tab) and View public page.
• The calculated list of changes in the footer, each line showing the setup number(s) it came from (#1    , #1 #3    , or auto    ), the setting label, the old value struck through, and the new value.
• Price and add-on changes are shown as one entry with a per-item breakdown so each affected category is reviewable on its own line.

To apply the changes to that event, click Submit Changes on its card. On success the footer shows "Changes were applied successfully!". If the system rejects it, a red error message appears on the card and that card cannot be resubmitted without recalculating (change a setup or apply filters again).

Events where the setups make no difference simply show "No changes to apply".

5. Actions available per type of setting

Which actions appear depends on the kind of value the setting holds.

Notes that apply to all types:

• Required settings do not offer "Clear" — an event must always keep a name, a status, a start and end date, and so on.
• A setup that would not actually change anything on a given event is silently dropped for that event (it shows "No changes to apply" rather than a no-op line).
• Setups that cancel each other out (e.g. add 5 then subtract 5) also produce no change.

6. Automatic behavior to be aware of

Settings that follow along ("auto" lines)

Some values only take effect once their enabling flag is on. To avoid silently useless changes, the tool turns those flags on automatically when needed. These lines appear in the preview tagged auto:

These flags are only ever switched on, never off, and only on events that actually need it. If you configured that same flag yourself in a setup, your own setup always wins.

Dates that shift with the start date

When Start Date & Time is changed, the same shift in duration is applied automatically to the event's related dates, shown as auto lines:

• Registration Open Date & Time
• Registration Close Date & Time
• Offline Payments: Before Date
• Deposit Payments: Before Date
• Reminder Emails: Date & Time
• Attendee Self-Serve: Allowed Before Date
• The early-bird "until" date of each price category

The End Date & Time is not shifted automatically. If a series is being moved, add a second setup that applies the same shift to the End Date & Time.

A date you configured explicitly in a setup is never overwritten by this automatic shift.

Price and add-on list rules

When price categories or add-on items are changed, the resulting list is kept valid the same way the event form does:

• A price or add-on with Variable Amount enabled is forced to non-discountable, and its early-bird options are turned off.
• At least one price category must remain enabled — if a setup would disable all of them, the first one stays enabled.
• An add-on with an empty label becomes "Unlabeled item", and an empty price becomes 0.
• Add-on inventory counts of units already sold are always preserved by the system, whatever the setup does.

Changes that are left out (blocked)

If a change cannot be safely made to a particular event, it is listed on the card in amber as "… was left out" with the reason, and it is never submitted. Currently this happens for:

• Changes to Start Date & Time / End Date & Time on events that have a dates breakdown. The breakdown is a manually curated agenda of individual sessions; moving the main dates would leave it out of sync. Those events must have their dates changed individually so the breakdown can also be adjusted with them. Events with a breakdown are marked with a Has Dates Breakdown tag.

All other setups on the same event are still applied normally — only the blocked one is skipped.

7. Full list of settings that can be changed

Main details

Registration

Payment

Pricing (price categories)

These target one or more price categories of each event — all of them, a position (#1–#6), or all categories with an exact label.

Add-ons

These target one or more add-on items of each event — all of them, a position (#1–#6), or all items with an exact label.

Communication and configuration

Settings tied to an account feature that is turned off (divisions, categories, age groups, genders, levels, account-wide price hiding) do not appear in the settings list at all.

8. Restrictions and limitations

Scope of the tool

• Only the settings listed in section 7 can be changed. Not available in bulk: event description, cover photo/video, virtual meeting info, custom form fields, dates breakdown items, time zone, language, minimum spots, waiting list automatic conversion and messages, registration restrictions (email domains, passcodes), volume discount tiers, coupon assignments, custom email message content, payment reminder settings, and certificate settings. Those are edited on the individual event.
• Items in lists are never added or removed. Price categories and add-on items can only be modified where they already exist. An event with no price categories is unaffected by price setups; a position target of #3 does nothing on an event that has only two categories.
• Position targeting covers the first 6 items of a price or add-on list. Beyond that, target by label or by "all".
• Label targeting is an exact match (letter case ignored). A typo or partial label matches nothing and results in no change for that event.

Applying and saving

• Events are submitted one at a time. There is no "apply to all" action — each card is confirmed individually.
• There is no undo. Once submitted, the change is saved to the event. Every bulk change is recorded in the account activity trail (tagged as a bulk update), but reverting means applying an opposite change.
• Setups are not saved. Leaving the page (Exit, navigation, refresh) discards the configured setups. A confirmation prompt appears first.
• Events that ended long ago cannot be updated. An event that has registrations and ended more than 30 days ago is rejected on submit with a message suggesting to clone it into a new event instead.
• Archived events are only in the list when the Archived status filter is chosen.
• Divisions: editors can only submit events within their divisions. Changing an event's divisions also updates the divisions of that event's attendees and memos.
• Waiting list processing: changing the spots maximum or the waiting list settings can trigger the automatic waiting list conversion flow on that event if it is enabled.
• Integrations (Zapier and similar) receive the normal "event updated" signal for every submitted event, the same as a manual edit.

Value handling

• Amounts never go below zero; percentage increases/decreases are calculated per event from that event's own current value, and results are rounded to 2 decimals.
• Text is trimmed and cut to the field's character limit.
• Whole-number fields are rounded; field minimums and maximums are enforced (for example spots and waiting list maximums are capped at 1000).
• The list of events loads 50 at a time — use Load more to reach the rest, or tighten the filters.

9. Common questions

"I don't see the Bulk updates button."

The feature is not enabled for that account, or the user is not an admin/editor. Contact Corsizio support to have the feature enabled.

"Nothing shows under my changes for some events."

The setup produces no difference for those events — the value is already what the setup would set, or the setting has nothing to act on (e.g. no price categories, or an empty date being shifted).

"My change says it was left out."

A rule blocked it for that specific event. Today this only happens for start/end date changes on events that have a dates breakdown. Edit those events individually.

"I moved the start dates but the end dates stayed."

Correct — the end date is deliberately not shifted automatically. Add a second setup applying the same shift to the End Date & Time.

"Why did another setting change on its own?"

Lines tagged auto are dependent flags the tool turns on so your value takes effect (see section 6), or dates shifted along with the start date.

"Can I undo a bulk update?"

No automatic undo exists. Apply an opposite change, or edit the affected events directly.

"Can I apply it to all events with one click?"

No. Submission is per event by design, so the calculated result is confirmed before each event is saved.