We compile a register of third-party dependencies and their licences — premium plugins, themes, API subscriptions — with renewal dates and costs, a commercially-focused tracking document distinct from a technical map of how those dependencies actually interact with each other.
Third-party dependency & licence register
A register of licensed plugins, themes, and subscriptions with renewal dates and costs.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to review installed premium plugins, themes, and third-party subscriptions
- Any existing licence or renewal information you already have on hand
- Your preferred format for the finished register
This or something else?
| You want a register tracking licences, renewal dates, and costs for third-party dependencies | This fix covers it |
| You want technical dependencies between plugins mapped instead of licence tracking | Plugin dependency & interaction map, in the Integrations & Automation bucket, a different, technical focus |
| You want general plugin and theme rationale documented, not specifically licensing | Plugin & theme inventory with rationale |
| You want this as part of a broader SaaS account security audit | SaaS account audit & access inventory report, a different, security-focused document |
What we do
- Identify every licensed premium plugin, theme, and third-party subscription
- Document renewal dates and costs where determinable
- Flag anything with an unclear or seemingly lapsed licence status
- Compile into a clear, organised register
- Recommend a review cadence to keep this current
What is included
- A register of licensed dependencies with renewal and cost details
- Flags for unclear or lapsed licence status
- A clear, organised document
- A recommended review cadence
Not included
- Technical dependency mapping between plugins — a separate, different-purpose document
- Renewing or purchasing any licence found lapsed — that’s your action to take
- Security auditing of third-party account access — a separate, related report
- Ongoing maintenance of this register, beyond the initial compilation
Questions about this fix
Is this the same as the plugin dependency map?
No — that maps technical interactions between plugins; this tracks the commercial side, licensing and renewal dates, which is a different, business-focused purpose.
What if I find a licence has already lapsed?
We'd flag it clearly so you can address the renewal — actually renewing or purchasing the licence is your action to take directly with the provider.
How do you determine renewal dates if I don't have records handy?
We'd check what's determinable from the plugin or service's own account area where accessible, supplementing with any records you can provide.
Should this be updated regularly?
Yes, we'd recommend a review cadence (annually, or whenever you add a new paid dependency) to keep this genuinely useful rather than letting it go stale.
Does this include free plugins, or just paid ones?
Primarily paid, licensed dependencies, since that's where renewal and cost tracking actually matters — a general plugin inventory covers the full picture including free plugins.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.