Is your store ready for Universal Cart?
Google's cart buys from the product data your pages publish, not from the page a shopper sees. mttr reads your product pages the way it does and checks the twelve fields a cart needs.
Two views of one product
A shopper reads the page. A cart reads only the data under it, and buys from that.
What a shopper sees
Linen shirt
$68.00, in stock, free returns for 30 days
What a cart reads
"@type": "Product",
"name": "Linen shirt",
"image": "//cdn.shop.example/shirt.jpg",
"offers": {
"price": "$68",
"priceCurrency": "Dollars",
"availability": "in stock"
}A sample, written the way many themes write it. Everything a shopper sees is on the page, but a cart cannot use it: the image is not a full address, the price is text, the currency is a word, stock is not a schema.org value, and the free returns are nowhere in the data.
What stores publish
371,608 product pages from 23,471 stores in the US and Canada that mttr has read.
A count of fields says what a page's data states, read before any script runs. It does not decide eligibility: Merchant Center and Google's own review decide whether a product shows in merchant listings, Universal Cart or any other Google feature.
Fix it where the data starts
The Shop Ready skill works in your store's own theme with Claude Code, Codex or Cursor, writes every field from the product's own data, and checks the live pages with mttr after. On Shopify, mttr can do it from the admin: that is in beta.