Learn / For your team
Agent readiness during a replatform
A replatform is the cheapest opportunity to build agent readiness in, because the requirements cost almost nothing when specified up front and a great deal to retrofit. It is also where readiness is most often lost silently, since a new storefront can look identical to the old one and serve markup with none of the facts the previous one published.
A replatform is the cheapest moment to get agent readiness right and the easiest moment to lose it without noticing. Both halves of that are worth planning for.
Why it is cheap now
Specifying that product pages emit price, availability and variant data server side costs almost nothing when it is in the requirements. Retrofitting it into a delivered storefront is a change request against a finished build.
The same is true of a guest checkout and of real form controls in the variant picker: they are design constraints when stated up front and rework when discovered afterwards.
The five requirement lines
- Product pages emit price, availability, variant data and an identifier in the served markup.
- A complete product feed, rebuilt on price and stock change.
- Policies published as text with one canonical page each.
- Guest checkout reaching the payment step from a cold session on a narrow viewport.
- An automated test asserting the first line, running in the pipeline.
Why it is lost silently
A new storefront is signed off on how it looks and how it behaves for a person clicking through it. Neither of those reveals that the price moved into a client rendered component, which is a common consequence of a more modern front end.
So the store launches looking better and publishing less, and nothing in the acceptance process is designed to catch it.
The pre-launch check
Fetch the same twenty products from the old site and the new one with scripts disabled, and diff what is present. Anything the old site published and the new one does not is a regression to fix before launch, not after.
Then walk checkout cold on a narrow viewport. See the agentic readiness checklist.
Questions
What should go in the requirements?
Structured product data in the served markup at variant level, a complete feed, policies as text, a guest checkout that works in a cold session, and a test asserting the first of those. Five lines, and each is cheap when specified early.
How do I check before launch?
Compare served markup between old and new on the same products with scripts disabled. Anything the old site published and the new one does not is a regression, regardless of how the pages look.
What about URLs?
Redirect properly and keep your sitemap and feed current through the transition. A feed pointing at retired URLs is confidently wrong, which is worse than a feed that is briefly missing.