Plans & features: does the hub agree?
Two separate things decide whether a paid feature works. This plugin knows which plan every feature belongs to. Our licensing hub decides which plan you are on, and what that plan unlocks. They have to be holding the same list, or a feature you have paid for can stay padlocked.
How they stay in step
Whenever a release moves a feature between plans, or adds one, this site sends the hub its whole feature-to-plan map on the next licence check. That is a few kilobytes, once, and then not again until something changes.
Why the line on the Licensing page exists
Until 2.625.0 the site recorded the map as delivered the moment any reply came back — and nothing in a reply actually says the hub applied it. A map that reached a hub too old to read it, or that was dropped on the way in, was marked done and never sent again, because the map had not changed. The two ends then disagreed permanently, silently, and the only symptom was somebody’s paid feature that never appeared.
Now the hub has to echo the map back before this side believes it, and the Licensing page says which of those you are looking at. Unconfirmed is re-offered once a day until it is answered.
What the line can say
Confirmed — the hub has said it holds this version’s map. Nothing to do.
Not sent yet, or this version changed something — it goes with the next licence check. Press Re-check licence if you would rather not wait.
Sent, not confirmed — normal on an older hub, which does not answer either way. It is only worth chasing if a feature somebody has paid for is not unlocking.
Example
A customer on Premium reports that rotas are padlocked. Everything on this side looks right, and it would once have taken a support session to find out why. The Licensing page now says outright that the hub has never confirmed it holds this version’s plan map — which is the answer, in one line, before anybody opens a database.
FAQ
It says unconfirmed. Is something broken?
Not necessarily, and usually not. An older hub does not answer either way, so unconfirmed is what a working site looks like against it. It matters when a feature somebody has paid for is not unlocking — then this is the first place to look.
What is actually sent?
A list of feature names, which plan each belongs to and which service each belongs to, plus a checksum of that list. No customer data, no key, no token.
Why does the service matter as well as the plan?
Because two separate things decide whether a feature works: your plan, and which services you bought. If you pay for grooming only, the walking and sitting features are not yours whatever your plan. The hub works that out from what this plugin tells it — and until 2.626.0 it was told the plan and not the service, so a single-service licence was quietly given the other services’ features as well. If you run one service and have been seeing screens for trades you do not offer, that was why, and it is fixed.
How often?
When it changes — so in practice on the first licence check after a release that moved something. If the hub has not confirmed it, once a day until it does.
Can I force it?
Yes. Press Re-check licence on the Licensing page.
I am on the free plan. Does any of this apply?
No. Basic needs no licence and no hub, so there is nothing to keep in step.