Can a product tag open a different page once the product is sold?
Yes, if something records the sale and the address resolves through a service you run. The tag keeps one address for the life of the product and the resolver decides what to serve, which means the behaviour now depends on a state that has to be right.
One address, two answers
The tag is written once, in the factory or on the line, and the address it carries never changes. Everything variable lives behind it, which is the argument the storage page makes for every deployment.
Serving a shopper and an owner differently from one address is therefore a resolver question rather than a tag question. The resolver page describes the machinery: one identifier, several links, a default, and a way to ask for a particular type.
What changes here is that the choice depends on the state of one unit rather than on who is asking.
Something has to record the sale
A sale is an event the tag knows nothing about. Something has to tell the service: a till, an activation step, a registration, a warranty form, a shipment record.
It also has to be per unit. A model level identifier is the same on every item in the shop and in every cupboard, so it cannot be sold, which the level page covers. This feature is one of the few that genuinely requires item level identification.
Which means the cost is not the resolver, it is the plumbing that marks one item as sold at the moment it is sold, in every channel the product is sold through.
What a wrong state looks like
A unit marked sold while it sits on a shelf shows a shopper an owner page, with setup instructions and a warranty form. A unit still marked unsold shows an owner the shop page, which reads as a brand that does not know what it sold.
Returns, gifts, display stock and resale all produce the second state, and none of them are edge cases. A scheme that has no answer for a returned item has no answer for a percentage of its units.
The safe default is the page that works for both, served whenever the state is unknown, rather than a guess in either direction.
The answer that often wins
One page, written for someone holding the product, with the shop content as a section rather than a destination. The packaging page reaches that conclusion from the campaign side: what stays useful is instructions, specifications, reordering and support, and none of them expire at the till.
Splitting before and after earns its cost where the two audiences want genuinely different things, a demonstration against a setup guide, and where the sale is already recorded per unit for another reason.
Where it is built for elegance alone, it adds a state to maintain in exchange for a distinction most customers never notice.
Frequently asked questions
Does the tag get rewritten at the sale?
No. The tag keeps one address and the service behind it decides what to serve, which is the only approach that works for products already in the field.
Does this need an item level identifier?
Yes. A model identifier is identical on every unit, so there is nothing to mark as sold.
What should a tap show when the state is unknown?
The page that works for both. Guessing produces a shopper reading setup instructions or an owner reading a shop page.
Is it worth doing?
Where the sale is already recorded per unit and the two audiences want different things. Otherwise one durable page costs less and fails less.