Q-SYS Plugin Activation
Order processing issue
Recent order failure
Open the order log to inspect payment processing.
Start here
Read meThis console is how you set up and manage a licensed Q-SYS plugin. In normal use there are only two steps — everything else is optional or for support.
Only when you need it
Plain-English glossary
- Activation Code
- The licence key the customer buys (
QPA-…). What they type on the activate page. - Plugin Activation Key
- The signed token the server returns, locked to one Q-SYS Core. What they paste into the plugin.
- Build constants
- Product ID + signing secret baked into the plugin at build time. Never shown in Q-SYS Designer.
- Core Locking ID
- The unique ID of a customer's Q-SYS Core. A licence binds to the first Core it activates on.
What this does Create a plugin product and get the build constants to paste into the plugin. Do this once per plugin, before you build it.
What this does Manage what the public shop shows for each plugin: listing copy, price, images and the download link. The Product ID doubles as the Paddle SKU and is what ties a purchase to offline plugin activation, so it is locked once licences exist.
Adding a product
1. Click Add product.
2. On Step 1 enter the Product ID (lower-case letters, numbers, dots and
dashes — e.g. coreforge.my-plugin.licence) and a Display name; the URL handle
fills itself in.
3. Fill in Listing and Pricing and click Next — the draft
saves itself automatically when you reach the Media step.
4. Upload the cover image (the first image is the cover) and any manual or
plugin files.
5. Check Review, then click Publish listing. Saved changes to a
published product appear on the store immediately.
Plugins
Not loadedLoad the catalogue to manage store listings.
What this does Find any licence or activation and export the licensing log to CSV. Real customer licences are created automatically from paid orders. Support actions for a single licence are at the bottom.
Support actions for one licence Reset / disable
What this does Order deliveries from Paddle, and how to read the live Cloudflare server logs. Per-licence history lives on the Licences tab.
Cloudflare server logs
Observability onLive request and error logs from the Worker itself. Observability is already enabled, so these are captured for you.
The dashboard link opens the Worker's Observability → Logs view. Pick your account if Cloudflare asks.
Testing only — your tool Real customers activate through the store and the customer activate page. Use this to create a test licence and mint or verify a token yourself when sanity-checking a plugin build.
Store analytics
Last 30 daysRevenue · Paddle
Loading…Revenue by plugin
No paid transactions yet.
Payment methods & status
No paid transactions yet.
Traffic · Cloudflare
Not connectedTop pages
No traffic data.
Traffic by country
No traffic data.
Sales by plugin
No sales recorded yet.
Downloads by plugin
No downloads recorded yet.
Purchase funnel
Where shoppers stopNo traffic recorded yet.
Traffic sources
No external traffic recorded yet.
Most visited pages
No page views recorded yet.
Where visitors are
Country onlyNo location data recorded yet.
Daily activity
No activity recorded yet.
Result
Ready
Waiting for a request.
Raw response (debug)
{}