Adobe Named-User Seats: Reharvesting Before the VIP Anniversary
Adobe named-user licences can be moved from one person to another at any time, but the number you pay for changes on one day a year. Under VIP Marketplace, that day is the Anniversary Date. Every seat still assigned and still in the renewal order on that date renews for another year at whatever price and discount level apply then. Reharvesting is the work of finding the seats nobody uses and deciding, before that date, whether each one goes to someone who needs it or out of the renewal.
Commercial customers now buy through VIP Marketplace: Adobe retired the original VIP program for commercial customers, with the move due by 31 May 2025. The mechanics below are from Adobe's VIP Marketplace help pages, which Adobe last updated in August and September 2026.
How named-user licensing works
A named-user licence belongs to a person's account, not to a device. Admins add users in the Adobe Admin Console and assign them product entitlements; Adobe describes the Admin Console as the place to assign, unassign and reassign licences, and to see who holds a licence and how many licences are purchased against how many are deployed.
That last point shapes the whole exercise. The Admin Console shows assignment. A seat assigned to someone who left the design team eight months ago looks exactly like a seat used every day. Knowing which seats are idle takes evidence from outside the assignment list.
The Anniversary Date, and what can change when
Adobe sets the Anniversary Date at 12 months after it accepts the organization's first VIP Marketplace order, and it recurs on the same calendar date every year. Every licence bought during the term co-terminates on it: licence terms end the day before the Anniversary Date, and seats added mid-term are prorated daily up to it.
| Action | Mid-term | At the Anniversary Date |
|---|---|---|
| Add licences | Any time, prorated to the Anniversary Date | In the renewal order |
| Reassign a seat to another user | Any time, in the Admin Console | Any time, in the Admin Console |
| Return licences | Only within 14 days of the order, and only licences not in use | Not applicable |
| Reduce the quantity | No, outside the 14-day return | Yes, through a partial renewal placed with the reseller |
| Change products (for example All Apps to Single App) | Upgrades only, through the reseller | Yes, through the reseller |
| Discount level | Can rise as licences are added | Reset to the quantity renewed |
Two rules from Adobe's renewal page drive the timeline. Licences auto-renew on the Anniversary Date unless the reseller turns off auto-renewal or cancels at least 3 days before it, and the reseller's own change or cancel period may be longer. And the discount level at renewal is based on the qualifying licence count on the Anniversary Date: level 1 is 1 to 9 licences, level 2 is 10 to 49, level 3 is 50 to 99 and level 4 is 100 or more.
Adding seats is also easier than removing them. A licence added in the Admin Console is available at once, but the reseller must place the order with Adobe within 7 days or Adobe removes it.
Finding seats nobody uses
Because the Admin Console records who is assigned, not who works in the apps, the evidence for an idle seat comes from three places that sit next to it:
- The HR leaver and mover list. Anyone who has left, or moved to a role that does not use the product, is the easiest seat to recover. Match accounts to the HR record, not to display names.
- Sign-in records from the identity provider. Where Adobe sign-in runs through single sign-on, the identity provider's logs show who has authenticated recently and who has not.
- Installed software on the endpoint. A user assigned All Apps who has Acrobat and Photoshop installed and nothing else is a candidate for a cheaper product at renewal. A user with no Adobe app installed at all is a candidate for removal.
LICENSEWARE's Adobe Deployment Manager handles the third source. It reads the installed Adobe products, versions, install dates and device-user mapping from the discovery data an estate already has, resolves the licence each device actually needs, and flags where a Single App licence covers what an All Apps seat is paying for. Set against the Admin Console export, that turns an assignment list into a list of seats to keep, move, downgrade or drop.
A reharvest timeline, working back from the anniversary
Take the Anniversary Date from the Account tab in the Admin Console or the order confirmation, then work backwards:
- 90 days out: export the users and their product assignments from the Admin Console, and pull the HR leaver list, the identity provider sign-ins and the endpoint install data for the same people.
- 60 days out: build the candidate list and send it to line managers with a deadline. Unassign seats from leavers straight away; those seats can go to new starters instead of new add-on orders.
- 45 days out: decide the renewal: the quantity per product, any All Apps seats moving to Single App, and whether the new total crosses a discount threshold in either direction.
- 30 days out: ask the reseller for their cut-off date for renewal changes, and send the renewal quote request. Adobe's minimum is 3 days before the anniversary; the reseller's is often longer.
- Before the reseller's cut-off: confirm the partial renewal order, and in the Admin Console select the named users whose licences will be deprovisioned.
- After the anniversary: check the Admin Console counts against the order, and check that nobody who should have kept a seat lost it.
Mid-term, the same list still earns its keep. A seat recovered in month four cannot be refunded, but reassigning it to a new starter avoids buying a prorated add-on for them.
Common mistakes
- Unassigning in the Admin Console and expecting the renewal to shrink. Adobe's renewal page is explicit that unassigning licences is not enough to show you do not want to renew them. The reseller has to place the right renewal order.
- Leaving Adobe to choose which licences go. If the admin does not select the users to deprovision in a partial renewal, Adobe removes licences that were never assigned first, then the most recently assigned. The most recently assigned seat is usually a new starter's.
- Missing the reseller's window. The 3-day minimum is Adobe's; a reseller that needs two weeks turns a late decision into another year of auto-renewed seats.
- Dropping below a discount level without pricing it. Renewing 48 seats instead of 52 moves the organization from level 3 to level 2, and every remaining seat is priced at level 2.
- Forgetting promotional pricing. Adobe notes that a product bought on promotional pricing renews at standard pricing, so the renewal quote can rise even with fewer seats.
- Reducing under a 3-year commit. Customers on the VIP Marketplace 3-year commit can only return quantities that keep them at their minimum commitment; the amendment sets the floor.
Seat counts are only part of the renewal. Price changes and exit terms matter as much, which is where Adobe's 2025 pricing changes and what Adobe cancellation fees really cost come in.
FAQ
What is the Adobe VIP anniversary date?
It is the date each year when all VIP Marketplace licences renew, set 12 months after Adobe accepts the first order. Licences bought during the year are prorated so they all end the day before it.
Can you reduce Adobe licences mid-term under VIP Marketplace?
Only through a return within 14 days of the order, for licences that are not in use. Otherwise the quantity changes at renewal, through a partial renewal order placed with the reseller before its cut-off.
What happens if you do not choose which users lose their licence at renewal?
Adobe removes licences that were never assigned first, then the most recently assigned ones. Selecting the named users to deprovision in the Admin Console keeps that decision with you.
Does the Admin Console show whether a named user actually uses Adobe apps?
Adobe describes the Admin Console as showing who holds a licence and how many licences are purchased against deployed. Evidence of use comes from elsewhere: HR records, single sign-on logs and the Adobe software installed on each device.
