Creating a License Type #
Before You Begin #
Plan your License Types to match your product catalog. Common patterns are one type per pricing tier, or one type per license model (annual vs. lifetime). Avoid creating redundant types that serve the same purpose.
Steps #
The new type appears immediately in the list above. Its slug is auto-generated from the Name you entered using WordPress’s sanitize_title() function (lowercase, hyphens for spaces, no special characters).
Field Reference #
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Displayed in product dropdowns and admin lists |
| Description | No | Internal note; not shown to customers |
| Activation Limit | No | 0 = unlimited |
| Is Lifetime | No | If checked, licenses never expire (new in v1.2.2) |
| License Duration (months) | No | Ignored when Is Lifetime is checked |
| Allows Updates | No | Whether licenses of this type can receive software updates |
| Allows Premium Content | No | Whether licenses of this type unlock premium content |
| Allows API Access | No | Whether licenses of this type can call your API |
| Sort Order | No | Controls display order in lists; lower numbers appear first |
| Set as Default | No | Pre-fills the License Type dropdown on new products |
Rules #
- Two License Types cannot share the same name (slugs must be unique).
- The slug cannot be changed after the type is created.
- Only one type can be the default at a time; setting a new default clears the previous one.
Related Topics #
- [License Type Fields Explained](#)
- [Editing a License Type](#)
- [Common License Type Configurations](#)