Package builder
You author packages the way you sell them, one at a time, and the public comparison table is assembled from what they list. There is nothing separate to fill in for the comparison grid: pick “Delegate passes” on Platinum with a value of 10 and on Gold with 4, and the two land on one row of the table.
Open the event → Website → Sponsorship packages.
Rate card — set this once
The rate card sits at the top of the page and applies to the whole event:
- Currency — the one currency every package on this event is quoted in. Pick from the common list or search all currencies. Saving the rate card re-quotes every existing package in the new currency, so the public page can never show Gold in SAR beside Silver in USD.
- Base price (optional) — a single figure the per-package multiples are taken from.
The base price is what makes a rate card a rate card: set it once, price Platinum at three times the base and Gold at two, and a revision means editing one number instead of hunting down every package.
Pricing a package
Each package chooses one of three pricing modes:
| Mode | What it does |
|---|---|
| Fixed price | An absolute figure for this package. |
| Multiple of the base | e.g. 3 for three times the rate card’s base price. The editor previews the resolved amount as you type. |
| No price | The package shows no figure at all. |
A fixed price wins over a multiple — that is the point of the escape hatch, so the one-off package that does not fit the card does not force you to invent a multiplier. A multiple with no base price set in the rate card resolves to no price rather than to a guess, and the editor tells you so.
Term in years (optional) is part of the price, not a footnote: a package priced per year over a three-year term renders as an annual figure with the term stated, because the bare number understates the ask threefold.
Hiding a price without hiding the package
Turn off Show the price on the public page for a package whose price is negotiated. Only the figure goes — the package, its benefits and its remaining slots still render. Use it to show real numbers on the entry tiers and put “enquire” behaviour on Platinum. The admin list marks these Price hidden.
Picking benefits from your catalog
The benefits a package offers are picked from your workspace’s Benefits & add-ons catalog, not typed in per package. Open a package and you get Benefits from your catalog — the whole catalog, each entry with three states:
| State | On the comparison table |
|---|---|
| Not listed | The package says nothing about it — a dash. |
| Included | A tick, or the value you set for this package. |
| Excluded | An explicit cross, next to the packages that have the tick. |
Excluded is the one worth knowing about. “Not listed” and “we deliberately do not give you this” used to look identical to a buyer. Now you can say the second one out loud.
Set the value per package on the entries that carry one — the catalog owns
the benefit’s name and kind, this package owns its number. Picking “Delegate
passes” on Platinum with a value of 10 and on Gold with 4 gives you one row
and two cells.
Renaming reaches everywhere. A package stores the catalog entry’s identity, not its label, so renaming “Delegate passes” in the catalog renames it on every package of every event that picked it. This is the point of the catalog, and it is why the comparison table no longer depends on two packages being typed identically.
A benefit that is not in the catalog yet
Under Benefit not in the catalog? name it, pick its value type (tick only, number, or text), and press Add to catalog and include. The button says what it does: the benefit joins your catalog and is included on this package, so the next package can pick it too. There is no way to attach a benefit that exists nowhere else — a one-off would be the drift the catalog exists to end.
Archived entries stay out of the picker — archiving means “stop offering this” — and a package that already sells one keeps it. If you type the name of an archived benefit into Add to catalog and include, that is a request to offer it again: it comes back rather than dead-ending, and the change is recorded. Typing a name that already exists reuses that entry instead of making a second one.
Add-ons
Add-ons offered with this package works the same way, from the same catalog. The price behaves as follows:
- Leave the price blank to use the catalog price.
- Enter 0 to offer the add-on free with this package.
Those are different statements and stay different end to end. The currency always follows the catalog entry — an override changes the amount, never the denomination.
The benefits builder (free-typed rows)
Each package carries its own benefit rows. A row has three parts:
- Benefit (English) — required. This is also the matching key for the comparison grid (see below).
- Benefit (Arabic) — optional. Leave it blank and the English shows on the Arabic page.
- Value — optional. A number or a short phrase:
10,6×3 m,Full page. Leave it blank and the benefit renders as a plain tick, which is the common case — most benefits are “you get this”, not “you get six of these”.
Reorder rows with the up/down arrows; the public page follows that order. A package holds up to 20 benefits, and the editor shows a live count.
Splitting the value from the label is what makes the comparison work.
Writing “10 delegate passes” as one sentence makes Platinum’s ten and Gold’s
four two unrelated lines that nothing can line up. Writing “Delegate passes”
with a value of 10 and 4 gives you one row and two cells.
The comparison table
The public sponsorship page at /e/<your-event-slug>/sponsor builds its
comparison from the packages themselves:
- Rows come from the benefit itself. Two packages that picked the same catalog entry produce one row by construction — the label is read from the catalog, so there is no string to get wrong. For older free-typed rows the match is still on the English benefit label, case-insensitively.
- A package that picked from the catalog shows its picks; its free-typed rows are the fallback for packages that have not picked yet.
- Row order follows first appearance, walking packages in display order — so the table reads down in the order you authored your top package. A benefit only a cheaper package carries appears after those.
- A package that does not list a benefit gets no cell, rendered as a dash. Absent means “we have not said”; a benefit you picked and marked Excluded renders an explicit cross instead.
- Arabic labels come from the catalog entry for picked benefits. For free-typed rows they come from the first package that filled one in, so one package leaving it blank cannot undo another that translated it.
On phones the table becomes one card per package listing what that package includes — a comparison grid cannot reflow to 360px without hiding the very columns the comparison is for.
Packages you authored earlier
Nothing to re-enter, at either step. A package whose benefits were a plain list opens in the builder as real rows — ticked, with the Arabic column blank — and appears in the public comparison table straight away. Edit it once and you can add values and Arabic labels.
The same applies to the catalog: packages built before it keep their free-typed rows and render exactly as they did. Nothing is migrated behind your back, and a package starts using the catalog the first time you pick from it.
Start from another event
On an event with no packages yet, the rate card offers to copy one. Pick an event under Start from another event and press Copy structure: its packages, their prices, their term and their benefit picks arrive here.
- Everything arrives unpublished, whatever the source said. “We built year two from year one” must not mean year two’s rate card went public on the click.
- Structure only — no sponsors travel. Which company bought Platinum last year is a relationship with that edition, not part of the package.
- The picks stay pointers. A copied package holds the same catalog entries, so renaming a benefit still reaches both editions.
- The card only appears while the rate card is empty. Copy is a starting point, not a merge — on an event that already has packages it refuses: “Nothing copied — this event already has content.”
The agenda has the same offer; see Agenda builder.
Deleting a package
Delete asks first, and names the package. Deleting removes it and its benefits from the public page; sponsorship applications already received keep their record.
Who can do what
Viewing needs the microsite view permission; editing packages and the rate card needs sponsors write. See Team & roles.
Related
- Sponsorship — the application and approval workflow that turns an applicant into a confirmed sponsor.
- Sponsors & exhibitors — managing confirmed sponsors, contracts and booths.