About Firewood v3 - Rollout FAQ
Firewood v3.0 is here!
We're super excited to launch Firewood v3, available to all of our clients this summer.
Firewood v3 replaces our old single‑registration : single-payment checkout with a multi‑item Shopping Cart & Order model, introduces accelerated payment methods (Apple Pay, Google Wallet and Firewood QuickPay for returning customers), delivers fully customizable re-usable registration data collection via Data Templates, and provides increased security with more than 150 security patches and framework upgrades for increased security and performance.
Important Update on Your Data During Platform Migration:
We’re in the process of upgrading to a new version of our platform, and all existing data is being automatically migrated through carefully tested, idempotent scripts during deployment.If you notice that any data appears to be missing, please don’t worry—no data has been lost.
These operations are non-destructive. In some cases, records may simply need to be re-tagged or included in a follow-up backfill. If this happens, just contact our operations team and we’ll take care of it promptly.
Occasionally, you may also see sample data from our demo environment. If you come across anything that looks unfamiliar, please email us at operations@firewoodcamps.com, and our team will clean it up right away.
Thank you for your patience as we make this transition—we’re confident the new platform will bring a smoother and more powerful experience.
Major Differences at a Glance
Firewood Event Registration Platform | v2 | v3 |
Checkout Model | 1 Stripe charge per registration | One Order per cart containing many items |
Payment Methods | Credit/Debit | Credit Cards, Apple Pay, Google Wallet - more payment options and Buy Now + Pay Later coming in Firewood v3.5 this Fall. Apple Pay alone has been shown by Stripe to produce a ~14% revenue uplift |
Data Collection | Static registration form | Data Templates – per‑event, reusable, 58 default datapoints (enterprise and full-school clients can have custom datapoints added per their contracts.) |
Fee Handling | Fee Breakout managed by Firewood | Fee Break‑Out Toggle shows/rolls fees line‑by‑line and can be done using User accounts with the "Account Owner" role |
Roles | 3 core roles | 8 roles with granular flags (view finance, manage attendees, etc.) |
Exports | Background CSV jobs | Instant CSV, filterable, order‑centric |
Security & Infra | N/A for AppSec reasons | More performant database and application layers - over 150 CVE patches |
Accessibility | WCAG AA partial | WCAG AA+ hover states, touch targets |
Inactive Registration Changes | Abandoned registrations were not trackable | Abandoned or pending registrations are now marked as inactive registrations - this will eventually allow for us to help our clients re-engage those potential customers with tooling in v3.5 to maximize conversions (please note: inactive registrations do not take up event spots. Read the link above re: inactive registrations for more details) |
Refund View Changes | Refunds tab shows 1:1 registration:payment refunds / legacy registrations | Refunds tab shows only Orders + v3 refunds. Reporting tab includes v2 + v3 refunds and payments |
Issued via the Admin Registration show page | Issues via the Admin Orders show page | |
Default Exported Attendees | All Attendees including deleted and inactive registrations | Only exports active attendees by default (inactive and deleted registrations are still exportable via the quick csv export button the Admin Event Registrations page) |
Core Checkout & Payment Upgrades
- Shopping Cart & Orders API – customers can now add any mix of registrations, products, bookings; cart persisted across devices
- Fee Break‑Out Toggle – admin‑level switch (→ Account Settings) to surface or absorb Stripe + platform fees
- Firewood QuickPay – reuses saved attendee profiles, cutting average repeat checkout time by roughly 80% for returning customers
- Apple Pay / Google Wallet Support
Registration & Data Collection Upgrades
- Data Templates allow per‑event form variations, toggle required fields from the admin center, enable forced‑recollection for important fields that may be subject to change
- Improved Validation UX – required‑field errors surfaced inline with focus rings.
- Liability Waiver & Refund Policy Assignment – defaults + per‑event overrides.
Admin Experience & Access Control
- Role‑Based Access Control – New roles and more control for account owners to safeguard their business data
- Team Management Hub – centralized add/promote/suspend with duplicate‑prevention.
- Refund Index + Itemized Refunds – full history, per‑line breakdown - please note, the refund tab will only
- Instant CSV & Filtered Exports – one‑click, order‑aware.
- Waitlist Enhancements – date wait‑listed column, bulk invite, inactive attendee insights.
Performance, Security & Infrastructure improvements
- Framework and Platform upgrades - 150+ CVEs patched in 2025 already
- Sidekiq tuning (45 % latency drop), Searchkick async workers, cross‑tenant RSpec isolation.
- Layered persistent backups and fault tolerance
Marketing & Branding Tools
- Branding Panels & Dynamic Event Panels (feature‑flag) – switch between a searchable event list, single-event stacked layout and dual event (2 per row) layouts
- Auto‑resizing email logos, Gmail‑optimized receipts (schema.org cards)
- Rich staff bios with video embeds; social OG tag fixes
Backward Compatibility & Deprecations
- Legacy single‑registration checkout routes redirect to
/cartwith query params preserved. - Old role names aliased to new RBAC until 2026‑03‑31.
- Deprecated endpoints documented in
/api/changelogand will emitDeprecationheader.
V3 Feature Flags
| Feature | Flag | Default |
| QR Codes | beta_qr_codes | Off |
| Branding Panels | branding_panels | Off |
| Product Sales | sell_products | Off |
| Advanced Discounts | discount_engine_v2 | Off |
Glossary
- Order – parent object representing one payment.
- Order Item – links Order → Registration/Product/Booking.
- Data Template – versioned schema of datapoints collected in registration flow.
Next Steps - what's coming in v3.5
- Store Credit - you've asked, we hear you - $0 promo codes are being build now - it's coming.
- Bookings - private bookings build out will be wrapping this fall
- Buy Now + Pay Later
- Firewood.com profiles + Subscription tiers
Client FAQ
Q 1: Why did Firewood change the checkout flow?
Parents often register multiple athletes or buy gear in one sitting. The new shopping‑cart flow lets them pay once instead of repeating the payment screen for every camper, reducing drop‑offs and boosting average order value.
Q 2: What is an “Order” and how does it differ from a registration?
An Order is the single payment. Inside it are Order Items—each ties back to a camp registration, product, or booking. Think of an Order as the receipt and each Order Item as a line on that receipt.
Q 3: Will my historical data be safe?
All v2 registrations, payments, and reports migrate automatically. Nothing is deleted—records are simply grouped under the new Order model for easier reporting (in rare cases, you may have demo data appear in your dashboard, contact operations@firewoodcamps.com or you may be locked out of your account while the migration runs - contact our Ops team if it is time sensitive and they can accelerate your access)
Q 4: Do I have to enable Apple Pay or Google Wallet?
Apple Pay and Google Wallet are both on by default if your Stripe account supports them. If you prefer not to offer these methods, toggle them off in your Stripe dashboard via Payment Settings.
Q 5: Can I pass Stripe and Firewood fees to customers?
Yes. Use the Fee Break‑Out Toggle in Account Settings. ON displays fees as separate lines and adds them to the cart total; OFF absorbs them into your item prices.
Q 6: How do Data Templates help me?
Create a template once—e.g., “Overnight Camp” versus “Day Clinic”—choose which fields are required, and reuse it on any future camp. Instantly build custom registration form flows from scratch.
Q 7: What happens to campers stuck in “Pending” status?
Pending Orders expire after the grace period you set (default 60 min). Until then, their spots are reserved but not counted against capacity. After expiry those spots are released automatically. These will be listed as inactive until a successful payment has been made at Checkout.
Q 8: Where can I find refunds now?
Navigate to Admin Dashboard → Refunds for a full list, or open any admin Order or Legacy Firewood v2 Registration to see line‑item refund details.
Q 9: How do I enable beta features like QR‑code tickets?
Email operations@firewoodcamps.com with the feature name. Most beta features activate instantly—no code deploy needed.
Q 10: I used custom roles in v2. Do I need to redo them?
No. Existing roles map automatically in the new v3 system. You can refine permissions anytime under Admin → Team.
Need more answers? Reach us at support@firewoodcamps.com or browse the v3 help‑center articles below:
