DEV Community

Cover image for Product Recall Data as a Notification Service: From Notices to Affected Batches
EveryInfra for EveryInfra

Posted on Originally published at everyinfra.com

Product Recall Data as a Notification Service: From Notices to Affected Batches

The U.S. Consumer Product Safety Commission (CPSC) published 165 recalls between Aug 6, 2026 and Nov 12, 2026. We pulled every record from its public recall API at 00:15 Singapore time (SGT) on Nov 18, 2026. Only 2 of the 165 records fill the structured UPC field. Not one record fills the structured model field. The model number appears only in the free-text description, in 91 records (55.2%).

We also pulled FDA food enforcement records from openFDA at the same time. The median food recall reached the weekly Enforcement Report 42 days after the firm started it. None of the 333 food records arrived within 7 days. So machines can read recall data today. But the data alone cannot answer the question a user asks: "Is this notice about the item in my kitchen?"

We then ran 14 live calls on EveryInfra marketplace and resale search, for a total charge of $0.016737. We searched for the recalled 3M laminator, model TL1302Z, on eBay, Walmart and Amazon. The 50 results held 0 listings for TL1302Z and 11 listings for other TL1302 variants: TL1302X, TL1302XVP, TL1302VP, or no suffix at all. All 11 were up for sale, and one of them was used. We also searched for Bose S1 Pro batteries. All 10 Amazon results were third-party batteries, and 9 of their titles used a recalled serial prefix as a part number. A matcher that trusts names or digit strings sends alerts to the wrong people.

Key points

  • Of 165 CPSC recalls from Aug 6 to Nov 12, 2026, only 2 (1.2%) fill the structured UPC field and 0 fill the structured model field; 91 put the model in the description text.
  • Of 333 openFDA food enforcement records, the median gap from recall start to weekly report is 42 days (25th percentile 27, 75th percentile 65); 0 arrive within 7 days. openFDA says a status stays unchanged after publication, yet 12 of the 14 "Terminated" records were terminated after their report date.
  • Searching the recalled TL1302Z by name on three platforms gave 0 exact listings and 11 near-model listings out of 50 results.
  • CPSC warnings are not in the recall API: of 10,089 records, the latest "CPSC Warns" title is from 2023-05-18, and the Bambora sling warning of Nov 12, 2026 is missing.
  • Our 14 live calls cost $0.016737; a seller who checks three marketplaces for each of about 50 new recalls per month pays about $0.27 per month in API fees.

What the official recall API gives you, and what it leaves out

The CPSC recall API page says that recall data is available through a REST endpoint in XML or JSON. A programmer's guide describes the fields. Each record has a recall number, a recall date, a last publish date, a title and a description. It also has products, retailers, countries of manufacture, hazards, remedies and images. The schema looks complete. We counted the fields that actually hold data in every record since Aug 1, 2026.

The structured ProductUPCs array is not empty in 2 of 165 records. Each of those 2 records lists 2 or 3 barcodes. The Products[].Model field is an empty string in all 165 records. We also looked at the full database, because the endpoint returns all 10,089 records when it ignores a filter. The records run from Jun 8, 1973 to Nov 12, 2026.

The model field is empty in every one of them. In the 521 recalls of 2026, only 15 (2.9%) list a UPC. The identifiers still exist, but they sit in the free-text description. In our 165-record sample, 91 descriptions use a phrase such as "model number", and 37 mention a lot, a date code or a serial number. The first job of a recall alert service is to extract those values from the text and keep the evidence for a human to check.

Horizontal bar chart of 165 CPSC recalls published from Aug 6 to Nov 12, 2026, showing the share that carries each kind of data: structured UPC field filled 1.2%, structured model field filled 0%, model number in the description text 55.2%, lot, date code or serial mentioned 22.4%, Amazon named as a sales channel 55.8%, sold online or through a web store 84.8%. The structured fields that allow an exact match are almost empty.

Field in the CPSC recall API Records with data (of 165) Share What it means for matching
ProductUPCs (structured barcode) 2 1.2% Exact barcode match is rare
Products[].Model (structured model) 0 0% You must extract the model from text
Model number in the description 91 55.2% Model match is possible after extraction
Lot, date code or serial mentioned 37 22.4% The user must read a label
Retailers include online or web store 140 84.8% You can check marketplaces
Amazon named as a channel 92 55.8% Many third-party sellers, mixed model names
Remedy includes a refund 115 69.7% The alert needs a refund link

3M recalled its Scotch thermal laminator on Oct 15, 2026. The CPSC notice names model TL1302Z. The model is on a sticker on the bottom of the unit. About 53,634 units were sold, only on Amazon.com, from June 2024 through September 2026.

In the API record, the description says TL1302Z twice. The structured model field is empty, and the UPC array is empty too.

Data source screenshot of the raw CPSC recall API response for recall 27024. A teal box marks the description text, which contains model TL1302Z twice. A red dashed box marks the structured fields: Model is an empty string and ProductUPCs is an empty array.

Raw CPSC API response: the model is only in the description, and the structured fields are empty. | source: CPSC Recalls API raw response 2026-11-18 00:15 SGT https://www.saferproducts.gov/RestWebServices/Recall?format=json&RecallDateStart=2026-08-01

These numbers set the limit for version one. Do not promise "scan a barcode and know." Barcode matching works for food and drugs. In openFDA, 56.8% of food records and 74.5% of drug records mention a UPC or an NDC code. For consumer products, barcode matching almost never applies.

Consumer recalls depend on a model plus a date code, a lot or a serial range. That information hides in descriptions, image captions and remedy text. One wrong character in an extraction rule can push a whole group of users to the wrong answer.

One suffix letter apart: TL1302Z and TL1302X

We wanted to see what name matching does in practice. At 00:16 SGT on Nov 18, 2026, we called ebay/search with "Scotch thermal laminator TL1302Z". It returned 20 listings and none had TL1302Z in the title. Eight listings belonged to the TL1302 family with another suffix: X, XVP, VP, or no suffix.

The other 12 listings were other Scotch models, such as TL901 and TL906. In the same minute we called walmart/search with "TL1302". One of 20 results was a Scotch TL1302X sold by Walmart.com, in stock at $49 with a was-price of $56. At 00:17 SGT we called amazon/search.

Two of 10 results were in the TL1302 family. One title only said "Extra Wide 13 Inch Input", and its description named the TL1302X. It was in stock at $49.

Stacked bar chart of four searches for recalled models, with results in three groups: eBay for TL1302Z, 20 results, same model 0, near model 8, other 12; Walmart for TL1302, 20 results, same model 0, near model 1, other 19; Amazon for TL1302Z, 10 results, same model 0, near model 2, other 8; eBay for NEWDERY ZHX-PB22, 20 results, same model 0, same brand other model 9, other 11. No search found the recalled model, and near models or same-brand items add up to 20.

The CPSC notice names only TL1302Z. It does not say whether the TL1302X shares the same circuit or the same factory batch, and we cannot tell. By the text of the notice, the TL1302X is outside the recall. A matcher that keys on the prefix "TL1302" will tell TL1302X owners that their laminator is recalled.

A matcher that keys on "Scotch laminator" produces even more false alerts. The reverse case is also hard. If a seller writes only "TL1302" with no suffix, the system cannot call the item safe. At 00:26 SGT we opened that eBay listing with ebay/product_detail.

The structured model and mpn fields both said "TL1302", the gtin field was null, the condition was used, and the price was $45. This listing goes to the "cannot tell" tier. Only the sticker under the machine can answer.

Data source screenshot of real EveryInfra ebay/search and walmart/search responses. It lists 7 titles that contain TL1302 with suffixes XVP, none, X and VP. None of them is the recalled TL1302Z.

Real response: the recalled model is TL1302Z, and every hit carries another suffix. | source: EveryInfra ebay/search and walmart/search real response 2026-11-18 00:16 SGT

The second case is a NEWDERY power bank, recalled on Sep 24, 2026. The CPSC notice names model ZHX-PB22, black with yellow cables, about 21,380 units, sold on Amazon from October 2023 to November 2024. At 00:26 SGT we called ebay/search with "NEWDERY power bank ZHX-PB22". None of the 20 titles had ZHX-PB22. Nine were other NEWDERY products, mostly phone battery cases and magnetic chargers.

At 00:36 SGT a walmart/search call for "NEWDERY power bank" returned 20 results with no NEWDERY item at all. Other brands filled the page. The 9 same-brand items show that "brand plus category" is weak evidence. It can only reach the "possible" tier, and even then with care. A user who owns a NEWDERY battery case should not get "Your NEWDERY power bank is recalled." After one such alert, many users stop reading alerts.

Recall (CPSC date) Identifier in the notice Search time (SGT) Exact-model listings Near model or same brand Right match tier
3M Scotch laminator (2026-10-15) Model TL1302Z 00:16-00:17 0 / 50 11 / 50 Confirm only on the full model
NEWDERY power bank (2026-09-24) Model ZHX-PB22 00:26, 00:36 0 / 40 9 / 40 Model to confirm, brand only to "possible"
Love To Dream sleep machine (2026-09-24) Model LTD-SM23 + date code 7W15TN 00:19 Walmart: 0 results n/a Both values must match
Bose S1 Pro battery (2026-11-05) First 6 digits of the battery serial 00:18, 00:35 0 titles with a serial 14 third-party batteries Ask the user to read the label
Walmart Expert Grill brush (2026-10-01) A list of model numbers 00:35 0 titles match a recalled name 7 same-brand items in stock Ask for the number on the package

Four kinds of identifiers, four matching rules

We read all 165 descriptions. The identifiers fall into four kinds. Each kind needs its own matching rule and its own user prompt.

The first kind is a model only. The 3M TL1302Z is an example. The notice says that every unit of that model is in scope. If the user's registered model equals the notice model, the match is confirmed.

If only a prefix matches, it is not. The hard part is registration. Users remember "Scotch 13-inch laminator", not the suffix. The product must guide them to the sticker under the unit at sign-up time.

The second kind is a model plus a date code. Love To Dream recalled a portable sleep machine on Sep 24, 2026. The notice says that only units with model LTD-SM23 and date code 7W15TN are in scope. Both values are on the side of the unit or the back of the box. A user who matches on model only should get "Please check the date code on the side." That user should not get "Your sleep machine is recalled." At 00:19 SGT we called walmart/search with "Love To Dream portable sleep machine".

It returned 0 results and charged $0. An empty result means only that Walmart search showed nothing for that name at that time. It does not prove that the item left every channel. The notice also lists Target, Nordstrom and the brand's own site.

The third kind is a serial range. Bose recalled lithium-ion battery packs for the S1 Pro and S1 Pro+ speakers on Nov 5, 2026. The notice lists 7 six-digit prefixes. A battery is in scope when its 17-digit serial, printed on a label under the pack, starts with one of them.

About 634,759 packs were sold in the U.S., and about 35,400 more in Canada. Consumer Reports says "more than 634,000". Android Authority says "over 670,000", because it adds the Canadian units. An alert should quote the number from the notice and say which country it covers.

The fourth kind is a list of model numbers. Walmart recalled more than 4.4 million Expert Grill brushes on Oct 1, 2026. The notice shows a table of model numbers, product names and sale periods. The API flattens that table into one run of text.

Model numbers and names sit side by side, such as EX5607031616002 followed by "Expert Grill 16-inch Steel Fiber Scrub Brush and Scraper". The extractor must split the flattened table into rows. If it does not, a model number can attach to the product name of the next row.

Illustration: four identical small-appliance cartons stand on a shelf. A magnifying glass points at the bottom label of one carton, which shows a barcode and a dot pattern. That carton has a teal outline. A notice card with a bell floats above and connects to the label with a dashed line.

Identical boxes differ only on the label: the model, date code or serial decides the scope. | source: EveryInfra generated illustration

Identifier kind Example What to ask at registration Prompt when only part matches
Model only 3M TL1302Z Full model with suffix "Check the last character on the bottom sticker"
Model + date code Love To Dream LTD-SM23 + 7W15TN Model and date code "The model matches. Check the date code on the side"
Serial range Bose battery, 7 six-digit prefixes 17-digit serial under the pack "Read the first 6 digits of the serial"
List of model numbers Walmart Expert Grill Number on the package or tag "Find the model number on the package or tag"

Three match outcomes: confirmed, possible, cannot tell

A recall alert system needs a match ladder that it can explain. The strongest evidence is an exact combination of identifiers. Examples are model plus date code, or model plus a serial range. Weaker evidence is a model match with a missing date code or lot. A brand match or a loose name match is only a lead. It must never become "Your item is recalled."

Design the output in three tiers. A confirmed match means that the key identifiers in the notice equal what the user registered. Send the alert now and attach the official notice. A possible match means that some conditions match but the lot, date or serial is missing.

The alert tells the user where to find the missing value. "Cannot tell" means that the notice or the registration lacks a key identifier. Keep watching and do not state a conclusion.

Diagram of three match outcomes. 1, confirmed match: model plus date code, lot or serial range all agree; notify now with the official text and the action. 2, possible match: only brand, category or a model prefix agrees; ask the user to check the missing label field. 3, cannot tell: the notice or registration lacks a key identifier; keep watching and never say safe.

"No match" does not mean "safe". It means only that the system found no evidence in the sources it covers, with the current data and identifiers. At 00:18 SGT, ebay/search for "Bose S1 Pro battery pack" returned 20 listings. Eight were batteries: 4 third-party compatible packs and 4 original or unstated packs.

The other 12 were speakers or bundles. At the same time, facebook/marketplace for "Bose S1 Pro" returned 20 listings: 3 loose battery packs, 11 speakers and 6 other Bose items. At 00:35 SGT, amazon/search for "Bose S1 Pro battery" returned 10 listings, and all were third-party batteries. Across 50 results on three platforms, no title showed the serial of a specific battery. Loose original packs can only go to "cannot tell".

Stacked bar chart of Bose S1 Pro battery search results by item type. eBay, 20 listings: original or unstated battery 4, third-party battery 4, speaker or bundle 12. Facebook Marketplace, 20 listings: original or unstated battery 3, speaker or bundle 11, other Bose item 6. Amazon, 10 listings: third-party battery 10. Titles that show a battery serial: 0. Titles that use a recalled prefix as a part number: eBay 2, Amazon 9.

Digit strings can also mislead a matcher. Of the 10 third-party batteries on Amazon, 9 titles contain one of the six-digit prefixes from the notice. Examples are "789175 078592 Battery Replacement for Bose S1 Pro" and "084105 Replacement Battery for Bose S1 Pro+ 084106". Two eBay titles do the same.

In these titles the digits are part numbers. Sellers use them to say which original part the battery replaces. They are not the serial of any battery. A rule that flags "recalled prefix in title" would push 11 third-party batteries into "possible".

The Bose recall covers Bose's own battery packs. The correct rule compares the prefix only with the 17-digit serial that the user reads from the battery label. Numbers taken from listing titles never reach "confirmed".

Use image recognition only to help users copy a label, never to make the final decision. OCR suggests a model and a barcode, and the user confirms them.

TL1302Z and TL1302X differ only in the last character, and Z and 2 are a common OCR confusion. Store the fields that the user confirmed, and match on those. Do not guess again from an old photo.

The time gap: food recalls reach the weekly report 42 days late

The speed of an alert depends on its source. The openFDA food enforcement endpoint takes data from the FDA Recall Enterprise System (RES) and updates weekly. The FDA Enforcement Reports page says that a recall usually enters the report after FDA classifies the hazard. Classification waits until the firm sends all the information that FDA needs.

At 00:15 SGT we pulled every record from 15 weekly reports, from Aug 5, 2026 to Nov 11, 2026. That gave 333 food records and 302 drug records. We measured the days from recall_initiation_date to report_date.

The median gap for food records is 42 days. The 25th percentile is 27 days, the 75th percentile is 65 days, and the maximum is 259 days. No food record entered the report within 7 days. The median gap from recall start to FDA classification is 39 days. Drug records move faster, with a median of 27 days and a middle half between 23 and 34 days.

In October 2026 a Reddit user shared a merged FDA and USDA food recall feed on r/datasets. The post says that openFDA trails the actual recall by a median of 35 days across 441 records. For that reason the author also parses same-day press releases. His sample covers a different period, but both numbers are above one month.

Horizontal bar chart of days from recall start to the weekly report in openFDA enforcement data. Food: 25th percentile 27 days, median 42 days, 75th percentile 65 days. Drug: 25th percentile 23 days, median 27 days, 75th percentile 34 days. Sample: 333 food and 302 drug records from weekly reports between Aug 5 and Nov 11, 2026.

Records also arrive in batches. Of the 15 weekly reports, the smallest added 3 food records and the largest, on Oct 28, 2026, added 74. A system that polls openFDA weekly will push dozens of records in some weeks. Many of them belong to one event.

The 333 food records map to only 141 recall events. One event has 61 product records, and 32 events have more than one. Users care about "the product I bought". Group by event, match by product, and never turn 61 records into 61 alerts.

openFDA measure (Aug 5 to Nov 11, 2026) Food Drug
Records 333 302
Median days, recall start to report 42 27
Middle half of days 27 to 65 23 to 34
Records within 7 days 0 0
UPC or NDC mentioned 56.8% 74.5%
Lot or date wording 55.0% 93.7%

Column chart of new openFDA food enforcement records per weekly report from Aug 5 to Nov 11, 2026: 3, 35, 28, 25, 22, 19, 5, 48, 8, 14, 21, 7, 74, 12, 12. The largest week is Oct 28 with 74 records.

The openFDA documentation says that the data should not be used as a method to collect data to issue alerts to the public. It also says that the data should not be used to track the lifecycle of a recall. It adds that FDA does not update the status after classification, so the status stays unchanged after publication. Of our 333 food records, 314 say "Ongoing", 14 say "Terminated" and 5 say "Completed".

Our data does not match that sentence. In 12 of the 14 terminated records, termination_date is later than report_date. One record entered the report on Aug 19, 2026 and was terminated on Sep 18, 2026. So the status field does change after publication, but nobody promises when. An alert service cannot use it to decide whether a recall is still open.

For time-sensitive alerts, use the FDA Recalls, Market Withdrawals, and Safety Alerts list as the first source. Use the weekly report to fill in classes and gaps. For meat, poultry and egg products, also connect the USDA FSIS recalls and public health alerts. FSIS posted a Listeria alert on Nov 14, 2026 for meat products with FDA-regulated biscuits.

Source Our sample Update rhythm Gap or blind spot Role in an alert service
CPSC recall API 165 records, Aug 6 to Nov 12, 2026 With each notice CPSC warnings are missing Main consumer source; add the warnings page
openFDA food enforcement 15 weekly reports, 333 records Weekly Median 42 days from start to report Fill classes and gaps, not first alert
openFDA drug enforcement 15 weekly reports, 302 records Weekly Median 27 days Same as above
FDA recalls and safety alerts list Updated Nov 17, 2026 With press releases Not every recall has a release First alert; parse free text
USDA FSIS Latest alert Nov 14, 2026 With each notice Meat, poultry and eggs only Add for those categories
NHTSA vehicle recalls Lookup by VIN With each notice New recalls add VINs over time Match vehicles by VIN

Recalls get revised and expanded, so alerts need versions

Each CPSC record has a RecallDate and a LastPublishDate. In 35 of 165 records the two dates differ. In every case the gap is one day, which points to a small fix after publication. When CPSC expands a recall, it usually publishes a new notice.

On Oct 1, 2026, Agrish reannounced and expanded its recall of adult portable bed rails. The new notice covers about 35,083 units, of which about 5,000 were already recalled in January 2026. A system that deduplicates by recall number treats it as a new recall. A system that deduplicates by product misses the new models.

Do both. Store the new notice under its own number, and link it to the old notice by brand and model. The user then gets "The recall has expanded. It now adds models 12014 and 12016."

The openFDA documentation also says that FDA corrects earlier report entries, for example when a firm adds lots to a recall. News coverage shows the same pattern. At 00:26 SGT we called google_news/search for "product recall" in the U.S. over the past week. Of 20 results, 3 were updates to existing recalls.

Medline updated a recall of bed products. FDA moved an egg recall to its highest risk class. A Trader Joe's fried rice recall expanded to more products. These 3 updates matter most to people who already got a first alert. The system must detect "this revises an earlier recall" and notify only the affected users.

A good event key for a recall record combines the source agency and the source record ID. At each check, store a content hash and the changes to key fields. A wider scope needs a fresh match against all related items. A layout change needs no alert. A new remedy needs a correction to everyone who got the first alert.

Each alert should also record the version it came from. If a source page fails for a short time, show "check not finished". Never show "no new recalls". Our API error self-healing guide explains why timeouts, rate limits, permission errors and source errors need separate handling. In a recall service, a coverage gap must never look like a safe status.

We hit one such case in our own run. At 00:19 SGT the shared test key reached its limit of 10 calls per minute. The API returned 429 and charged nothing, and the retry at 00:26 SGT worked.

Change found at a check Example What the service does
New record number Agrish reannounces with more units Match all items again, link to the old notice
Scope widened New models or lots added Alert only the newly affected users
Remedy changed Refund added to a repair Send a correction to everyone already alerted
Risk class raised Egg recall moved to Class I Re-send at the higher priority
Text or layout fix LastPublishDate one day later Store the version, send nothing
Source fetch failed Timeout or 429 Show "check not finished"

Flow diagram of one run of a recall alert service in six steps. 1, pull official sources: CPSC, openFDA, NHTSA, Safety Gate. 2, version by record ID, with new, revised and expanded records handled apart. 3, extract identifiers: model, date code, lot, serial prefix. 4, match owned items into confirmed, possible or cannot tell; this step is highlighted. 5, tiered alert, action first and source second. 6, track remedy progress for refund, repair or replace. A dashed line runs from step 6 back to step 4.

Beyond the recall API: warnings and sources in other countries

CPSC publishes more than recalls. When a firm will not recall a product, CPSC can issue a unilateral warning. Warnings live under /Warnings/, apart from /Recalls/. On Nov 12, 2026, CPSC issued a warning about Bambora sling carriers and told consumers to stop using them at once.

We searched the full 10,089-record pull from Nov 18, 2026, and found no Bambora record. The latest title that starts with "CPSC Warns" dates from May 18, 2023. A service that reads only the recall API will miss the messages that call for the fastest action. The Boshengya rug recall from the same day appears in the API as expected.

Consumer goods, food, drugs, vehicles and foreign markets each have their own sources and legal rules. The openFDA food API keeps enforcement reports as a separate dataset. The example queries show filters by date range and class, and the drug enforcement endpoint uses the same shape. NHTSA handles vehicle recalls.

Its datasets and APIs page lists recall, investigation and complaint endpoints. Its recall lookup says that a VIN search may not show some new recalls whose VINs are not all identified yet. So for vehicles, a "no match" must state its date. Recalls.gov is a shared entry page from six federal agencies for people, not a single machine API.

Outside the U.S., the Health Canada recalls and safety alerts site updated on Nov 17, 2026. It showed 19,916 active and 14,466 archived records. Its open dataset offers daily CSV and JSON files. Of our 165 CPSC recalls, 22 were joint notices with Canada. In the EU, Safety Gate collects member-state alerts on dangerous non-food products.

The 2025 Safety Gate report says that national authorities can ask at any time to update a risk or product description. They can also withdraw an alert. Mason Hayes & Curran wrote on Mar 10, 2026 that 2025 set a record of 4,671 alerts. The UK lists product safety alerts, reports and recalls by category. The OECD GlobalRecalls portal puts recalls from many countries behind one search box.

China publishes recalls through the SAMR Defective Product Recall Technical Center (recall center site). The SAMR report on 2025 recalls, issued on Mar 15, 2026, counts 1,081 consumer product recalls covering 8.236 million units. It also counts 190 vehicle recalls covering 6.846 million vehicles.

A SAMR notice of Jun 12, 2025 on online sales asks producers to submit barcode data in their recall plans. Consumers can then scan a barcode and check the model, production date and lot. Compared with 2 barcodes in 165 CPSC records, that rule makes exact barcode matching far easier in China. Model and lot checks still matter.

Use one shared shell for internal data, and keep the source record as it is. Shared fields serve search and delivery. Source fields serve review. Keep a unified ID, the source agency, the source record ID, the notice date and the last check time. Keep the product name, brand, model, code, lot, sale region and sale period, and leave missing values empty.

Keep the hazard text, the remedy, the consumer contact and the link to the original notice. Keep the current status, the previous version, the field changes and any fetch failure. If a record has only free text, label it as free text. Do not invent a model number to make the database look tidy.

The marketplace side: what you can still find after a recall

Every CPSC recall page carries the same footer. Federal law prohibits any person from selling products subject to a Commission-ordered recall or a voluntary recall made in consultation with CPSC. The law is clear, but resale and third-party channels are hard to police. Scripps News reported on Oct 23, 2026 on a Consumer Reports study.

Investigators found all four banned or recalled baby product types for sale on Mercari, Craigslist, Facebook Marketplace and eBay. All four platforms got the lowest rating for catching unsafe listings before they go live. WFMY reported that the team stopped counting after 50 in-bed sleepers in 65 search results.

Third-party sellers also pull platforms into recalls. On Jul 30, 2024, CPSC decided that Amazon is a "distributor" of hazardous products that third-party sellers ship through Fulfilled by Amazon. Amazon must therefore notify buyers and support remedies. A site that counts retailers named in recall notices was covered by a trade report on Nov 15, 2026. From Jan 1 to Nov 10, 2026, FDA, USDA FSIS and CPSC published 826 recalls. Amazon was named in 336 of them, and 306 of those were CPSC recalls. The report headline uses a different count: among physical stores, Walmart was named most often, in 81 recalls. The Amazon figure sits in the body text. In our own 165-record sample, 92 (55.8%) name Amazon, which points the same way.

Our live calls answer a narrower question. After a recall, what do you find when you search marketplaces with the recall data? Across five recalls, we found 0 listings of the exact recalled model. This result has limits. One search shows only the first 10 to 20 results, and listings that omit the model do not show up.

At 00:35 SGT, walmart/search for "Expert Grill grill brush" returned 20 results. Seven were Expert Grill items, all in stock. No title matched a product name in the recall table, and every upc field was empty. Those 7 items are likely the bristle-free brushes that came after the recall. To be sure, someone must open each listing and read the model number.

A seller-side service can make this first pass routine. When a recall appears, search a few marketplaces with the model and the name. Sort hits into "title matches", "brand matches" and "no match". Then hand the list to the person who removes listings.

Users need the next step, not a summary

A good alert puts the action first. Typical actions are: stop using it, check the lot, contact the seller, get a refund or repair, or wait. The action must come from the current official notice. Do not let a model invent advice. In the RemedyOptions of our 165 recalls, 115 include a refund, 39 a repair and 19 a replacement. One recall can list more than one. The steps differ a lot.

3M asks for an online registration form. NEWDERY asks for a photo of the power bank with the word "recalled" written on it. Bose asks owners to remove the battery first, and the speaker still works on wall power. Copy these steps from the notice and show them as written. Fake recall texts are a related risk. A Jul 24, 2025 FTC consumer alert describes texts that pose as Amazon, say that an item "has been recalled", and offer a refund through a phishing link. A real alert should link to the official notice and never ask for payment or a password.

Horizontal bar chart of remedy options in 165 CPSC recalls from Aug 6 to Nov 12, 2026: refund 115, repair 39, replace 19. One recall can list more than one option.

Alert timing should depend on both risk and match confidence. Send a confirmed, high-risk match at once. Put a low-confidence possible match in a review queue, and update it when the user adds an identifier. A daily digest suits general monitoring.

Do not delay a clear safety alert just to send fewer messages. A USA Today recall guide from Oct 28, 2026 reminds readers that some recalls target retailers only, and some cover a short purchase window. A label typo and a deadly Listeria outbreak are both recalls. For the user, "does this affect me" and "how dangerous is it" are two separate questions.

A developer on r/SideProject described his food recall app in a post. He says that push alerts arrive 10 to 30 minutes after an announcement, and that the app scans barcodes to check lot codes. One commenter asked how much the push lags the FDA notice. Another asked for medical devices.

A separate post on r/newproducts pitches a service that saves owned items from photos and alerts on matching recalls. Both posts show demand for "push it to me". Neither gives a match accuracy or a false-alert rate.

Seller-side products also need internal tasks: stop sales, locate stock, find orders, contact affected customers and record the outcome. Data collection only triggers the task. It does not replace the seller's access control over orders, warehouses and customer identity. Our unified data API guide shows how to keep raw evidence, normalized fields and business actions in separate layers.

Registration sets the ceiling for matching

The information a user gives at sign-up limits every later match. If a user registers only "Bose speaker", the best alert says "You may be affected. Check under the battery." With the battery serial, the system can confirm or rule out the match. So the form should not be one product-name box.

Ask different questions by category. For small appliances, ask for the model and the date code on the bottom sticker. For batteries, ask for the serial. For baby products, ask for the model and the purchase date.

For food, ask for the barcode, lot and best-by date. For vehicles, ask for the VIN. Show a small picture of where each number usually sits.

Category What to ask for Where it usually is Example recall
Small appliance Model and date code Sticker on the bottom or side Love To Dream LTD-SM23
Battery pack Full serial Label under the pack Bose S1 Pro battery
Grill tool or kitchen item Model number Package or hang tag Walmart Expert Grill
Packaged food Barcode, lot, best-by date Back or bottom of the pack openFDA food records
Vehicle VIN Windshield base or door frame NHTSA lookup

Registration must also record the source and the time of each field. A model imported from an order email usually comes from the seller's title. It is less reliable than a number that the user copied from the item. The TL1302X and TL1302Z case shows that a seller title can carry a wrong suffix or no suffix. Tag each field with a source: order import, photo recognition, typed by the user, or confirmed by the user.

Let only confirmed fields count toward a confirmed match. Other fields can only lift a result to "possible". This rule produces fewer confirmed matches. But each confirmed match holds up under questions.

Treat used items apart. The Consumer Reports study and our Facebook Marketplace and eBay searches both show that resale titles rarely include lots or serials. A used item may already have gone through a recall refund with its first owner, or that owner may never have known. Ask "Did you buy this used?" at sign-up.

Put used items into "possible" at a lower evidence bar. The alert can say: "Used items may already have had the recall fix. Check the label first, then confirm with the maker."

Item source Field reliability Highest tier it can reach
Typed and confirmed by the user from the label High Confirmed
Read by OCR, then confirmed by the user High Confirmed
Read by OCR, not confirmed Medium Possible
Imported from an order email or seller title Low Possible
Bought used, no label data Low Cannot tell

A list of owned products is sensitive data

The items a household owns can reveal health, babies, home location and spending habits. A seller's stock and orders are business data. A recall alert product should not keep photos, receipts and full orders forever just because the purpose is safety. Version one can store only the fields needed for a match and let users delete them at any time.

Imports from email, orders or store accounts need clear consent. Show the scope of access, and tell users what stays stored after they stop a sync. Set a clear rule for whether a photo stays after recognition.

EU rules put part of this duty on companies. Article 35 of the General Product Safety Regulation (EU) 2023/988 requires economic operators to notify affected consumers directly. This applies to every consumer they can identify with the personal data they hold. Where they cannot reach everyone, they must spread a recall notice through other channels such as websites, social media and stores. Article 36 sets the required content of a written recall notice, and Implementing Regulation (EU) 2024/1435 gives a template.

A McDermott Will & Schulte analysis adds that Article 9(5) requires a type, batch or serial number on the product. It also notes that Article 37 normally requires a choice of at least two remedies among repair, replacement and refund. For recall alert teams, this means cleaner identifiers on EU products, and customer contact data that must follow data protection rules.

For sellers, split access to recall source data, internal SKU mappings and customer contact details. The person who checks recalls may not need full customer records. The person who sends alerts should not be able to change source evidence. The audit log should show who confirmed a match, which notice version they used, and which action went to which recipients.

Integration: three ways in and one cost estimate

Every live call in this article uses the EveryInfra data endpoint POST /api/v1/social. The request body has three parts: platform, action and params. The free catalog at GET /api/v1/social/catalog lists each capability with its parameters, response fields and price. Here is the eBay search from 00:16 SGT, with the key read from an environment variable:

curl -s -X POST https://api.everyinfra.com/api/v1/social \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"platform":"ebay","action":"search","params":{"keyword":"Scotch thermal laminator TL1302Z"}}'
Enter fullscreen mode Exit fullscreen mode

In the response, results is an array of listings. Each listing has item_id, title, url, price, condition, seller and other fields. count is the number of results, and billing.charged_usd is the actual charge, 0.001389 for this call. The walmart/search response adds a upc field, which was empty in all 20 Expert Grill results. The ebay/product_detail response has model, mpn and gtin fields.

Use it to open a "near model" hit and check it. In Claude, Cursor and other tools that support remote MCP, you can expose the same capabilities as tools. The model can then read a recall notice and search several marketplaces by itself. See the MCP setup page for the config:

{
  "mcpServers": {
    "everyinfra": {
      "url": "https://api.everyinfra.com/mcp",
      "headers": { "Authorization": "Bearer ${EVERYINFRA_API_KEY}" }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Failed and empty calls are free. The Walmart search at 00:19 SGT returned 0 results and charged_usd was 0. The rate-limited call that returned 429 was also free. For a first run, follow the quickstart to send one request. Then read the field notes for the eBay data API, the Walmart data API and the Amazon data API.

Horizontal bar chart of the price per 1,000 calls for each capability used in this article: amazon/search $2.236; walmart/search, ebay/search and facebook/marketplace $1.389 each; ebay/product_detail $0.958; google_news/search and reddit/search $0.792 each. Source: EveryInfra catalog price_usd times 1,000.

Time (SGT) Capability Query Results Charge (USD)
00:16 ebay/search Scotch thermal laminator TL1302Z 20 0.001389
00:16 walmart/search Scotch thermal laminator TL1302 20 0.001389
00:17 amazon/search Scotch thermal laminator TL1302Z 10 0.002236
00:18 ebay/search Bose S1 Pro battery pack 20 0.001389
00:18 facebook/marketplace Bose S1 Pro 20 0.001389
00:19 walmart/search Love To Dream portable sleep machine 0 0
00:19 ebay/search NEWDERY power bank ZHX-PB22 429 rate limit 0
00:26 ebay/search NEWDERY power bank ZHX-PB22 20 0.001389
00:26 ebay/product_detail eBay item 900079208872 1 0.000958
00:26 google_news/search product recall (U.S., past week) 20 0.000792
00:26 reddit/search recall alert app 4 0.000792
00:35 walmart/search Expert Grill grill brush 20 0.001389
00:35 amazon/search Bose S1 Pro battery 10 0.002236
00:36 walmart/search NEWDERY power bank 20 0.001389
Total 14 calls, 12 charged 0.016737

The cost table supports two conclusions. First, marketplace checks per recall do not grow with the number of users. CPSC published 521 recalls in 2026 up to Nov 12, which is 161 more than the 360 in the same period of 2025. That is about 50 recalls per month.

One search each on eBay, Walmart and Amazon costs $0.005014 per recall, or about $0.25 per month. Add one recall news search per day (30 × $0.000792, about $0.024), and the total is about $0.27 per month. Second, user-side matching runs in your own database. Ten thousand registered items cost the same in API fees as one hundred.

The real cost is in keeping extraction rules correct and in human review. The author of the r/datasets feed met the same issue. He tags hazard classes parsed from press releases as "inferred" and keeps them apart from official classes. A commenter asked for a confidence field.

The reddit/search call gave one more repeatable result. A search for "recall alert app" returned 4 posts, and none was about product recalls. "Recall" is the name of several apps. When you add social signals, pair recall keywords with a brand or a category, or same-name apps will fill the results.

Trends from autumn 2026

On Nov 5, 2026, Consumer Reports published "The Consumer Product Safety Commission Is Broken". The article says that the agency covers more than 15,000 product categories, and that many experts worry about its reduced capacity. The pace and depth of official notices may therefore change. Monitoring should detect signals such as "unusually few notices this week". Fewer notices do not mean fewer hazards.

On Nov 13, 2026, CDC closed its investigation of an E. coli outbreak linked to Graziers raw milk cheese. The CDC page says that the firm recalled all of the cheese on Sep 24, 2026. More than half of the sick people were children aged 5 or younger.

The FDA outbreak page warns that the cheese has a long shelf life and may still be in homes. The end of an outbreak does not make home stock safe. Alerts for long shelf-life products should stay active longer.

From Nov 13 to Nov 16, 2026, several recalls returned to the news as updates, expansions or upgrades. They were the Medline bed update, the egg recall upgrade and the Trader Joe's fried rice expansion. The ConsumerAffairs roundup of Nov 13, 2026 also lists about 2,960 recalled Cummins generators. The second alert is often more urgent than the first, so build version tracking into the first release.

Teams that sell into Spanish-speaking markets can start with two official sources. The Spanish food agency AESAN alert page posted an alert update on Nov 13, 2026. The Mexican consumer agency keeps a rapid alert network by category.

An MVP should test the full matching flow, not count notices

A safe pilot can cover one regulator, one product category and a small group of volunteer items. Review every candidate by hand first. Then see which fields make the system fail. At this stage, judge the pilot by whether it can explain each relevant alert, not by how many years of history it holds. Based on our data, a consumer pilot should start with CPSC recalls of the "model plus date code" kind. The identifiers are clear, users can check the label, and both false alerts and misses are easy to review.

Track four metrics. The first is the share of records you can match. The second is the fields that possible matches still need. The third is delivery and opening of confirmed alerts, and the fourth is the status from alert to finished remedy.

Review false alerts and misses apart. Also separate missing source fields, registration errors and rule errors. Only then do you know whether to fix data, the user flow or the rules.

We wrote four tests for this article before we pulled any data. Structured barcodes in under half of CPSC records: 1.2%, test passed. Median food delay of at least 7 days: 42 days, passed. At least one recalled model found on sale in a marketplace: 0 found in five recalls, so this test failed.

Near models outnumber exact models: 11 TL1302 variants to 0, passed. The 9 other NEWDERY products are the same brand but a different product, so they do not count as near models. The failed test shows that marketplace checks mainly rule items out and keep evidence. Expect them to catch a live recalled listing only some of the time.

This article describes a data product design. It does not mean that EveryInfra has launched a recall alert service. Teams that work on market intelligence can compare the same layered-evidence idea in our competitive intelligence data product article. A recall alert product must connect the official record, the specific item, the clear action and the later correction, and each step must be checkable.

We first published this article on Sep 5, 2026 and rewrote it on Nov 18, 2026. The original conclusions stay: tiered matching, "no match" is not "safe", recalls change, and an item list is sensitive data. The rewrite adds full counts from CPSC and openFDA, 14 live marketplace calls and the access cost, and removes claims that had no data behind them.

FAQ

Can a product recall notification service work in real time?

It can get close to the official release, but it cannot beat it. CPSC recalls reach the API with each notice. FDA food recalls arrive a median 42 days late if you rely only on the openFDA weekly report, based on our 333-record sample. Connect the same-day FDA recalls list to go faster. One developer on r/SideProject says his alerts arrive 10 to 30 minutes after an announcement, which depends on polling frequency.

Is there a free recall API?

Yes. The CPSC recall API, the openFDA enforcement endpoints, the NHTSA recall API and the Health Canada recall dataset are all free and public. You can try them without a key. Their field quality differs. The CPSC structured model field is empty in all 10,089 records, and the openFDA status field can change after publication with no promised timing. See the source table above.

How do I know if something I bought was recalled?

Read the model, date code, lot or serial on the product label. Then search the right agency's recall page by model. Consumer Reports also tells secondhand buyers to search recalls.gov by the exact product name or model. Do not decide on a brand or name match alone. The Bose battery recall, for example, depends on the first 6 digits of the serial.

What should a product recall notice include?

Article 36 of the EU General Product Safety Regulation lists the required content. It covers product identification, the hazard, the consumer action and the available remedy. Implementing Regulation (EU) 2024/1435 gives a template. CPSC notices follow a similar order: description, hazard, remedy, where sold and contact details. The action in an alert should copy the notice text.

How should a food recall notification app check lots?

Food recalls carry lots and barcodes more often than consumer goods. In openFDA food records, 56.8% mention a UPC and 55.0% mention a lot or a date term. An app can scan the barcode first to narrow the list. Then it asks the user to check the lot and date on the package. Send a confirmed alert only when both match.

References

  1. CPSC Recalls Application Program Interface (API) Information, U.S. Consumer Product Safety Commission, read 2026-11-18, https://www.cpsc.gov/Recalls/CPSC-Recalls-Application-Program-Interface-API-Information
  2. Recall Retrieval Web Services Programmer's Guide, U.S. Consumer Product Safety Commission, 2017-10-31, https://www.cpsc.gov/s3fs-public/RecallRetrievalWebServicesProgrammersGuide20171031.pdf
  3. CPSC Recalls REST endpoint (JSON), SaferProducts.gov, read 2026-11-18, https://www.saferproducts.gov/RestWebServices/Recall?format=json&RecallDateStart=2026-11-01
  4. 3M Company Recalls Scotch Thermal Laminators, CPSC, 2026-10-15, https://cpsc.gov/Recalls/2027/3M-Company-Recalls-ScotchTM-Thermal-Laminators-Due-to-Risk-of-Serious-Injury-or-Death-from-Fire-Hazard
  5. NEWDERY Power Banks Recalled, CPSC, 2026-09-24, https://cpsc.gov/Recalls/2026/NEWDERY-Power-Banks-Recalled-Due-to-Fire-and-Burn-Hazards-Risk-of-Serious-Injury-Sold-on-Amazon
  6. Love To Dream Recalls Portable Sleep Machines, CPSC, 2026-09-24, https://cpsc.gov/Recalls/2026/Love-To-Dream-Recalls-Portable-Sleep-Machines-Due-to-Risk-of-Injury-from-Fire-and-Burn-Hazards
  7. Bose Recalls Lithium-Ion Battery Packs for S1 Pro and S1 Pro+, CPSC, 2026-11-05, https://www.cpsc.gov/Recalls/2027/Bose-Recalls-Lithium-Ion-Battery-Packs-for-S1-Pro-and-S1-Pro-Bluetooth-Speaker-Systems-Due-to-Risk-of-Injury-from-Fire-and-Overheating-Hazards-0
  8. Walmart Recalls Over 4.4 Million Expert Grill Brushes, CPSC, 2026-10-01, https://www.cpsc.gov/Recalls/2027/Walmart-Recalls-Over-4-4-Million-Expert-Grill-Brushes-Due-to-Ingestion-Hazard
  9. Agrish Reannounces and Expands Recall of Adult Portable Bed Rails, CPSC, 2026-10-01, https://cpsc.gov/Recalls/2027/Agrish-Reannounces-and-Expands-Recall-of-Adult-Portable-Bed-Rails-Due-to-Risk-of-Serious-Injury-or-Death-from-Entrapment-and-Asphyxiation-Violate-Mandatory-Standard-for-Adult-Portable-Bed-Rails-Additional-Units-Added
  10. CPSC Warns Consumers to Stop Using Bambora Sling Carriers, CPSC, 2026-11-12, https://www.cpsc.gov/Warnings/2027/CPSC-Warns-Consumers-to-Stop-Using-Bambora-Sling-Carriers-Immediately-Due-to-Risk-of-Serious-Injury-or-Death-from-Fall-Hazard-Violate-Mandatory-Standard-for-Sling-Carriers
  11. Boshengya Recalls Rugs, CPSC, 2026-11-12, https://www.cpsc.gov/Recalls/2027/Boshengya-Recalls-Rugs-Due-to-Risk-of-Serious-Injury-or-Death-from-Fire-Hazard-Violate-Mandatory-Standard-for-Carpets-and-Rugs
  12. CPSC Finds Amazon Responsible Under Federal Safety Law, CPSC, 2024-07-30, https://www.cpsc.gov/Newsroom/News-Releases/2024/CPSC-Finds-Amazon-Responsible-Under-Federal-Safety-Law-for-Hazardous-Products-Sold-by-Third-Party-Sellers-on-Amazon-com
  13. Food Enforcement Overview, openFDA, read 2026-11-18, https://open.fda.gov/apis/food/enforcement/
  14. Food API, openFDA, read 2026-11-18, https://open.fda.gov/apis/food/
  15. Food enforcement example API queries, openFDA, read 2026-11-18, https://open.fda.gov/apis/food/enforcement/example-api-queries/
  16. Drug Enforcement API, openFDA, read 2026-11-18, https://open.fda.gov/apis/drug/enforcement/
  17. Recall Enterprise System (RES), openFDA, read 2026-11-18, https://open.fda.gov/data/res/
  18. Enforcement Reports, U.S. Food and Drug Administration, read 2026-11-18, https://www.fda.gov/safety/recalls-market-withdrawals-safety-alerts/enforcement-reports
  19. Recalls, Market Withdrawals, & Safety Alerts, U.S. Food and Drug Administration, updated 2026-11-17, https://www.fda.gov/safety/recalls-market-withdrawals-safety-alerts
  20. Outbreak Investigation of E. coli O26:H11: Raw Milk Cheese, U.S. Food and Drug Administration, 2026-11-13, https://www.fda.gov/food/outbreaks-foodborne-illness/outbreak-investigation-e-coli-o26h11-raw-milk-cheese-september-2026
  21. E. coli Outbreak Linked to Raw Milk Cheese, U.S. Centers for Disease Control and Prevention, 2026-11-13, https://www.cdc.gov/ecoli/outbreaks/raw-milk-cheese-09-26/index.html
  22. Recalls & Public Health Alerts, USDA Food Safety and Inspection Service, 2026-11-14, https://www.fsis.usda.gov/recalls
  23. NHTSA Datasets and APIs, National Highway Traffic Safety Administration, read 2026-11-18, https://www.nhtsa.gov/nhtsa-datasets-and-apis
  24. Check for Recalls: Vehicle, Car Seat, Tire, Equipment, NHTSA, read 2026-11-18, https://www.nhtsa.gov/recalls
  25. Recalls.gov, six U.S. federal agencies, read 2026-11-18, https://www.recalls.gov/
  26. Find recalls, advisories and safety alerts, Health Canada, 2026-11-17, https://recalls-rappels.canada.ca/en
  27. Recalls and Safety Alerts dataset, Open Government Portal of Canada, read 2026-11-18, https://open.canada.ca/data/en/dataset/d38de914-c94c-429b-8ab1-8776c31643e3
  28. Safety Gate: the EU rapid alert system, European Commission, read 2026-11-18, https://ec.europa.eu/safety-gate-alerts/
  29. Safety Gate 2025 report, European Commission DG JUST, 2026-03, https://op.europa.eu/webpub/just/safety-gate-2025-report/en/
  30. Regulation (EU) 2023/988 on general product safety, EUR-Lex, 2023-05-10, https://eur-lex.europa.eu/eli/reg/2023/988/oj/eng
  31. Implementing Regulation (EU) 2024/1435, recall notice template, EUR-Lex, 2024-05-24, https://eur-lex.europa.eu/eli/reg_impl/2024/1435/oj/eng
  32. Product Safety Alerts, Reports and Recalls, UK Government, read 2026-11-18, https://www.gov.uk/product-safety-alerts-reports-recalls
  33. OECD GlobalRecalls portal, OECD, read 2026-11-18, https://globalrecalls.oecd.org/
  34. SAMR report on 2025 vehicle and consumer product recalls (reposted by the Hunan provincial government), 2026-03-15, https://hunan.gov.cn/zqt/zcsd/202603/t20260320_33937982.html
  35. SAMR notice on recall supervision for online sales (reposted by MOFCOM), 2025-06-12, https://policy.mofcom.gov.cn/claw/clawContent.shtml?id=102854
  36. SAMR Defective Product Recall Technical Center, read 2026-11-18, https://www.samrdprc.org.cn/
  37. Alertas alimentarias, Spanish Agency for Food Safety and Nutrition (AESAN), 2026-11-13, https://www.aesan.gob.es/alertas/alertas-alimentarias
  38. Red de Alerta Rápida, Mexican Federal Consumer Protection Agency (PROFECO), read 2026-11-18, https://alertas.gob.mx/
  39. Commission Presents Safety Gate Report for 2025, Mason Hayes & Curran, 2026-03-10, https://www.mhc.ie/latest/insights/commission-presents-safety-gate-report-for-2025
  40. The GPSR in practice, McDermott Will & Schulte, 2026-11, https://www.mcdermottlaw.com/insights/the-general-product-safety-regulation-gpsr-in-practice-how-the-eus-new-regime-is-reshaping-recall-communications-and-manufacturer-obligations/
  41. The Consumer Product Safety Commission Is Broken, Consumer Reports, 2026-11-05, https://www.consumerreports.org/product-safety/dangerous-products-cpsc-cuts-a1128194170/
  42. Bose S1 Pro speaker batteries recalled due to fire risk, Consumer Reports, 2026-11, https://www.consumerreports.org/electronics/electronic-product-recalls/bose-s1-pro-speaker-batteries-recalled-due-to-fire-risk-a1247615920/
  43. Bose recalls over 670,000 S1 Pro speaker batteries, Android Authority, 2026-11-17, https://www.androidauthority.com/bose-s1-pro-bluetooth-speaker-battery-recall-3735448/
  44. Interactive: The used baby gear you're buying online may have been recalled, Scripps News, 2026-10-23, https://www.scrippsnews.com/life/money/interactive-the-used-baby-gear-youre-buying-online-may-have-been-recalled
  45. Has your Marketplace item been recalled?, WFMY News 2, 2026-10, https://www.wfmynews2.com/article/news/local/2-wants-to-know/has-your-marketplace-item-been-recalled-consumer-reports-finds-recalled-baby-items-for-sale-facebook-ebay-craigslist-mercari-illegal-to-sell-check/83-b74381f9-6176-4f8a-b393-e9d1c7e58d9e
  46. A consumer's guide to recalls, USA Today, 2026-10-28, https://www.usatoday.com/story/money/consumer-protection/recalls-alerts/2026/10/28/recalls-consumers-guide/92399401007/
  47. Walmart Leads 2026 Store Recalls With 81 Notices, Food & Beverage Magazine, 2026-11-15, https://www.fb101.com/store-recalls-walmart-81-recalls-2026-retailer-report-302938913
  48. Consumer product safety recall roundup for November 13, 2026, ConsumerAffairs, 2026-11-13, https://www.consumeraffairs.com/news/consumer-product-safety-recall-roundup-for-november-13-2026-111326.html
  49. Medline updates recall on all bed-related products, LiveNOW from FOX, 2026-11-15, https://www.livenowfox.com/news/medline-updates-recall-all-bed-related-products-reported-deaths-climb
  50. Egg recall upgraded to highest risk level, ABC News, 2026-11-16, https://abcnews.com/GMA/Food/19-million-eggs-voluntarily-recalled-potential-salmonella-contamination/story?id=135028861
  51. Trader Joe's frozen fried rice recall expands, ABC News, 2026-11-16, https://abcnews.com/GMA/Food/trader-joes-frozen-fried-rice-recall-expands-products/story?id=130754612
  52. Free JSON feed of all active US food recalls, Reddit r/datasets, 2026-10, https://www.reddit.com/r/datasets/comments/1wmkoql/free_json_feed_of_all_active_us_food_recalls_fda/
  53. I built a real-time FDA recall tracker, Reddit r/SideProject, 2026, https://www.reddit.com/r/SideProject/comments/1wj1jqo/i_built_a_realtime_fda_recall_tracker_because_i/
  54. Stop guessing! We alert you when anything you own is recalled, Reddit r/newproducts, 2026, https://www.reddit.com/r/newproducts/comments/1w5fhen/stop_guessing_we_alert_you_when_anything_you_own/
  55. Scammy texts offering "refunds" for Amazon purchases, U.S. Federal Trade Commission, 2025-07-24, https://consumer.ftc.gov/consumer-alerts/2025/07/scammy-texts-offering-refunds-amazon-purchases

Originally published on the EveryInfra blog: Product Recall Data as a Notification Service: From Notices to Affected Batches. This article was written with AI assistance; the numbers come from the API calls and sources linked above, and were checked before publishing.

EveryInfra is a pay-per-call data API for AI agents and developers: everyinfra.com.

Top comments (0)