An event product type gives WooCommerce a reusable structure for workshops, seminars, conferences, and other paid events. Editors maintain venue, organizer, date, duration, format, and preparation details in one place, while customers receive a consistent event purchase page.
This guide uses a WooCommerce Workshop example built with Custom Product Type for WooCommerce.
Define the event offer before the fields
A workshop page should answer who it serves, what attendees will learn, when and where it happens, what preparation is required, and what is included. The description sells the learning outcome; Event Details carries the repeated facts.
Plan the event model
| Information | Structure |
|---|---|
| Organizer, venue, duration, format | Event Details fields |
| Event topic hierarchy | Custom taxonomy |
| Attendee name or note | Customer input |
| Supporting document | File upload when required |
| Fixed ticket versions with commercial differences | Appropriate purchasable-version layer |
Keep customer data outside the reusable Event record. Attendee names and submitted notes belong to the individual purchase.
Step 1: Create Event and Events
- Go to WooCommerce > Product Types > Add New.
- Enter Event and Events as the labels.
- Select an available product-page layout, or keep the default WooCommerce layout.
- Enable Custom Taxonomy for Workshops, Conferences, and Webinars when needed.
- Choose whether events appear in the main shop.
- Add an Event badge when it helps recognition in listings.
Step 2: Create the Event Details tab
Enable Back-end Fields > Admin Fields and label the tab Event Details.
| Field | Type | Example |
|---|---|---|
| Organizer | Text | WPSAAD |
| Event Date | Text | September 15, 2026 |
| Duration | Text | Four hours |
| Format | Select | Online |
| Recording Included | Checkbox | Yes |
| Preparation | Textarea | Bring a staging WooCommerce website |
| Included Sessions | Number | 3 |
Step 3: Build a scannable event page
Enable Show In Front for date, duration, format, organizer, preparation, and included sessions. Place essential details before Add to Cart or in the Single Product Summary. Use Product Meta positions for secondary references.
The description should focus on the outcome, agenda, audience, and speaker value. Structured fields should answer the practical questions.
Build the event page in decision order
- State the workshop outcome and intended audience.
- Present the agenda and organizer credibility.
- Show date, duration, format, and preparation.
- Present price and the purchase action.
- Collect only required attendee information.
This order prevents the registration controls from appearing before customers understand the event.
Step 4: Add attendee inputs
- Attendee name or business details through customer text.
- Session preference through a dropdown or checkbox.
- Required document through file upload.
- Additional attendee note where it supports preparation.
These controls collect customer information. Capacity, seat inventory, ticket validation, and scheduling rules require their own verified operational behavior and should not be inferred from the product model.
Use versions only for real ticket offers
Standard and Premium can be purchasable versions when they have different prices or included value. An attendee note is not a ticket version. A workshop format shown as a stable event fact is not automatically a variation.
Keep the Event type focused on the shared event model and use the appropriate commercial layer for genuine ticket versions.
Step 5: Create the first workshop
- Add the workshop title and clear outcome.
- Explain the agenda and intended audience.
- Add price and a relevant event image.
- Mark the event Virtual when appropriate.
- Select Event as the product type.
- Complete Event Details.
- Preview the page and attendee inputs on desktop and mobile.
Use one event publishing checklist
- Date, duration, timezone, and format are clear.
- Organizer and audience are identified.
- Agenda and outcomes are specific.
- Preparation and included materials are visible.
- Customer inputs are limited to necessary details.
- The purchase action follows the essential event facts.
A reusable Event model reduces omissions and gives every workshop the same professional information standard.
Final event QA checklist
- The title and introduction communicate a specific outcome.
- Date, duration, format, and organizer are complete.
- The Event Details tab separates public and private values.
- Attendee inputs are limited to necessary information.
- Ticket versions represent real commercial differences.
- Desktop and mobile pages remain easy to scan.
Repeat the test with an online event and an in-person event. The shared Event model should remain useful while format-specific values and attendee inputs change without confusing editors or customers.
Document the final event publishing workflow.
Use the custom field guide to refine Event Details and the booking product guide when customer date selection is part of the offer.
Frequently asked questions
Which event details belong in product fields?
Organizer, date, venue or format, duration, preparation, and included materials are stable event information.
Should attendee names be product fields?
No. Attendee details are customer input for an individual purchase.
Can event products have their own taxonomy?
Yes. Enable Custom Taxonomy for a dedicated hierarchical event browsing structure.
Does the Event type manage capacity or seats?
The product model does not imply those operational behaviors. Validate them in the system responsible for ticketing or reservations.
