[WordPress] 外掛分享: JAZ-X Product Recall Manager for WooCommerce

首頁 › 外掛目錄 › JAZ-X Product Recall Manager for WooCommerce
全新外掛
安裝啟用
—
尚無評分
15 天前
最後更新
—
問題解決
WordPress 6.5+ PHP 7.4+ v1.0.4 上架:2026-09-29

內容簡介

JAZ-X Product Recall Manager for WooCommerce 為商店擁有者提供了一個結構化的產品安全召回工作流程,幫助管理產品召回資訊,確保顧客安全。

【主要功能】
• 手動管理產品召回案例
• 連結 WooCommerce 產品與召回資訊
• 批次安全掃描 WooCommerce 訂單
• 受影響訂單/顧客列表
• 解決方案追蹤:退款、替換等
• 公開產品召回通知頁面

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.0.4) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「JAZ-X Product Recall Manager for WooCommerce」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

JAZ-X Product Recall Manager for WooCommerce gives store owners a structured workflow for product safety recalls.
Free 1.0.0 includes:

Manual product recall cases.
Recall reference, source, date, brand, model, identifier, batch/lot, hazard, customer action and remedy fields.
Link recalls to WooCommerce products.
Batch-safe scanning of WooCommerce orders using WooCommerce order APIs.
HPOS compatibility declaration.
Affected order/customer list.
Quantity counts.
Resolution tracking: open, refund, replacement, repair or closed.
Public product recall notice pages.

Internal audit log foundation.

Provider-agnostic Purchase Source Adapter API for verified external buyers.

Built-in WooCommerce order source plus optional hook/callback adapters.
Adapter records are normalized before storage and quarantine locks are enforced centrally.

Purchase Sources admin screen shows only registered verified sources, without requiring provider-specific branding.

Deep Transaction Discovery using exact product title, slug, SKU or product URL; numeric-only IDs are ignored.

Read-only discovery across transaction/customer-capable custom tables and transaction-like custom record types.
Strict external product identity verification and quarantine of legacy false-positive matches.

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.
Adapter API Example
Integrations may register a callback-backed verified purchase source:
add_action( 'recallsafe_register_purchase_sources', function ( $registry ) {
$registry->register_callback_source(
'my_external_source',
'External verified purchase source',
function ( $context ) {
// Query your own system and return only independently verified buyers.
return array();
}
);
} );

Or use the generic hook-backed adapter:
add_filter( 'recallsafe_external_verified_matches', function ( $records, $context ) {
// Return only provider-verified records for the supplied product fingerprints.
return $records;
}, 10, 2 );

A verified record requires source_record_id and customer_email. Optional fields are customer_id, customer_name, quantity, purchased_at, verification_method, and product_reference.
Adapter SDK v2 Example
add_action( 'recallsafe_register_purchase_sources', function ( $registry ) {
$registry->register_callback_source(
'verified_external_commerce',
'External verified purchase source',
function ( $context ) {
$records = array();
foreach ( RecallSafe_Adapter_SDK::products_from_context( $context ) as $product ) {
// Query your own trusted system using the product fingerprint.
// Only return a row after your integration has verified ownership.
}
return $records;
}
);
} );

Build records with RecallSafe_Adapter_SDK::verified_record(). Required fields remain source_record_id and customer_email. Recommended fields are verification_method, product_reference, purchased_at, and, for access-based products, entitlement_status and entitlement_expires. Provider-specific API credentials, webhook secrets and private implementation details must stay in the integrating system.

文章
Filter
Mastodon