Select one or more tags, then press “Search Plugins”

Find Plugin with any / all of the selected criteria
Search Plugin

Kat3x Catalog Guard Wordpress Plugin - Rating, Reviews, Demo & Download

Kat3x Catalog Guard Wordpress Plugin - Rating, Reviews, Demo & Download
No ratings yet
Free
Follow for free plugins, new theme releases and theme news

Plugin Description

Complete user guides (EN, IT, DE, FR, ES) are in docs/ inside this ZIP; start with docs/en.md or your language. Technical reference: docs/reference.md.

Compare a WooCommerce catalog with an expected price list and show the differences
to your assistant, with the scope of the check always visible. Catalog Guard helps
agencies and catalog operators prepare an import handover with declared exclusions.
Load two CSV files, or compare one list with two read-only WooCommerce observations.
Confirm the proposed column mapping and decimal conventions before comparing.
Only SKU is required. Unmatched fields are listed; totals needing an unmatched
field are not calculable. Known unsupported importer columns are excluded explicitly.
The plugin reports differences, duplicate keys, ambiguous readings and a reconciliation
of stock and value totals. Prices use integer cents. It does not import or repair products.
The administration page is supplied in English, Italian, German, French and Spanish.

What the comparison can establish

Store reads use prepared SQL SELECTs (wpdb_select) and WooCommerce REST v3 GETs
inside WordPress (wc_rest_v3, wc_data_store, wp_object_cache). Both use the same
database: independence concerns the layers above it. Both enforce the same user
permission policy. No network requests are made by these readers.
A single available reading yields partial coverage with single_observation.
Two complete independent agreeing readings can yield the technical state verified.
Conflicting observations select no value. The catalog changing during a reading
can yield stale. Compatibility combinations remain empty: combo_unknown applies.
A signature does not establish store truth, freshness, revocation status, or importer compatibility.

Parent-managed stock is read from the parent. Effective prices use the sale dates
at the chosen instant. Variation names are not compared because WooCommerce derives
them from the parent and attributes; the local report states this limit. Other product
names are compared as original UTF-8 bytes. Only a hash and length are used internally
for agreement; neither the name nor its hash enters the signed export.
Product attributes are not observed by the store readers and remain a declared limit.
Without intl the original Unicode difference is retained and normalization is reported
unavailable. Windows-1252 conversion requires iconv; other unsupported encodings are rejected.

Five-minute demonstration

  1. Open WooCommerce > Kat3x Catalog Guard and select Use the demonstration sample.
  2. Review proposed columns and decimal conventions, then Compare.
  3. Inspect the 15 exceptions and the stock/value reconciliation.
  4. Download exceptions.csv and the unsigned local report.
  5. For store mode, load File A, select read-only store comparison, choose before/after
    import and optionally whole-catalog scope, then download the signed receipt.
    The sample is synthetic. A successful demonstration does not validate a real import.
    Contextual Help on this page explains the workflow, limits and common problems.
    The user guide in English, Italian, German, French and Spanish is included
    in the docs/ folder of the plugin.

Node and signing limits

The signing key is stored in the installation, in the plugin database option with
autoload disabled. The expected responses do not export it. Anyone with database
access or code execution on the site can read it; backups, caches and site copies
require protection and revocation management.
Two copies with the same address cannot be distinguished by the store: use a new
identity on every staging copy. Uninstalling removes local options but does not
revoke the key in the register: request revocation from Kat3x.
The comparison runs in the store. The receipt contains the declared reduced fields;
in the optional assistance path it passes to the customer’s model and Kat3x.
The signature permits checks of integrity and signing key. The receipt describes the readings and comparisons declared by the node; it does not guarantee that the catalog is correct. A compromised site can sign false data.
The plugin sends nothing on its own. Optional assistance uses customer-configured
connectors and requires a compatible model, Abilities API and MCP Adapter, revocable
credentials and product permissions; the complete assistance path still requires testing.
Guard and Sonda sign locally. Admission and verification of the node by the kernel
are under construction and require their own checks.
build_digest is the build declared by the node, without attesting the running code.
The node identifier and shop_ref are stable pseudonyms. Service purpose, retention
and deletion must be declared before the first real store uses the service.

Signed receipt ability (0.4.0)

The optional WordPress MCP Adapter can expose kat3x-catalog-guard/receipt to a user
with manage_woocommerce. The caller supplies CSV text (at most 1048576 bytes), column
mapping, decimal convention, whole-catalog flag and import phase. No file path or
saved page result is accepted as a reference.
Every call reads the catalog again through the same database and in-process REST
readers used by the local comparison. A stale REST object cache can produce a declared
conflict; timestamps and watermark alone do not prove new data.
A supplied kernel request is copied unchanged after structural and UTC calendar checks.
Without one, the receipt declares issued_by plugin-locale; freshness is not guaranteed
by the kernel. The plugin does not decide whether the kernel issued a request or
whether it was already consumed.
The signed ability response contains the receipt only. Technical text identifiers are
replaced by opaque references local to that receipt, product names are omitted, and
supported numeric differences remain visible. These references cannot be matched
across receipts. The local page download retains its separate, existing export policy.
Orders, customers and user data are outside this catalog response.
The three node abilities do not change catalog rows or node options after activation,
except that a failed signature with a broken key records chiave_non_valida. Saving a
shop reference preserves chiave_da_ammettere and chiave_non_valida.
PHP, WordPress, MCP Adapter and Plugin Check are evaluated separately at the server
bench. The release is not admitted by its author and compatibility is not assumed.
The skeleton uses the product namespace; Abilities API is optional for panel use.

Privacy

The plugin reads product lists and catalog data, not orders or customers. No external
services are called. The local report contains full product names; the signed receipt
omits them. The signed ability uses opaque text references local to each receipt;
supported numeric differences remain visible. The local page has a separate export policy.
Uploads are private temporary files, retained for one hour and removed on cleanup.
WP-Cron is request-driven, so deletion may occur later. Signing keys and node options
are stored locally. Protect database access, code execution, backups and site copies.
The node identifier and shop_ref are stable pseudonyms, not anonymous values.
If optional assistance is chosen, the reduced receipt passes through the configured
model and Kat3x. Define service purpose, retention and deletion before the first real
store. Do not include customer or supplier data in a support example.

Screenshots

No screenshots provided


Reviews & Comments