What ratato actually does

Pricing periods handle early-bird and late pricing automatically — whichever period covers now is the price a registrant pays, with optional capacity and waitlisting per period. When a period fills, further signups are queued in FIFO order instead of turned away; you promote from the waitlist yourself when a slot opens.

Levels handle same-day distance splits (a 50 km and a 90 km start together) — each with its own pricing and capacity. Add-ons (a T-shirt, a meal ticket) can carry their own option sets, like sizes, each with independent inventory. Discount codes support fixed or percentage amounts, usage caps, and validity windows, and can be tagged with an affiliate name for attribution reporting — see webhooks & integrations below.

A stage race (a 3-day mountain tour, a multi-leg trail event) gets its own stages — each with its own description, distance, date, and GPX route — registrants sign up once for the whole race by default. Results are entered or imported per stage, and ratato computes an overall General Classification automatically.

The rule for handling a missed stage is configurable per event: strict (a registrant must finish every stage to be classified; anyone with a DNF or missing stage shows as NC) or lenient (ranks by the sum of whichever stages they did finish). Both the per-stage results and the computed GC publish to the event's public results page.

Not every stage race needs every entrant for every leg. Flag any stage as open for individual signup with its own price, and registrants can sign up for just that stage instead of the whole event — they still show up in that stage's own results, but are excluded from the overall General Classification, since they didn't attempt every leg.

Bib numbers are assigned automatically at registration. When you're stuffing race envelopes with timing chips, ratato has a rapid entry screen — type or scan a bib, confirm the registrant's name, scan the chip, save, and it resets for the next envelope — plus a bulk CSV import (bib_number, chip_id columns) for pre-assigning a whole batch at once. Either way, a chip already bound to a different registration in the same event is rejected outright.

Results come back the same three ways timing vendors already expect: a CSV export matched by bib, chip ID, registration ID, or email (your choice, per import); manual entry for smaller events; or, for a timing partner that pushes results live as the race happens, a per-event API key your timing vendor posts straight to — generated from the event's results page, shown once, and revocable at any time.

Results pushed through the live API publish immediately — no separate "publish" step — so a leaderboard fed this way updates in near real time.

Configure a webhook URL on any event and ratato notifies it the moment a registration is paid — no polling, no manual CSV export into your CRM or mailing list. Every delivery is signed with a per-event secret, generated once and shown to you, so your receiver can confirm the request actually came from ratato.

A misconfigured or unreachable receiver never blocks or delays the registrant's own confirmation email — delivery failures are logged and swallowed, not retried against your checkout flow.

Running an affiliate or referral program? Tag a discount code with an affiliate name and the discount-codes page shows paid-registration count and revenue per affiliate, so you can reconcile payouts yourself — ratato tracks attribution, not the payout.

Every event gets a subdomain of its own (yourclub.ratato.net), with markdown-driven info pages, a photo gallery, and a route map with elevation profile generated straight from the GPX file you upload — one per level or stage, if the event has more than one route.

Invite staff with owner, admin, or staff roles, scoped to your organization — everyone works from the same registration data, with access matched to what they're responsible for. A full registrations export is available whenever you need one, alongside the reporting views built into the organizer console.