Universal Gift Registry: Add Any Product Link From Any Store
A universal gift registry lets people add a product from any store by pasting its link. This guide covers what link matching takes to build yourself, how Affiliate.com handles it, and a demo that runs the real lookups.
A universal gift registry lets people add a gift from any store by pasting its link. Most registries cannot do that, because a link names one page at one store and a registry needs to know which product it is, where else it is sold and what it costs. Affiliate.com handles that part. It turns a link into a barcode, then returns every store that sells the barcode with its price and stock. This guide covers what link matching takes to build yourself, how the lookups work, and how a registry uses them. The demo below runs them on real products, with lookups last pulled November 17, 2026.
What makes a registry universal
A single-store registry is simple because the store knows its own products. Every item has the store’s ID, the store holds the price and stock, and a guest has one place to go. A universal registry has none of that. Items arrive as links from different stores, each with its own address format, its own tracking text and its own product ID.
What it takes to build link matching yourself
Accepting any link means solving several problems at once, and each one needs ongoing work.
Each of these is manageable alone. Together, across many retailers and for registries that stay open for months, they are a data pipeline and not a registry feature.
How Affiliate.com handles it
Affiliate.com does the matching and the tracking. A registry makes up to three lookups, and only the first touches a link.
The second lookup is what makes the registry universal, because it shows guests every store and not only the one the link came from. The third is optional. Our guide to barcode lookup covers all three in more detail, and barcode search covers the identifiers.
Add any store link to a registry
Pick a product page someone might paste, then step through the three lookups. Each step shows the real request and the real response, and the last step shows the one item the registry would save. The page holds a rotating set of products rebuilt every night, and it offers three of them, a different three on most visits.
Notice how little the registry keeps at the end: a barcode. The product name, stores and prices are fetched when the list is shown. That is why a second link to the same product is harmless. It produces the same barcode, so the registry sees the same item.
When a link does not convert
Some links will not convert, and a registry has to expect that. A link to a store that is not in the catalog returns an empty list. A page that sells a product in several colors or sizes can return several barcodes. Four responses cover the cases.
In a test of 98 product links from 45 stores on November 17, 2026, a link sent exactly as the store lists it converted to the product’s own barcode 74 times. Adding tracking text made no difference (77). Removing the query string made it worse (68), because a query string can choose the color or size. Changing the letter case of the path broke most matches (52). So send the link as it was pasted, and keep in mind that about one in four of these links did not return the product’s own barcode, so every flow needs a fallback.
Recognizing duplicates
A couple adds a pan from one store, a family member adds the same pan from another, and a guest buys both. With barcodes the check is simple: before saving an item, look for its barcode on the list. If it is there, add to the quantity or tell the person it is already wanted. This is the strongest reason to convert on the way in. A registry that stores links has to compare pages, and pages from different stores do not look alike.
What to store, and what to fetch
Keeping the original link is optional, and nothing should depend on it. See our Gift Registry API guide for building the list around the barcode, the Wedding Registry API guide for choosing a store when the first one runs out, and the Baby Registry API guide for checking stock.
What the November 17, 2026 pull shows
The three lookups ran on real products on November 17, 2026. We chose products whose links convert, so these results show what a registry can do with a link that matches, not how often links match. Every link in the table converted to the product’s barcode, and three of the five linked stores were more expensive than the cheapest store that had the product in stock. Three of the five had a store SKU on file for the linked store. None returned more than one barcode for the link.
This table is fixed to November 17, 2026. The demo above is rebuilt every night with a different set of products, so its figures will change. Treat the table as a record of one day. A handful of products is a small sample and not a measure of any market or of how often links match.
Terms
Getting started in three steps
- ✓Turn a store link into a barcode
- ✓Find every store that sells it
- ✓The same lookups as MCP tools or REST requests
{
"data": [
"https://www.example-store.com/product/12345"
]
}