Platform Updates

Repositories: Partners, Partners API, RegoSite and Docs, with an EMS LAN implementation workstream. Status: Local implementation; not deployed.

Event operators can now create SKU-bearing inclusion variations in the Rego tier editor, choose whether variants are alternatives or bundle additions, and configure multiple fixed or random selection groups. Random results are chosen server-side and saved to the registration; check-in shows the allocated variant SKU. The attendee tier chooser shows the promised random/fixed variation quantity without exposing candidate SKUs or manipulating the draw. This local slice supports standard and group registration.

Each variation can also carry its own attendee-facing description, so an alternative design does not need to inherit misleading base-item copy.

The editor separates fixed quantities from random draw counts and displays the resolved component-unit total per attendee before the draft is applied. This makes a bundle versus alternative choice auditable without treating a fixed selection as a random draw.

Inventory reservations, historical offer snapshots, public Rego presentation, and the remaining registration lifecycles are still under development. EMS LAN now accepts the versioned variation snapshot capability, retains allocated fixed/random SKU outcomes in the claimable local checklist, and rejects an unknown capability before it can replace an event. A local EMS authoring modal was rendered with an independent variation SKU after a same-host development-session fix. Partners and Rego typecheck/build plus the API typecheck and dry-run build passed locally. Deployment and persistent database migration rehearsal remain pending approval.

Fixed variation groups now include every selected SKU, while random groups use their configured draw count and optional repeat policy. A local rollback-only database check confirmed fixed, distinct random, repeat-enabled random, and retry-safe outcomes. This is local certification evidence only; no database migration or deployment was applied.

Variation SKU identity is now checked case-insensitively in the pending schema, and saved registration or Dealer Den allocation snapshots cannot be rewritten by later catalog edits. The corresponding local rollback fixture passed; this does not yet constitute a deployed database migration or live-event evidence.

The EMS editor now saves the dependent inclusion, variation, tier-link, and selection-group graph through one revision-checked database transaction rather than sequencing inclusion and tier writes. A stale editor must reload instead of producing a half-updated offering; no existing event catalog was changed during local verification.

For a paid attendee whose first payment account cannot accept the original amount, coupon and affiliate inputs are available before account validation. This lets the API reprice the registration and avoids trapping a valid zero-total or lower-total registration behind an over-limit account.

Older catalog clients that do not understand inclusion variations are now asked to reload instead of being allowed to overwrite or archive variation settings.

When fulfilment starts, the saved variation allocation identity now travels with the check-in item and its retry-safe claim receipt, including in EMS LAN snapshots. This protects the SKU history behind a repeated claim attempt.

That receipt also records the handout against the variation’s own inventory identity, so SKU-level fulfilment reports do not collapse it into the base item.

For variations with tracked event stock, new registrations and Dealer Den slots now reserve only available SKU units; an unavailable full set is rejected rather than partially promised. This remains locally certified pending migration and deployment approval.

If an event operator later makes a required variation unavailable, a new registration now fails instead of silently receiving only part of its configured variation set. The registration draft remains recoverable and no partial local allocation is retained.

For tote-bag-style random pools, a selected fixed design is now kept out of the random draw. Separate no-repeat random groups also avoid a design already drawn for that inclusion, while an explicitly repeat-enabled group can still produce more than one of the same random design.

Dealer Den registration slots now use the same server-side variation allocation rule as ordinary registrations. If any slot cannot receive its configured item, the new Dealer Den registration is not retained. Inventory demand includes the slot’s allocated SKU instead of its alternative base item.

Check-in staff can now see the saved SKU-labelled Dealer Den variation in the slot’s fulfilment list. This makes handout decisions use the allocated design, not the generic inclusion name.

An attendee upgrade now keeps their existing saved variation outcome and only allocates newly introduced target-tier variations. If a required target design is unavailable, the upgrade leaves their original registration unchanged.

Gift purchase and a live waitlist offer now also lock the exact inclusion variation SKU before the receiver finishes registration. Redeeming the gift or accepting the offer materializes that saved outcome instead of running a new random draw; expired, declined, converted, or rejected deferred offers no longer reserve an unclaimed SKU. Local rollback checks covered both paths and the API lifecycle/type checks passed. This remains unpublished and is not hosted-release evidence.

Check-in corrections can now return a specific number of already handed-out units instead of treating a multi-unit SKU line as all-or-nothing. Each return remains an immutable inventory correction against its original claim receipt, so the SKU audit trail and stock analytics remain intact. This has local browser, API, and rollback-database evidence only; it is not deployed.

Group-order review now shows each attendee’s fixed or random inclusion promise using the same safe wording as ordinary registration. It does not disclose candidate SKU pools or reroll a randomized design while a group is reviewed.

The associated schema is also installed in the local development database for end-to-end local work. It remains unpublished to hosted infrastructure.

Repository: partners.furries.ph. Status: Local implementation verified; hosted deployment pending.

What’s Changed

The RegoSite-derived attendee preview in Event Management now includes the same add-on step as the attendee registration flow. It filters add-ons by the selected tier, shows configured artwork and pricing, collects add-on-specific questions, validates required answers, and carries chosen extras into review.

Impact

Event teams can verify the complete registration draft, including optional extras, before saving. Preview actions remain local and do not reserve capacity, change inventory, create payments, or submit attendee data.

Upgrade Notes

Partners TypeScript checks passed locally. Deploy Partners before expecting this corrected preview in the hosted dashboard.

Repository: partners.furries.ph. Status: Local implementation verified; hosted deployment pending.

What’s Changed

The Event Management registration preview now mounts the copied RegoSite registration-wizard presentation instead of a dashboard-specific approximation. Tier selection, attendee-detail steps, question rendering, Conditions confirmation, review, and navigation use the same structure as the attendee-facing flow while preview commands remain local.

Impact

Event teams can review an unpublished registration draft in Partners without comparing it to a visually different dashboard mock. The preview cannot create registrations, capacity holds, payments, uploaded files, or attendee answers.

Upgrade Notes

Type checking passed locally. Deploy Partners before relying on the changed preview in the hosted dashboard.

Repository: partners.furries.ph. Status: Local implementation verified; hosted deployment pending.

What’s Changed

Opening the Partners sign-in entry now checks an existing dashboard session with the platform before choosing the sign-in screen or continuing to the requested dashboard page. Expired or invalid sessions show the normal sign-in flow; recovery and invitation links retain their dedicated handling.

Impact

Returning partners no longer need to sign in again just because they opened the dashboard entry page. Operators should continue to the dashboard after the short session check.

Upgrade Notes

The redirect contract and TypeScript checks passed locally. Deploy Partners for the updated entry behavior to reach the hosted dashboard.

Repositories: partners.furries.ph and partners-api. Status: Local implementation verified; API deployment pending.

What’s Changed

Event email composers now include Saved prefill users as an audience option. It contains people with an active, saved registration prefill for that event; revoked prefills are excluded. The Everyone audience includes this group and still removes duplicate contacts.

Impact

Organizers can now send an event email directly to people who started and saved a registration draft, including people who have not yet completed a registration or joined a waitlist. Account-level announcement choices continue to be honored.

Upgrade Notes

Partners and API email-audience checks cover the new group. Deploy Partners API before using the option in the hosted composer.

Repository: partners.furries.ph (API database migrations). Status: Database correction published; hosted transaction verification passed.

What’s Changed

The reservation service now checks the current attendee identity records. A recent hold-duration update had reintroduced a retired account-table lookup, causing registration starts to return a temporary-unavailability error.

Impact

Affected attendees can retry starting registration. Existing capacity limits, attendee ownership, five-to-ten-minute hold durations, and retry deadlines remain unchanged.

Upgrade Notes

The focused correction is published. Hosted reservation creation and retry passed in rolled-back transactions that left no test reservation behind. Local database regression checks also passed, including access restrictions and hold durations. A signed-in browser retry remains the final attendee-facing check; no frontend release is required for this correction.

Repository: rego.furries.ph. Status: Local implementation verified; hosted release pending.

What’s Changed

Opening a standard registration page without the verified event-entry handoff now shows a full-screen recovery dialog. Its only action returns the attendee to the event page, where Start registration begins a new verified request. The same recovery action is used when a held registration slot expires.

Impact

Attendees cannot keep editing an unverified or expired registration checkout. They are returned to the event page to obtain a current verification grant and live capacity hold before making choices.

Upgrade Notes

Rego type checking and the isolated mobile/desktop registration fixture cover both missing-grant and expired-hold recovery dialogs, including the forced return action. Deploy RegoSite before this behavior is available to attendees.

Repository: rego.furries.ph. Status: Local implementation verified; hosted release pending.

What’s Changed

For every paid registration, the payment reference and uploaded receipt are now both mandatory before the attendee can continue from the payment screen. The Continue button stays unavailable until the reference is present and the receipt upload finishes.

Impact

Paid registrations reach review only with the payment evidence needed by event staff. The existing API submission check continues to reject a missing reference or receipt.

Upgrade Notes

Rego type checking and the payment-handoff fixture cover the locked, reference-only, and completed-receipt states. Deploy RegoSite before attendees receive this requirement.

Repository: rego.furries.ph. Status: Local implementation verified; hosted release pending.

What’s Changed

Continue controls now remain unavailable while their visible required fields are incomplete. This applies to standard and gift registration payment evidence, Dealers Den payment handoffs and applications, activity proposals, and volunteer applications. Each transition also validates again before changing steps.

Impact

Attendees cannot reach review or submission with missing required answers, a missing payment reference, or an absent receipt. Optional, conditional, and free-flow fields remain unaffected.

Upgrade Notes

Rego type checking and required-step fixture coverage verify disabled controls and transition-time checks. Deploy RegoSite before this behavior is available to attendees.

Repository: rego.furries.ph. Status: Local implementation verified; hosted release pending.

What’s Changed

All attendee-facing price summaries now combine platform and payment-processing charges into one Fees line. Registration, group registration, gifts, Dealers Den, shop, upgrades, receipts, transaction details, item previews, and guide examples use the same presentation.

Impact

Attendees see the final combined charge without needing to reconcile two technical fee categories. Totals and API-owned fee calculations are unchanged.

Upgrade Notes

Rego type checking and commerce fixtures cover the combined fees presentation. Deploy RegoSite before the updated labels are visible to attendees.