A closed case is not the end of the record.
Handle amended notices without losing the decisions your team already made.
A notice can be older than the item on your shelf and still change today. Monitor the source publication history as well as the original recall date.
Separate three different dates
The original recall date tells you when a notice was issued. CPSC's last-published date can be later. Recall Ledger's observation time tells you when this dataset actually retrieved the record. None of those is the date your staff inspected a physical item. Keep review decisions on their own timeline.
For example, the CPSC API returned recall 01130 with an original date in 2001 and a last-published date in February 2026 during development. This proves that a filter for recent original recall dates alone can miss an older record's later publication. It does not prove that the underlying hazard or applicability changed on that date.
Compare evidence, not just timestamps
Recall Ledger compares the title, description, product and model fields, manufacturer information, UPCs, hazards and remedies. A change to that evidence creates a new source fingerprint. Changes only to images, contacts or publication timestamps do not reopen a case. This reduces repeat work from metadata updates while retaining a reason to revisit meaningful evidence.
A closed case with changed source evidence returns to Review. Holds and remedy tracking retain their current status and get a dated source-change entry. A previously created case remains traceable even if the revised notice no longer produces the same automatic text candidate.
Inspect the changed notice before deciding again
Reopening is a request to inspect, not a finding that the item is affected. Compare the official notice to the label and the reason the case was previously closed. A newly included model, clarified serial range or changed remedy may matter. Document the new decision separately so the original reasoning is not overwritten.
At present, this app shows the current public evidence and your prior decisions. It does not display a certified redline of every historical official webpage. The refresh collector retains source snapshots privately for operational investigation; those snapshots do not contain your browser inventory.
Plan for gaps and interruptions
The collector retains the last successful dataset if a source request fails. The app displays refresh failures and marks observations older than 48 hours as stale. Keeping old evidence visible is useful; presenting it as current is not. Check the official source if freshness is uncertain.
The open app checks for a newer published dataset every five minutes. If it finds one, it reconciles your locally saved cases and shows an in-app message. There are no email or phone alerts, and closing the browser stops these private-inventory checks. The public RSS feed contains source observations only, never private matches.
Make the handover portable
Export the backup before changing devices or clearing browser data. A backup includes the inventory and case notes, so treat it as a private business record. Import it only into a trusted browser. A CSV inventory export does not replace the JSON backup because CSV omits the review history.
Do not use a closed status, a clean-looking queue or an old export to assert that an item is safe. These are records of a bounded checking process. The official notice and the merchant's wider duties remain the reference for action.
Primary sources: CPSC API programmer's guide; CPSC recall 01130; Official CPSC recall search.