Wedding Registry API: Prices, Stock and Store Choice for Every Item
Couples register at one store, but guests can buy a gift at several. This guide covers what wedding registry product data takes to build yourself, how Affiliate.com handles it, and how to handle a registered store that has run out, with a demo.
A wedding registry API gives a wedding registry the part that is hardest to build: the product data for every gift. One request returns what the gift is, every store that sells it, today’s price in each and whether it is in stock. Couples usually register at one store, but their guests are not tied to it. A guest may find the same blender cheaper elsewhere, or reach the registered store to find it sold out. This guide covers what that data takes to build yourself, how Affiliate.com handles it, and how a registry can use it to choose where a guest buys. The demo below uses prices last pulled November 16, 2026.
What it takes to build a wedding registry’s product data yourself
A wedding registry is open for months, and its gifts are considered ones: cookware, bedding, glassware. Guests buy over the whole engagement, so the data has to stay right without anyone editing the list. For every gift, you would have to keep five things correct.
Keeping this current across many retailers for the length of an engagement is a data pipeline, not a registry feature.
How Affiliate.com handles it
Affiliate.com does the tracking. A registry sends the gift’s barcode and gets back every store with its price and stock, already matched and current.
Our guide to barcode search covers the identifiers. The same requests are available as MCP tools, which MCP or REST explains.
Choose where guests buy each gift
The demo groups real products by room. Pick a room and a gift, then choose the store the couple registered at. The page shows every store with its price and stock. If the store you chose has the gift in stock, it says where guests are sent and whether another store has it for less. If it has run out, it shows the next best store. Every figure comes from one real Price History API response for that product’s barcode, and the page holds a set of products rebuilt every night.
Choose a store that shows as out of stock, where there is one. That is the case a registry built around a single store gets wrong, and the reason to keep every store from the response.
The store choice, step by step
Whether to favor the registered store or the lowest price is a product decision. Some couples care where the gift comes from, for store credit or returns. Others only care that it arrives. The data supports either, so it can be a setting.
Couples who register at more than one store
Many couples register at two or three stores, which splits one wish list across several systems. For a guest that is more work, and for the couple it makes duplicates easy: the same gift can sit on two registries and be bought twice. Because the barcode is the same everywhere, a registry that keeps its list by barcode can show each gift once, with every store that sells it. Our Gift Registry API guide covers the same idea for any registry.
Rooms and timing
Wedding lists are usually grouped by room: kitchen, bedroom, dining and the rest of the house. A product’s category field is each merchant’s own text, so keep the room in your own data, saved with the barcode when the gift is added. Then every guest sees the same grouping.
Most purchases come in the weeks around the shower and the wedding. Check when the registry is shown, so a guest never sees stale data, and run a nightly check across the whole registry in the last two months, so the couple hears about a problem gift while there is time to swap it. Checking more often than daily rarely finds anything new, because the data behind the response changes over hours. How often product pages should be updated covers the schedule, and how price history helps a reader trust a deal shows how to back up a discount. Guests who want ideas first can use the Gift Guide API guide.
What the November 16, 2026 pull shows
On November 16, 2026 we pulled every store that sells each of the eight products in that day’s set. One of the eight products had at least one store that did not have them in stock. Four of the eight products with two or more stores in stock had a gap of at least ten percent between the cheapest and the most expensive store. For the first group a registry needs a fallback, and for the second it has a real choice to offer a guest.
This table is fixed to November 16, 2026. The demo above is rebuilt every night from a rotating set of products, so its figures will change. Treat the table as a record of one day. Rooms are our own grouping for the demo and not a merchant category. Each figure is a store’s current price in US dollars, and the gap is the difference between the cheapest and the most expensive in-stock store, as a percentage of the cheapest.
Getting started in three steps
- ✓Every store, price and stock level in one request
- ✓A fallback when the registered store runs out
- ✓The same data as an MCP tool or a REST request
{
"target_type": "barcode",
"target_ids": [
"885991222392"
],
"currency": "USD",
"include_series": false,
"include_stats": true,
"include_product": true,
"per_page": 25
}