Skip to main content

Product capabilities

Choose capabilities under Settings > Product types. They decide which settings and tools each product in that category can use. Curling IO supplies six capabilities; your organization chooses from that fixed list.

Turn on the settings you need for each product under Info. A capability makes an option available, but doesn't turn every product setting on. See How products fit together for the relationship between products, types and settings.

Purchasable​

Use Purchasable when people should buy something through checkout. The Products starter type uses it for merchandise, and Fees uses it for ordinary charges.

On Info, it makes Pricing, Addons, Discounts and Accounting available. Late Fee also needs Dates. Turn on Availability before these settings. Price and Taxes belong to Pricing; accounting codes, selected addons and discounts belong to their own sections.

On the public site, a product with Availability and Pricing can show a price and a purchase action. Its dates, inventory and visibility still determine whether a buyer can purchase it. Pricing must contain a value; enter zero for a free item. Taxes, discounts and other charges affect the checkout total. See Info.

Removing Purchasable makes those price-related controls unavailable. A type that still supports Registerable can still offer registration; a type with neither has no ordinary purchase or registration action. Removing both also removes Inventory.

Registerable​

Use Registerable when you need registration forms and records or need to assign a registration to a participant. Programs and Leagues are starter examples.

It makes Participant available on Info, where you can require a participant, set age or gender eligibility, and choose product-specific waivers. Turn on Availability to use those settings. An account-based purchase can leave Participant off.

With Availability on, the admin product shows Form builder and Registrations. The form builder controls the questions collected during registration; Registrations shows the resulting entries. Public registration can collect that information and require a participant when configured. Purchasable adds pricing to the same workflow.

Removing Registerable hides its participant controls and registration sections for an ordinary type. Purchasable can still support a simple purchase. Removing both Registerable and Purchasable also removes Inventory. Existing order records are kept.

Dates​

Use Dates for a product's period and its online purchase or registration window. Leagues, Programs, Products and Fees are starter examples that include it.

Info shows Starts and Ends in Basics and Opens and Closes under Availability. Starts and Ends are required. They describe the product's period; Opens and Closes control when online registration or purchasing is available. Fill in both window boundaries: a missing one makes a dated product unavailable. Before Opens, the product isn't open; at Closes, it is closed.

Dates also makes Late Fee available when the type is Purchasable. Admin product lists and positioning can be organized by season. Public details can show the product dates and opening or closing information. Checkout respects the configured window.

Removing Dates hides these date controls and stops using the date window for ordinary product availability. It also removes Event, so competition tools become unavailable. It doesn't delete the stored dates.

Inventory​

Use Inventory to limit how many registrations or items can be sold. Products uses it for stock, and Leagues can use it for capacity.

It requires Purchasable or Registerable. If neither is selected, selecting Inventory also selects Registerable.

Under Availability, set Inventory to the limit or leave it blank for unlimited capacity. Waitlist lets people express interest after capacity is sold. The admin Waitlist section appears when Availability and Waitlist are on. See Waitlist for follow-up.

Public cards and details can show remaining capacity. A sold-out product can't be bought normally; it can offer a waitlist action when configured. Checkout checks capacity. Removing Inventory hides those stock and waitlist controls and stops applying that capacity limit to new purchases. Stored limits and existing registrations remain.

Event​

Use Event to manage a competition's teams, stages, draws and scores. Leagues and Bonspiels are starter examples. It requires Dates; selecting Event also selects Dates.

On Info, turn on Event Settings for team format, composition, alternates, spares and venue details. Then turn on Schedule for resources and draw defaults. Results requires Schedule and controls scoring and public result options. These settings have their own dependency order.

The admin product can then show Participants, Teams, Stages, Schedule and Results. Free agents also depends on the product's free-agent and participant settings. Use the focused Teams, Stages, Schedule and Results guides for the work inside those sections.

Public schedules and results depend on the product's publication settings. When participant registration and event team settings are configured, registration can collect the event's lineup information. Event alone doesn't set a price or make a product purchasable.

Removing Event hides the competition settings and sections and makes their public event tools unavailable. Changing the type alone keeps the existing team, schedule and result data. Adding Event back makes the retained settings available again.

Managers​

Use Managers when someone needs access to one product without becoming an organization manager. Leagues, Programs and the Memberships starter include it. It doesn't require another capability.

It adds the admin Managers section. There is no Managers switch on Info. An organization manager assigns people and chooses their permitted sections there. The choices depend on the tools available for that product. See Managers for permissions and invitations.

This capability changes administration access management, without adding a public field or checkout question. Removing it hides the Managers assignment section; it doesn't delete existing assignments. Adding it back restores that section. Don't use a capability change as a substitute for removing a person's assignment on the Managers page.

Change a type carefully​

A type change affects every product using it. The current editor can save capability removals, including their dependency effects. Check existing products before doing this.

Changing the type alone keeps product configuration and historical data. If you restore a capability without changing the affected products, the retained settings become available again. Restore it before changing product settings that depend on it, then check the admin and public outcome.

Prefer leaving an unused setting off on a new product when the rest of the category still needs the capability. For type-management steps, see Product types.