JAZ-X Product Recall Manager for WooCommerce gives store owners a structured workflow for product safety recalls.<\/p>\n\n
Free 1.0.0 includes:<\/p>\n\n
Internal audit log foundation.<\/p><\/li>\n
Provider-agnostic Purchase Source Adapter API for verified external buyers.<\/p><\/li>\n
Purchase Sources admin screen shows only registered verified sources, without requiring provider-specific branding.<\/p><\/li>\n
Deep Transaction Discovery using exact product title, slug, SKU or product URL; numeric-only IDs are ignored.<\/p><\/li>\n
JAZ-X Product Recall Manager does not determine whether a product is legally subject to a recall. Store owners remain responsible for verifying recall information and legal obligations.<\/p>\n\n
Integrations may register a callback-backed verified purchase source:<\/p>\n\n
add_action( 'recallsafe_register_purchase_sources', function ( $registry ) {\n $registry->register_callback_source(\n 'my_external_source',\n 'External verified purchase source',\n function ( $context ) {\n \/\/ Query your own system and return only independently verified buyers.\n return array();\n }\n );\n} );\n<\/code><\/pre>\n\nOr use the generic hook-backed adapter:<\/p>\n\n
add_filter( 'recallsafe_external_verified_matches', function ( $records, $context ) {\n \/\/ Return only provider-verified records for the supplied product fingerprints.\n return $records;\n}, 10, 2 );\n<\/code><\/pre>\n\nA verified record requires source_record_id<\/code> and customer_email<\/code>. Optional fields are customer_id<\/code>, customer_name<\/code>, quantity<\/code>, purchased_at<\/code>, verification_method<\/code>, and product_reference<\/code>.<\/p>\n\nAdapter SDK v2 Example<\/h3>\n\nadd_action( 'recallsafe_register_purchase_sources', function ( $registry ) {\n $registry->register_callback_source(\n 'verified_external_commerce',\n 'External verified purchase source',\n function ( $context ) {\n $records = array();\n foreach ( RecallSafe_Adapter_SDK::products_from_context( $context ) as $product ) {\n \/\/ Query your own trusted system using the product fingerprint.\n \/\/ Only return a row after your integration has verified ownership.\n }\n return $records;\n }\n );\n} );\n<\/code><\/pre>\n\nBuild records with RecallSafe_Adapter_SDK::verified_record()<\/code>. Required fields remain source_record_id<\/code> and customer_email<\/code>. Recommended fields are verification_method<\/code>, product_reference<\/code>, purchased_at<\/code>, and, for access-based products, entitlement_status<\/code> and entitlement_expires<\/code>. Provider-specific API credentials, webhook secrets and private implementation details must stay in the integrating system.<\/p>\n\n\n\n- Upload the
jaz-x-product-recall-manager-for-woocommerce<\/code> folder to \/wp-content\/plugins\/<\/code> or install the ZIP from Plugins > Add New > Upload Plugin.<\/li>\n- Ensure WooCommerce is installed and active.<\/li>\n
- Activate JAZ-X Product Recall Manager for WooCommerce.<\/li>\n
- Go to JAZ-X Recalls > Add Product Recall.<\/li>\n
- Add recall details and link the affected WooCommerce products.<\/li>\n
- Go to JAZ-X Recalls > Affected Customers and run Scan \/ Rescan Orders.<\/li>\n<\/ol>\n\n\n
\nDoes JAZ-X Product Recall Manager automatically contact government recall databases?<\/h3><\/dt>\nNot in Free 1.0.0. This release focuses on the store-side recall workflow, manual verified recall records, and provider-neutral purchase-source adapters.<\/p><\/dd>\n
Does it support WooCommerce HPOS?<\/h3><\/dt>\nThe plugin declares HPOS compatibility and uses WooCommerce order APIs rather than directly querying legacy order post tables.<\/p><\/dd>\n
Can another checkout, licensing, membership, marketplace, or download system integrate with JAZ-X Product Recall Manager?<\/h3><\/dt>\nYes. Version 0.4.0 adds a provider-agnostic Purchase Source Adapter API. Integrations can register an object implementing RecallSafe_Purchase_Source_Interface<\/code>, register a callback source through the registry, or supply verified rows through the recallsafe_external_verified_matches<\/code> filter. JAZ-X Product Recall Manager core does not need to know the provider implementation.<\/p><\/dd>\nWhat must an external adapter return?<\/h3><\/dt>\nEach verified row must include a stable source_record_id<\/code> and a valid customer_email<\/code>. Optional fields include customer_id<\/code>, customer_name<\/code>, quantity<\/code>, purchased_at<\/code>, verification_method<\/code>, and product_reference<\/code>. The adapter is responsible for verifying that the buyer belongs to one of the product fingerprints supplied in the scan context.<\/p><\/dd>\nDoes it automatically email customers?<\/h3><\/dt>\nJAZ-X Product Recall Manager can send a manual safety notification to a verified affected customer and includes a no-send preview. Draft and Reviewing recalls cannot send live notifications.<\/p><\/dd>\n
Does uninstalling delete recall records?<\/h3><\/dt>\nNo. Safety and audit-related data is intentionally not automatically deleted on uninstall.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.4<\/h4>\n\n\n- Documented the activation-only SHOW INDEX query as using a trusted schema identifier derived only from $wpdb->prefix and a fixed suffix.<\/li>\n
- No functional behavior changed from 1.0.3.<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Marked activation-only schema verification queries as intentional direct database checks for WordPress coding standards.<\/li>\n
- No functional behavior changed from 1.0.2.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Renamed the public plugin identity to JAZ-X Product Recall Manager for WooCommerce and updated the WordPress.org text domain\/package slug.<\/li>\n
- Moved admin JavaScript out of inline script tags and into a properly enqueued admin asset.<\/li>\n
- Passed scan runtime data to JavaScript through WordPress localization instead of interpolating PHP values into a script block.<\/li>\n
- Reduced the composite unique-index prefix lengths for compatibility with older WordPress-supported MySQL\/InnoDB index limits.<\/li>\n
- Database version is now recorded only after the required tables and unique index are verified.<\/li>\n
- Existing RecallSafe database\/meta keys and developer hooks are intentionally preserved for backward compatibility and existing data.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Removed the duplicate Plugin URI header so Plugin URI and Author URI no longer conflict during WordPress.org validation.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First stable Free release.<\/li>\n
- Finalized the professional Add\/Edit Recall, Product Recalls, Affected Customers, Purchase Sources, audit, and quarantine interfaces.<\/li>\n
- Includes provider-neutral purchase-source adapters, strict external-buyer verification, quarantine safeguards, manual safety notifications, no-send email preview, and resolution tracking.<\/li>\n
- Reworked the quarantined-record removal control for reliable visible rendering.<\/li>\n
- Declares WooCommerce HPOS compatibility and uses WooCommerce order APIs for order scanning.<\/li>\n
- Preserves recall, affected-customer, quarantine, and audit data on uninstall; safety records are not deleted automatically.<\/li>\n
- Release packaging, readme, version, stable-tag, translation-domain, and Plugin Check cleanup completed.<\/li>\n<\/ul>\n\n
0.5.10<\/h4>\n\n\n- Made the quarantined-record removal action render as a plain, reliable text button.<\/li>\n
- Added explicit spacing between the Recent Audit Activity title and event-count badge.<\/li>\n<\/ul>\n\n
0.5.9<\/h4>\n\n\n- Added direct-access protection to the provider-neutral adapter example.<\/li>\n
- Documented and scoped Plugin Check handling for validated dynamic database identifiers used by external-source discovery.<\/li>\n
- Kept value parameters prepared and existing strict source-validation safeguards unchanged.<\/li>\n<\/ul>\n\n
0.5.8<\/h4>\n\n\n- Reworked bounded post-meta discovery to use fixed prepared statements and remove dynamic IN-clause prepare warnings.<\/li>\n<\/ul>\n\n
0.5.7<\/h4>\n\n\n- Fixed the remaining Plugin Check translators-comment error in payment evidence diagnostics.<\/li>\n
- Corrected the plugin header version to match the runtime version.<\/li>\n<\/ul>\n\n
0.5.6<\/h4>\n\n\n- Added the two remaining translator comments for payment-evidence placeholder strings reported by Plugin Check.<\/li>\n<\/ul>\n\n
0.5.4<\/h4>\n\n\n- Polished Affected Customers audit and quarantine panels.<\/li>\n
- Improved audit event badge spacing and card consistency.<\/li>\n
- Restored a prominent, reliable Remove permanently quarantine action.<\/li>\n<\/ul>\n\n
0.5.3<\/h4>\n\n\n- Redesigned Add\/Edit Recall screen with professional card layout, summary metrics, responsive sections, numbered product selection, and checkboxes.<\/li>\n
- Added serial numbers and selection checkboxes to the Product Recalls list.<\/li>\n<\/ul>\n\n
0.5.0<\/h4>\n\n\n- Professional admin UI\/UX polish across recall management screens.<\/li>\n
- Added scan summary metric cards for orders, affected units, external signals, and verified external buyers.<\/li>\n
- Moved technical scan output into a collapsed Advanced diagnostics panel.<\/li>\n
- Improved responsive layout, spacing, typography, cards, toolbars, tables, empty states, and audit presentation.<\/li>\n
- Kept provider-neutral purchase-source architecture and quarantine safeguards unchanged.<\/li>\n<\/ul>\n\n
0.4.8<\/h4>\n\n\n- Improved Recent Audit Activity with meaningful scan summaries.<\/li>\n
- Collapsed Scan Started\/Completed pairs into a single scan event in the UI.<\/li>\n
- Added reliable actor labels (admin, system, or user ID fallback).<\/li>\n
- Added clearer audit cards for notifications, resolution changes, quarantine and recall updates.<\/li>\n<\/ul>\n\n
0.4.5<\/h4>\n\n\n- Added no-send safety email preview.<\/li>\n
- Added meaningful empty state for audit activity and filters malformed legacy audit rows.<\/li>\n
- Reused the exact notification builder for preview and live sends.<\/li>\n<\/ul>\n\n
0.4.4<\/h4>\n\n\n- Expands Purchase Sources into an adapter operations screen with health, capabilities, last verification, last test, and non-destructive source tests.<\/li>\n
- Adds optional Adapter SDK v2 methods: get_capabilities(), get_health_status(), and test_connection() without breaking the original interface.<\/li>\n
- Records source runtime health\/verification timestamps and clean adapter failure diagnostics.<\/li>\n
- Keeps WooCommerce on the same common purchase-source contract and adds health\/capability reporting.<\/li>\n
- Updates the provider-neutral developer example and keeps provider-specific implementation outside JAZ-X Product Recall Manager core.<\/li>\n<\/ul>\n\n
0.4.2<\/h4>\n\n\n- Packaging fix: restored the canonical plugin directory used by that release so uploaded ZIPs replaced the existing plugin instead of installing as a duplicate.<\/li>\n
- Keeps the v0.4.1 Adapter SDK v2 functionality unchanged.<\/li>\n<\/ul>\n\n
0.4.1<\/h4>\n\n\n- Adds Adapter SDK v2 while preserving the v1 interface for backward compatibility.<\/li>\n
- Adds a richer provider-neutral scan context with a normalized
products<\/code> array.<\/li>\n- Adds standardized verification methods for webhook, provider API, entitlement, subscription, download and license integrations.<\/li>\n
- Adds optional entitlement status\/expiry and source type fields to normalized adapter records.<\/li>\n
- Keeps provider-specific implementation outside JAZ-X Product Recall Manager core.<\/li>\n<\/ul>\n\n
0.4.0<\/h4>\n\n\n- Adds the provider-agnostic Purchase Source Adapter API.<\/li>\n
- Adds registration through
recallsafe_register_purchase_sources<\/code>, callback-backed sources, and a generic verified-match filter.<\/li>\n- Adds centralized verified-record normalization before external buyers can enter the affected-customer table.<\/li>\n
- Enforces external quarantine locks for adapter-provided matches.<\/li>\n
- Adds a Purchase Sources admin screen for connected verified sources.<\/li>\n
- Keeps provider-specific implementation details outside JAZ-X Product Recall Manager core.<\/li>\n<\/ul>\n\n
0.3.3<\/h4>\n\n\n- Fixes the unique-bridge discovery-to-correlation hand-off.<\/li>\n
- Carries catalog-unique bridge fingerprints on exact external source rows instead of re-deriving them later.<\/li>\n
- Deduplicates multiple bridge hits on the same external row.<\/li>\n
- Correlation diagnostics now use the already-proven unique bridge discovery as authoritative evidence.<\/li>\n
- Allows human-review buyer candidates when a catalog-unique bridge, customer identity, and entitlement\/access evidence are present without requiring a transaction reference.<\/li>\n<\/ul>\n\n
0.3.1<\/h4>\n\n\n- Preserve catalog-unique bridge fingerprints through row-level buyer correlation.<\/li>\n
- Deduplicate multiple bridge hits that refer to the same external source row.<\/li>\n
- Align in-memory bridge matching with common case-insensitive database collations.<\/li>\n
- Treat unique bridge + customer identity + entitlement evidence as a valid human-review path when no transaction reference exists.<\/li>\n<\/ul>\n\n
0.3.0<\/h4>\n\n\n- Adds Unique Bridge Buyer Verification for external download\/access stores.<\/li>\n
- Allows a catalog-unique product bridge to verify a buyer without requiring a transaction reference when entitlement\/access evidence is present.<\/li>\n
- Resolves opaque same-source customer references to customer identity rows before presenting a human-review candidate.<\/li>\n
- Keeps human approval mandatory and preserves quarantine for older false-positive external matches.<\/li>\n<\/ul>\n\n
0.2.9<\/h4>\n\n\n- Added catalog-wide bridge identifier uniqueness validation.<\/li>\n
- Shared\/global bridge identifiers are rejected for buyer promotion.<\/li>\n
- Added catalog-unique bridge + customer identity + entitlement verification when no transaction reference exists.<\/li>\n
- Added uniqueness diagnostics to the External Identifier Bridge Discovery UI.<\/li>\n<\/ul>\n\n
0.2.8<\/h4>\n\n\n- Adds related-row bridge correlation inside the same external source.<\/li>\n
- Follows exact transaction\/reference values from bridge-matched seed rows to customer and entitlement\/history rows.<\/li>\n
- Keeps correlation bounded and read-only; private provider, bridge and transaction values are never displayed.<\/li>\n
- Deduplicates multiple related history rows into one human-reviewed buyer candidate.<\/li>\n<\/ul>\n\n
0.2.6<\/h4>\n\n\n- Adds Bridge-Correlated Buyer Verification for opaque external catalog identifiers.<\/li>\n
- Correlates exact linked-product bridge identifiers with customer identity, transaction evidence and download\/access entitlement evidence in the same external source.<\/li>\n
- Deduplicates history\/event rows by source and customer identity before human review.<\/li>\n
- Shows masked buyer candidates with bridge-correlation confidence; raw provider, table, bridge and transaction values remain private.<\/li>\n
- Keeps promotion human-reviewed and revalidates promoted external buyers against current bridge evidence on later scans.<\/li>\n<\/ul>\n\n
0.2.5<\/h4>\n\n\n- Adds External Identifier Bridge Discovery for opaque external catalog\/product\/price references.<\/li>\n
- Reads only safe, non-sensitive linked-product metadata and displays identifier fingerprints instead of raw values.<\/li>\n
- Correlates exact bridge identifiers with transaction\/customer-capable external sources without exposing provider names or private values.<\/li>\n
- Numeric WooCommerce product IDs alone remain insufficient for external customer promotion.<\/li>\n<\/ul>\n\n
0.2.3<\/h4>\n\n\n- Quarantines legacy external matches that fail strict product-identity revalidation.<\/li>\n
- Excludes quarantined rows from active affected-customer counts.<\/li>\n
- Adds a dedicated Actions column with a visible Remove button for external rows.<\/li>\n
- Adds a quarantined-records review panel with permanent removal.<\/li>\n
- Keeps deep transaction discovery read-only and provider-agnostic.<\/li>\n<\/ul>\n\n
0.2.2<\/h4>\n\n\n- Strict external product identity verification: numeric IDs alone can no longer be promoted.<\/li>\n
- Added false-positive removal for external affected-customer records.<\/li>\n
- Added deeper read-only transaction discovery using exact text identifiers.<\/li>\n<\/ul>\n\n
0.2.1<\/h4>\n\n\n- Adds human-reviewed promotion of exact-product external download\/access entitlement candidates into Affected Customers.<\/li>\n
- Deduplicates entitlement history by customer identity and keeps provider\/table names private.<\/li>\n
- Uses generic external entitlement source labels and masked candidate identities before approval.<\/li>\n<\/ul>\n\n
0.2.0<\/h4>\n\n\n- Added entitlement-aware external record classification for digital products that grant direct downloads or time-limited access without issuing a license.<\/li>\n
- Separates purchase\/transaction, download\/access entitlement, license\/supporting, fulfillment and access-period evidence.<\/li>\n
- Treats subscription\/access\/download fields as entitlement evidence instead of assuming they are license records.<\/li>\n
- Reports access-period\/expiry evidence so time-limited download access can be distinguished from licensing.<\/li>\n
- Expands safe source discovery to entitlement, download, access, fulfillment and delivery storage signals.<\/li>\n
- External candidate mapping remains read-only and diagnostic; raw customer, payment, entitlement and license values are not displayed or auto-enrolled.<\/li>\n<\/ul>\n\n
0.1.9<\/h4>\n\n\n- Added privacy-preserving Safe Candidate Mapping for strong external purchase\/license sources.<\/li>\n
- Reads only exact affected-product candidate rows in bounded read-only queries and never displays raw customer, transaction or license values.<\/li>\n
- Reports customer evidence, transaction evidence, license evidence, anonymized unique identity counts, likely record role and mapping confidence.<\/li>\n
- Fixed external-source labels so verification\/mapping uses the same source letter shown by Source Inspector.<\/li>\n
- External candidates remain diagnostic only and are not auto-enrolled as affected customers.<\/li>\n<\/ul>\n\n
0.1.8<\/h4>\n\n\n- Added a read-only Candidate Verification Engine for strong unknown external purchase\/license sources.<\/li>\n
- Runs exact affected-product reference checks without displaying customer identity or transaction values.<\/li>\n
- Reports anonymized candidate-record counts, match method and confidence.<\/li>\n
- Candidate evidence never auto-marks customers as affected; a compatible adapter or safely mapped source is still required.<\/li>\n<\/ul>\n\n
0.1.7<\/h4>\n\n\n- Added anonymized Source Inspector for possible non-WooCommerce purchase\/license storage.<\/li>\n
- Inspects schema metadata only; unknown customer and transaction rows are never read.<\/li>\n
- Classifies generic source capabilities such as customer identity, product reference, transaction\/license reference, status\/date and quantity\/amount.<\/li>\n
- Adds adapter-readiness guidance without exposing provider names in the plugin UI.<\/li>\n<\/ul>\n\n
0.1.6<\/h4>\n\n\n- Added provider-agnostic purchase-source registry and safe external source discovery signals.<\/li>\n
- Prepared affected-customer storage for verified non-WooCommerce purchase sources.<\/li>\n
- Unknown external schemas are never read automatically and cannot create affected-customer matches without an adapter.<\/li>\n<\/ul>\n\n
0.1.4<\/h4>\n\n\n- Improved affected-order scanner diagnostics.<\/li>\n
- Normalize WooCommerce order statuses before querying orders.<\/li>\n
- Match recalled products by product ID, variation ID, parent product ID and SKU fallback.<\/li>\n
- Show scan totals, line-item totals, match method counts and linked product identifiers after each scan.<\/li>\n
- Keep matching conservative: product-name-only matching is intentionally not used.<\/li>\n<\/ul>\n\n
0.1.3<\/h4>\n\n\n- Block Draft and Reviewing recall URLs for all frontend visitors, including logged-in managers.<\/li>\n
- Add linked WooCommerce product names, SKUs and product image to public recall notices.<\/li>\n
- Improve the public recall notice with an official safety-alert layout and clearer status presentation.<\/li>\n<\/ul>\n\n
0.1.1<\/h4>\n\n\n- Fix public recall URLs returning 404 after activation by flushing rewrite rules safely after post type registration.<\/li>\n<\/ul>\n\n
0.1.2<\/h4>\n\n\n- Replaced the generic WordPress post editor with a dedicated product-recall management interface.<\/li>\n
- Added searchable WooCommerce product selection.<\/li>\n
- Unified recall status handling so Draft\/Reviewing notices are not public.<\/li>\n
- Added structured admin sections and improved public recall notice formatting.<\/li>\n
- Redirected legacy recall edit links into the product-recall management interface.<\/li>\n<\/ul>\n\n
0.1.0<\/h4>\n\n\n- Initial free release.<\/li>\n
- Manual recall case management.<\/li>\n
- WooCommerce product linking.<\/li>\n
- Batch order scan and affected customer detection.<\/li>\n
- Resolution tracking.<\/li>\n
- Public recall notice.<\/li>\n
- HPOS compatibility declaration.<\/li>\n<\/ul>","raw_excerpt":"Manage WooCommerce product recalls, identify affected past orders, and publish product safety notices.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/377887","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=377887"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/jazxinnovation"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=377887"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=377887"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=377887"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=377887"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=377887"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=377887"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}