Gorilla Dash

Help Centre

Guides for every part of Gorilla Dash

Step-by-step how-to guides written by the team that builds the product. Read them here, or download any guide as a PDF.

Network Store Orders

Allocations and the Register

Download PDF

Using allocations for anything handed out to named people — conference places, dinner seats, shirts — and working the Register that collects the entries.

Last updated September 2, 2026


Some things you sell need a list of who is getting them. A conference place needs a name and a dietary requirement; a shirt needs a size. An allocation is that list, and the Register is where you work it.

Allocations are set up under Allocations, and the entries appear under Register.

Why they are separate from products

Because several products can fill the same list. A conference might be sold as an early-bird ticket, a standard ticket and a sponsor package — three products, one dinner to cater. Link all three to one "Awards Dinner" allocation and the register gathers every attendee regardless of which product they came through.

It works the other way too: one product can include several allocations, so a conference package that bundles a seat, a dinner and a shirt fills three lists from one purchase.

THE TEST
If you will end up building a spreadsheet of names for it, it is an allocation. If you just need to ship a box, it is not.

Setting one up

  1. Create the allocation and name it as the thing being handed out — "Awards Dinner", "Conference Place", "Polo Shirt".
  2. Add the fields you need against each entry: name, dietary requirement, size, lanyard title.
  3. Link it to the products that grant it, in the product editor.
  4. On those products, turn on Collect fields per unit so each place is asked for its own answers rather than one set for the whole order.
DECIDE THE FIELDS BEFORE YOU SELL ANYTHING
Entries created before you add a field have no answer for it, and you will be chasing those tribes individually. Adding "dietary requirement" the week before the event means emailing everyone who already booked.

Working the Register

The Register lists every entry across the store, one row per place, with who it belongs to and the answers collected.

ColumnWhat it tells you
Organisation and LocationWho the entry belongs to.
Email / ValueThe identifying answer for the entry — usually the attendee or the address.
AllocationWhich list it belongs to.
ProductWhich product granted it.
Production statusWhere it has got to, if the product tracks stages.
BillingWhether the entry is included in the allowance or billable as an extra.
SinceWhen it was added.

Filter by allocation to get one event's list, or by tribe to answer "who did we send?". The Register can be exported, which is what you hand to a caterer, a venue or a uniform supplier.

Adding an entry yourself

Not every place is bought. Head office attendees, speakers and guests can be added to an allocation directly, without going through a product or a payment. They appear in the register and the export alongside everyone else, which is what you want when the caterer needs one number.

Running an event with it

  • Set up the allocation and its fields before the products go live.
  • Watch the register fill as orders come in — it is your live headcount.
  • Add non-buying attendees directly so the numbers are complete.
  • Export near the deadline for the caterer or supplier, filtered to that allocation.
  • Use the entries themselves for name badges and seating; they already hold the answers.
ONE NUMBER, NOT SEVERAL
The value of a shared allocation is that the dinner headcount is one number gathered from every ticket type, rather than a spreadsheet someone merges by hand the week before.
Next · Network Store BillingPayment methods: what tribes can pay with