The Settings page is where you control how the plugin behaves – when keys are generated, how ticket numbers look, which REST API features are enabled, where shortcodes appear, and how to load demo data for testing. All of these settings live in one place.
Where to find it: Go to License Verification → Settings in your WordPress admin.
Section 1 – Order License Generation
This section controls when the plugin creates license keys. There are two triggers and you can use one or both.
| Setting | What It Does | Recommended? |
|---|---|---|
Generate on order placed |
Creates the license key the moment the customer completes checkout – instantly, before the order is even paid (for pay-later methods). The customer gets their key immediately on the “Thank you” page. |
Yes – recommended for all digital product stores |
Also generate when order status is… |
A backup trigger – if you tick one or more WooCommerce order statuses (e.g. “Processing”, “Completed”), the plugin also generates keys when the order reaches those statuses. This only runs if no key has already been created for that item. |
Use for physical product bundles or bank-transfer orders that need payment confirmation before key delivery |
Both options can be active together without risk. The system checks whether a key already exists before generating – no order item will ever receive two keys.
Section 2 – Support Tickets
| Setting | What It Does | Example |
|---|---|---|
Ticket number prefix |
The text that appears at the start of every ticket number. Choose something that matches your brand – it appears in every ticket notification email. |
WLV-, SUPPORT-, HELP- |
Preview |
A live preview next to the field shows you what the full ticket number will look like, for example: |
– |
The prefix applies to new tickets only. Tickets that already exist in your system keep their original numbers permanently – changing the prefix does not rename existing tickets.
Section 3 – Shortcodes & Customer Pages
This section shows you all the shortcodes available and gives you the URLs to your customer-facing My Account pages. Use these shortcodes to embed plugin functionality anywhere on your website.
| Shortcode | What It Adds to Your Page | Where to Use It |
|---|---|---|
[wlv_support_form] |
A full support ticket form. Logged-in customers can submit a new ticket directly from this page. |
A “Contact Support” or “Get Help” page |
[wlv_verify_license] |
A public form where anyone can type a license key and check if it is valid. No login required. |
A “Check Your License” page, product pages, support pages |
[my_license] |
Shows the logged-in customer’s full list of license keys with status and expiry. Same view as My Account → Licenses. |
A custom “Your Products” or “Your Licenses” page outside My Account |
The Settings page also shows you the direct URLs for the built-in My Account pages (Licenses, Support, View Ticket) so you can share them with customers or add them to your site navigation.
If a My Account page URL shows a 404 error, go to Settings → Permalinks in WordPress admin and click “Save Changes” – no need to change anything, just saving flushes the URL cache and fixes the issue.
Section 4 – REST API
The REST API section lets your software communicate with the plugin programmatically – verifying, activating, and deactivating license keys without any manual admin action. See REST API for full details.
| Setting | What It Controls |
|---|---|
Enable License API |
Master switch for the REST API. When OFF, all API requests return a 503 error regardless of the key. Turn this ON when you are ready for your software to start making API calls. |
API Secret Key |
A unique, automatically generated secret code that your software must send with every API request to prove it is authorised. Keep this private – treat it like a password. |
Regenerate button |
Creates a new random API key. Use this if you suspect your API key has been exposed. Warning: all software currently using the old key will stop working immediately until you update them with the new key. |
Base URL |
The starting URL for all API endpoints. Your software appends the specific endpoint name to this URL. Shown in the settings page for easy copying. |
Section 5 – Support Email Notifications
This section shows you a list of all support ticket email notifications and whether each one is currently enabled or disabled. Click the “Configure” button next to any email to open WooCommerce’s full email settings for that notification, where you can customise the subject line, heading, and email content.
Section 6 – Demo Data
Demo data lets you populate your store with sample content for testing and previewing how things look – without needing to place real orders. This is only for development or learning. Never use demo data on a live store that has real customer orders.
| Demo Data Button | What It Creates | Safe to Use? |
|---|---|---|
Load demo data |
Creates three sample license plans (Starter, Professional, Lifetime), links them to demo products, and generates sample license keys for test customers. |
Yes – only runs if plans and licenses table is empty. Skipped if real data already exists. |
Load demo support tickets |
Creates sample support tickets showing Open, Pending, and Closed statuses, with staff and customer replies, so you can preview the admin inbox without real customer traffic. |
Yes – only runs if the tickets table is empty. |
Remove demo data before going live. Demo licenses and tickets appear in your admin reports and counts. Clear them before your store receives real customers – or use demo data only on a staging/test site that is separate from your live store.
Settings Tips
- The very first time you set up the plugin, go through Settings top to bottom. Enable “Generate on order placed,” set your ticket prefix, check that the My Account URLs work, then place a test order to confirm everything generates correctly.
- Do not share your API Secret Key publicly. Put it in your software’s configuration file and restrict access to that file. If it is ever exposed, regenerate it immediately.
- Use a ticket prefix that matches your company name or product. For example, if your company is “TechCo” and your product is “BuilderPro,” use prefix
BUILDERPRO-so tickets look likeBUILDERPRO-1001. - Load demo data on a staging site and explore every feature before setting up on your real store. It is much easier to learn in a test environment where mistakes have no consequences.