--- title: "CPSC recall dates: publication updates and store reviews" description: "Separate CPSC recall and publication dates from retrieval, catalog exports, and store decisions. Preserve changes and gaps in earlier source evidence." canonical: "https://scalewithsearch.com/articles/cpsc-recall-publication-dates-review-history" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # CPSC recall dates: keep the announcement, publication update, and store review separate A recall date, a publication timestamp, and a store decision date describe different observations. Put them in separate fields before comparing two reviews. Otherwise, a fresh download can look like a new recall, or an old store decision can appear current. The practical task is preserving what the reviewer saw. Record the official source values, the retrieval time, the catalog export used, and the decision that followed. When evidence is missing, describe the gap directly. This guide proposes a manual review history for merchandising and product-safety staff. Its dates and store records are synthetic. They illustrate documentation choices without claiming that a particular notice changed on those dates. For broader context, see the [retail and ecommerce page](/for/retail-and-ecommerce) and the [retail intelligence overview](/intelligence/retail-and-ecommerce). This article concerns evidence chronology. The companion [product-model and retail-SKU guide](/articles/cpsc-recall-model-match-retail-sku) explains the separate task of establishing product identity. ## Preserve the official field names The [CPSC retrieval guide, version 1.3](https://www.cpsc.gov/s3fs-public/RecallRetrievalWebServicesProgrammersGuide20171031.pdf), lists RecallID, RecallNumber, RecallDate, LastPublishDate, and URL among its returned fields. It also lists separate search parameters for recall dates and last-publication dates. Preserve those distinctions in your review record. Use RecallID and RecallNumber as separate source references. Retain URL as the route back to the notice. Copy RecallDate and LastPublishDate under their original names. Do not rename both values “updated” in the store worksheet. The guide lists fields and examples without providing a complete account of every publication event. It does not establish which substantive change caused a particular LastPublishDate value. Treat the reason for an observed date difference as unknown until supported by notice text or other official evidence. Use the date displayed on the official notice as the notice's stated recall date. For example, the [CPSC RSX luminaire notice](https://www.cpsc.gov/Recalls/2027/Lithonia-Lighting-Recalls-RSX-Luminaires-with-Adjustable-Tilt-Arm-Mountings-Due-to-Risk-of-Serious-Injury-from-Impact-Hazard) displays October 22, 2026. That observation does not establish when a store learned about it or reviewed its inventory. If the API and page appear inconsistent, preserve both readings with their source references. Ask the responsible reviewer to resolve the discrepancy. Do not silently substitute whichever date looks newer. ## Give each store event its own date Use retrieval time for the moment your process obtained the source. Use review time for the moment a person inspected it. Use decision time for the recorded conclusion. These events can occur together, but the record should not assume that they did. The catalog export has another timestamp. It describes the store data supplied for comparison. A notice retrieved today can still be compared against yesterday's catalog. A later review does not make that catalog export current. The following timeline is entirely hypothetical. The placeholders for source identifiers do not refer to a real CPSC notice. | Record field | Synthetic value | What it represents in this example | | --- | --- | --- | | RecallID | Example identifier A | Source-record reference, copied independently | | RecallNumber | Example notice number B | Notice reference, kept separately from RecallID | | URL | Official notice link would be copied here | Source location, not a saved historical copy | | RecallDate | 2026-09-10 | Official field value observed in this example | | LastPublishDate | 2026-10-06T00:00:00 | Official field value preserved without adding a time zone | | Retrieved at | 2026-10-07T13:15:00Z | Time the store obtained this example source copy | | Catalog exported at | 2026-10-07T11:00:00Z | Time attached to the catalog used for comparison | | Reviewed at | 2026-10-07T15:00:00Z | Time the responsible reviewer inspected the evidence | | Decision recorded at | 2026-10-07T15:20:00Z | Time the reviewer entered the unresolved label question | Keep the original source timestamp even if your worksheet also provides a readable display. Where a source value has no time-zone suffix, do not append one by guesswork. Use explicit time zones for timestamps your store records itself. Distinguish scheduled checks from completed retrievals. A calendar entry for Monday morning proves that someone planned a check. It does not prove that the source opened successfully or that a reviewer read it. ## A publication difference starts a reading task Suppose a second retrieval shows a different LastPublishDate value. Begin by opening the current official notice. Compare the relevant identification details and instructions against the evidence retained from the earlier review. Do not write “recall expanded” from the date field alone. Do not write “remedy changed” without inspecting the text. The date difference identifies a reason to investigate, while the content comparison supplies the explanation. The [CPSC recall index](https://www.cpsc.gov/Recalls) notes that remedy data may change with company operating status or remedy availability. This supports checking current instructions. It does not tell you why a specific API timestamp changed or prove that an affected product list grew. Use separate observation and interpretation sentences. An observation might say that the stored timestamp differs from the current timestamp. An interpretation might identify a specific changed instruction after comparison. Cite the saved copies supporting each statement. If the current page gives no explanation, keep the reason unknown. The reviewer can still inspect its current instructions and assess the store's next step. Uncertainty about history does not justify inventing a history. ## Write a before-and-after note when both copies exist Consider a hypothetical review with two saved source copies, labeled A and B. Copy A was retrieved on October 7. Copy B was retrieved on October 14. Both labels are store references, not official CPSC version numbers. Start the note by identifying the two files and their retrieval times. Record the source identifiers attached to each. Then specify which parts the reviewer compared, such as product descriptions, model lists, production periods, and remedy wording. A useful synthetic observation reads: “The inspected model list is unchanged between saved copies A and B. The publication value differs.” That wording limits the finding to the sections inspected. It does not claim the entire notice remained unchanged. If an instruction differs, describe the difference in plain language with a reference to both copies. Keep any quotation short and exact. Do not smooth two instructions into a new composite instruction that neither source contains. Next, record the review implication. Perhaps the identity evidence remains the same, but the responsible reviewer needs to reconsider the current instructions. The record should distinguish that pending review from a completed store action. Finish with the reviewer, the review date, and unresolved questions. If another person must confirm a label, name that role and the missing evidence. Leave the earlier decision visible as a decision made against copy A. ## Preserve unknowns when the earlier version was never saved Now consider a different hypothetical case. The store retains an October 7 spreadsheet row and a notice URL. It did not save the notice text. On October 14, a reviewer opens the URL again. The current page cannot establish what the earlier page contained. A stored link identifies a source location, not the text available at an earlier visit. The previous reviewer might have written a useful summary, but that summary has a narrower evidentiary scope. Write the limitation directly: “Earlier notice text was not retained. Current source inspected October 14. Changes to the earlier wording cannot be established from this record.” This is a synthetic note, not a statement about an actual CPSC publication. If the spreadsheet retained an earlier LastPublishDate, compare that value with the current observation. You can report the difference between the recorded values. You still cannot infer which paragraph changed without supporting evidence. Keep the earlier decision and its stated basis. Mark the source-copy gap beside it. Do not backfill the old row with today's text, because that would make the record appear more complete than it was. When a recollection conflicts with the saved note, preserve the conflict for review. Label recollections as recollections. Ask the responsible reviewer to assess the current notice without presenting an uncertain memory as a historical source. ## Keep the catalog snapshot attached to the decision A recall review compares two changing bodies of evidence: the public notice and the store's own product records. Preserve both references. Otherwise, a later reader may assume that the review covered stock or variants added afterward. In a synthetic example, the first export contains `STORE-417` with no lot information. A later export adds the lot field after a label inspection. The second review now has evidence the first reviewer lacked. Record that improvement as a store evidence change. Do not attribute it to a publication update merely because the notice was also retrieved again. The worksheet should let a reader distinguish changes in the source notice from changes in the catalog. Keep the original export timestamp beside any inventory quantity. A newer decision date does not refresh that quantity. If the decision needs current stock information, obtain it through the store's approved inventory process. Use product references without copying customer records into the review history. The task concerns notice evidence, catalog identity, and the responsible person's decision. Customer communications or other actions require their own authorized records. ## Make the handoff state explicit At each handoff, separate the latest successful retrieval from the latest completed human review. A source check can finish while a label question remains open. A review can also remain pending after someone saves a new notice copy. If retrieval fails, record the failure time and the last successful source reference. Do not advance the “current source checked” date. A failed request cannot support a conclusion that nothing changed. Use a short status sentence that names the missing step. “Current notice saved; physical lot check pending” is more useful than “updated.” It tells the next reviewer what exists and what still requires work. The [Product recall finder](/tools/product-recall-finder) is a separate starting point for public research. Read its current limits before relying on a search. Your store history should retain the official evidence and review dates needed for the decision. Keep those records in a location your business controls. The [business memory guide](/articles/business-memory-for-ai-agents-guide) explains how reusable records survive individual sessions. For recall work, reuse should carry source dates and unresolved questions forward, rather than copying an old conclusion without context. ## Choose a clear first review record Start with one notice and one catalog comparison your responsible reviewer can inspect. Fill the date fields from the evidence available. Leave unavailable values explicitly unknown instead of estimating them to complete the form. Ask a second staff member to read the record as a handoff. They should be able to identify the inspected notice, catalog export, last decision, and outstanding question. If those answers require oral explanation, improve the record before expanding its scope. For implementation help, bring Scale With Search a non-sensitive example showing the current record and the desired handoff. Use the [written scope process](/work) to define the work and responsibilities. Source interpretation and product actions remain with the responsible human. ## Source note Sources were reopened on 2026.10.28. The [CPSC API information page](https://www.cpsc.gov/Recalls/CPSC-Recalls-Application-Program-Interface-API-Information) linked an older guide with a version 1.1 cover and version 1.2 footers. Version 1.3 is separately available and dated October 31, 2017. The guides identify date fields but do not document every event that changes publication values. The recall index and linked luminaire notice were also inspected. All timelines, comparisons, and proposed store procedures above are synthetic editorial examples, not reconstructed historical notices or legal advice. Continue the website review: [AI-native retail and ecommerce: the first functions to build](/articles/ai-native-retail-first-functions); [Brick-and-mortar business: plan the website around visits](/articles/brick-and-mortar-store-website-plan); [CPSC recall matching: compare a product model with your retail SKU](/articles/cpsc-recall-model-match-retail-sku); [Dealer SEO: make vehicle inventory pages useful](/articles/dealer-seo-inventory-page-checklist); [Google Business Profile products: check the right editor](/articles/google-business-profile-products-or-services); [Fix a Merchant Center price mismatch on your store site](/articles/merchant-center-price-mismatch-store-website); [Retail and ecommerce AI rules: data, approvals, and spend](/articles/retail-ai-rules-data-approvals-spend); [Retail gift bundles in Merchant Center: what to submit](/articles/retail-gift-bundles-merchant-center); [Store guest checkout: check Google's requirements](/articles/retail-guest-checkout-google-requirements); [Fix a Merchant Center availability mismatch](/articles/retail-merchant-center-availability-mismatch); [Missing GTIN in Merchant Center: check before you guess](/articles/retail-merchant-center-missing-gtin); [Fix a rejected product image in Merchant Center](/articles/retail-merchant-center-product-image-disapproval); [Fix a Merchant Center shipping cost mismatch](/articles/retail-merchant-center-shipping-cost-mismatch); [Merchant Center website verification and claim problems](/articles/retail-merchant-center-website-verification-claim); [Product variants not grouped in Merchant Center](/articles/retail-product-variants-merchant-center-grouping); [Make store pickup instructions match your Google listing](/articles/retail-store-pickup-website-google-check); [Fix a store return policy that appears wrong on Google](/articles/store-return-policy-wrong-google). [retail stores and ecommerce sellers](/for/retail-and-ecommerce): website and search resources. ## Related: retail stores and ecommerce sellers - [Dealer SEO: make vehicle inventory pages useful](/articles/dealer-seo-inventory-page-checklist) - [Google Business Profile products: check the right editor](/articles/google-business-profile-products-or-services) - [Fix a Merchant Center price mismatch on your store site](/articles/merchant-center-price-mismatch-store-website) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```