Who Should Own WordPress Plugin Licenses?

A premium plugin license is not one decision. It is a set of responsibilities that should be assigned before launch, recorded in the care-plan agreement, and reviewed when the client relationship changes.

Separate the six decisions

• License ownership: Whose vendor account holds the subscription or entitlement?
• Payment responsibility: Whose card or budget pays the vendor at renewal?
• Renewal responsibility: Who monitors the date, checks whether the plugin is still needed, and completes the renewal?
• Client approval: Who must approve a charge before the agency commits money?
• Invoicing: Is the cost included in a care plan, passed through, marked up under an agreed policy, or billed separately?
• Care-plan coverage: Does access to an agency-provided license end when maintenance ends?

Keeping these decisions separate prevents a common failure: the agency assumes the client will pay, the client assumes the care plan includes the renewal, and nobody acts before the date.

Choose a model that fits the relationship

Client-owned and client-paid. This is usually the cleanest model when there is no continuing maintenance agreement. The client keeps the vendor account and billing relationship. The agency can still monitor the renewal and provide instructions.

Client-owned and agency-managed. The client owns and pays for the subscription, while the agency handles installation, updates, and renewal reminders under a care plan. Document the access the agency needs without sharing a personal password.

Agency-owned and included in a care plan. This can work when the vendor terms permit client-site use and the agency actively maintains the site. State which licenses are included, whether replacement is required at offboarding, and how much transition time the client receives.

Agency-owned and billed separately. Use a written approval and invoicing policy. The client should know the expected amount, billing cycle, and consequence of declining before the agency renews.

Vendor terms decide what can be shared or transferred

Do not assume every “agency,” unlimited, or multisite plan has the same rules. Check the current vendor agreement for site limits, staging allowances, account sharing, transferability, and continued use after the service relationship ends.

WooCommerce, for example, documents separate workflows for transferring ownership and billing, sharing access while retaining ownership, and client handoff. Its agency guidance also recommends recording which subscription keys connect to which client sites. See WooCommerce’s agency subscription guidance.

WordPress itself is released under the GPL, and WordPress.org states its view that plugins and themes are derivative works that inherit the GPL. A commercial vendor subscription can still govern services such as updates, support, downloads, cloud features, and account access. See the WordPress.org license page.

Put the agreement into operational fields

• Plugin or theme name, vendor, client, and website
• Vendor account owner and the operational renewal contact
• Payer, approval owner, billing cycle, expected cost, and tax treatment
• Care-plan coverage and whether the cost is included or separate
• Renewal date, auto-renew status, and current payment-method owner
• Sites or activations using an agency license
• Offboarding action: transfer, client purchase, replacement, or removal

Handle offboarding before access becomes urgent

1. Inventory every premium plugin and theme on the site.
2. Classify each item as client-owned, client-owned but managed, or agency-provided.
3. Check vendor terms before promising a transfer or continued access.
4. Give the client purchase or transfer steps and a realistic deadline.
5. Remove or reassign agency activations only after the replacement is confirmed.
6. Record the handoff without storing passwords or private license keys in the tracker.

The practical rule is simple: use client ownership for independence, and use agency ownership only where it is an explicit, vendor-permitted part of an active service. In either model, write down who approves, pays, renews, and invoices.