Description
Kiverniq Equipment Match helps a WooCommerce store identify a customer’s equipment and recommend compatible products from its own catalog. The complete manual workflow works without an AI account.
- Collect requests from customers and guests, with optional images and PDF documents.
- Configure form fields, labels, validation, tasks, upload limits and appearance with a visual form builder and live desktop/mobile preview.
- Give guests a secret access link they can copy or download, without requiring email.
- Let staff manage requests, discuss details, add private notes, preview answers and publish product recommendations.
- Maintain equipment models, families, facts and verified compatibility rules through visual editors. Import and export knowledge using the administration interface.
- Show customers their requests and saved equipment in My Account.
- Add recommended products to the cart with request context. Supports classic checkout, Cart and Checkout blocks, and WooCommerce HPOS.
- Optionally assist staff using OpenAI, Anthropic Claude, Google Gemini, OpenRouter, DeepSeek or an administrator-configured compatible API, with a separate model and encrypted key for each profile.
Manual processing is the default. AI assistance and automatic publication are separate, optional settings. Automatic publication requires verified equipment and compatibility evidence; a model’s confidence alone cannot authorize it. Provider accounts, supported models and any API charges are managed separately by the store owner.
The interface is in English and uses WordPress translation functions. No Node.js, Composer, SMTP service or external application server is needed on the store. Image uploads require GD or Imagick. Network activation is not supported; activate separately for each site.
Kiverniq is an independent plugin by Theron Hettinger and is not affiliated with or endorsed by WooCommerce or Automattic.
Upgrading from 1.0.0
Back up the database and uploads. Deactivate Equipment Match 1.0.0 before activating Kiverniq. Existing data is migrated automatically. Existing attachment URLs and guest access links are retained. Form shortcodes stored in WordPress posts are updated to [kiverniq_request_form]; update any shortcodes embedded in theme files or external page-builder storage manually. The REST namespace is now kiverniq/v1, extension hooks use the kiverniq_ prefix, and My Account endpoints are kiverniq-requests and kiverniq-equipment.
Support
Author: Theron Hettinger.
Contact: hettingert159@gmail.com.
Source code
The original, editable JavaScript and CSS source files are included in assets/js/ and assets/css/. These files are served directly by WordPress. They are not minified, compiled or generated bundles and have no separate upstream source files. No npm, webpack, transpilation or asset build step is required; edit these files directly. PHP source is included in src/ and templates/ with the plugin bootstrap and autoloader in the root directory. No runtime libraries are bundled.
Compatibility
This release uses direct provider adapters to support WordPress 6.2 and later, separate provider profiles, native PDF/image inputs and provider-specific structured output. It does not use the WordPress AI Client introduced in WordPress 7.0. The adapters use the WordPress HTTP API; external processing remains optional and subject to the consent and service disclosures below.
External services
The plugin has no installation telemetry and downloads no executable code from external services. Manual mode sends no requests to an LLM provider.
An administrator can explicitly check the saved provider connection; this sends the configured credential and model metadata to that provider, without customer materials. AI analysis requires AI assistance to be enabled and the customer’s separate consent. When analysis runs, the selected provider receives task text, description and model hints, selected uploaded materials, source references, locale, and a bounded equipment/catalog candidate set. Contact fields, guest access secrets and internal staff notes are excluded from constructed prompts. Uploaded documents or descriptions can themselves contain personal data; review them before consenting. The selected service authenticates requests using its own API key.
The services are:
- OpenAI (api.openai.com): native equipment analysis and ranking. Service terms and privacy policy; API data information.
- Anthropic Claude (api.anthropic.com): native equipment analysis and ranking. Commercial terms and privacy policy.
- Google Gemini (generativelanguage.googleapis.com): native equipment analysis and ranking. API terms and privacy policy. Data treatment can differ between paid and unpaid services.
- OpenRouter (openrouter.ai): compatible analysis and ranking, routed to the selected model’s downstream provider. Terms and privacy policy. Review the routed provider’s terms and data policy too.
- DeepSeek (api.deepseek.com): compatible analysis and ranking. Terms and privacy policy.
- Custom compatible API: requests go to the public HTTPS base URL configured by the administrator. No custom endpoint is enabled by default. The administrator must identify its operator and publish its terms and privacy links in the store’s privacy policy before enabling it.
Only the active provider is used; there is no automatic fallback to another provider. Provider retention, processing regions and charges depend on that provider and account. Withdrawing consent prevents later calls but cannot recall data already sent to a service.
Privacy
The store stores requests, customer-provided details and attachments, conversations, staff notes, answers, access grants and compatibility knowledge in its own WordPress database and uploads directory. Request creation also uses network/browser identifiers to limit abuse. Administrators can configure retention, use WordPress privacy export/erasure, and configure plugin-data deletion on uninstall. WooCommerce order items retain the recommendation context needed for order history.
The store owner must configure a privacy-policy URL and describe its own retention and any enabled external processing. Uploaded file URLs are accessible to anyone who possesses the full URL, as explained above.
Installation
- Install and activate WooCommerce 8.2 or later on WordPress 6.2 or later, with PHP 7.4 or later. Also meet the requirements of your installed WooCommerce version.
- Upload the plugin ZIP through Plugins > Add New > Upload Plugin, and activate Kiverniq Equipment Match for WooCommerce.
- Open WooCommerce > Kiverniq Equipment Match. Use Form builder to configure the form and its privacy-policy link.
- Add the shortcode [kiverniq_request_form] to a page, or use the built-in New request page.
- In Settings, configure request limits and rebuild the catalog index for existing products. Manual processing can be used immediately.
- If desired, configure an LLM provider and key, check its saved connection, review its data policies, and enable AI assistance.
Use HTTPS on a live site. Exclude the form, request pages, My Account and the plugin REST routes from full-page caching. Background work uses the Action Scheduler supplied by WooCommerce and requires working WordPress cron or a system cron.
FAQ
-
Does this plugin require an AI subscription?
-
No. Staff can process requests and publish recommendations manually. Optional AI calls require an account and key for the selected service and may incur charges. Attachment and structured-output support depend on the adapter and selected model. Compatible APIs support text and optional images; PDFs use the native OpenAI, Claude or Gemini adapters.
-
How do I save an API key?
-
Use Settings > LLM providers and keys. Each provider has its own profile. Leaving a key field blank keeps its saved value; the explicit removal option deletes it. Keys are encrypted in a separate, non-autoloaded WordPress option and are never returned in settings responses or displayed in HTML. Changing WordPress authentication salts may require entering saved keys again.
-
Can a guest use the form without email?
-
Yes. A guest receives a secret access link and can read the request using an authorized browser session. Save this link securely. Knowing an email address does not grant access to a request.
-
Are uploaded files private?
-
Request pages and file metadata require request access. The files themselves are ordinary WordPress uploads named with an independent random UUID prefix and the sanitized original filename: anyone with the complete URL can open them. Do not upload materials that require authorization on every download. The store owner controls allowed types, sizes, counts and retention. Supported formats are JPEG, PNG, WebP and PDF.
-
What happens when the plugin is deleted?
-
Deactivation preserves data. Uninstall also preserves plugin data and files by default. To remove them, enable the deletion option in Settings before uninstalling. Back up the site first. Existing WooCommerce products, orders and order-item history are retained.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Kiverniq Equipment Match for WooCommerce” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Kiverniq Equipment Match for WooCommerce” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.1
- Introduce the distinctive Kiverniq name, plugin slug and public identifier prefix.
- Load access-link JavaScript through WordPress script APIs and restrict error notices to relevant administration screens.
- Include formatted, editable asset sources and document their location.
- Migrate Equipment Match 1.0.0 data, encrypted keys, permissions, form shortcodes and order references.
1.0.0
- Initial release with manual request handling, guest access, uploads and visual form configuration.
- Equipment knowledge, verified compatibility, staff answer preview, customer equipment and WooCommerce cart/checkout integration.
- Optional multi-provider AI assistance with separate encrypted credentials and consent controls.