Linux 软件免费装
Banner图

DT-PM AI Sale Assistant for WooCommerce

开发者 dtpm
更新时间 2026年10月30日 00:22
PHP版本: 8.2 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce artificial intelligence ai chatbot product recommendations

下载

1.3.0 1.4.1 1.4.2 1.1.3 1.0.13 1.1.1 1.2.0

详情介绍:

DT-PM AI Sale Assistant for WooCommerce (DT-PM AI Sale Assistant for short) is not a generic AI chatbot bolted onto search, and it does not just match keywords in a product's title or description. For each product category, it builds an explicit "causal chain" - a structured model of the actual questions and criteria your customers weigh when choosing between products (e.g. intended use, must-have features, budget) - and you, the merchant, review and confirm that model before it ever talks to a shopper. Every recommendation the assistant makes is then reasoned through that confirmed, category-specific model, not generated from an unstructured prompt or a plain product search. Main features: How it works: this plugin is a thin WordPress/WooCommerce interface. The actual AI processing (analyzing your categories, building the causal model, generating recommendations) runs on our own hosted backend service, which this plugin talks to over HTTPS. See "External services" below for exactly what is sent and when. Free to start, paid tiers for growing stores: every store gets a free tier with a usage allowance and a one-time trial month. Larger product catalogs or higher usage require a paid plan - see the plugin's Status tab for your current tier, catalog usage, and an upgrade link. Requirements: an active WooCommerce installation. An outbound HTTPS connection from your server to our backend service (see "External services") is required for the plugin to function.

安装:

  1. Make sure WooCommerce is installed and active.
  2. Upload the plugin files to /wp-content/plugins/dtpm-ai-sale-assistant-woocommerce, or install the plugin through the WordPress plugins screen directly.
  3. Activate the plugin through the "Plugins" screen in WordPress.
  4. Go to the new "DT-PM AI Sale Assistant" menu item in your WordPress admin and click "Connect this store" - this registers your store with our backend service (see "External services" above). You can then review your connection status, run the Category Analysis, and set up your first Causal Chain.
  5. Once you're happy with the setup, place the chat widget on your storefront by completing the Product Coverage step - the widget then appears automatically across your storefront (product pages, homepage, cart, checkout, and more).

屏幕截图:

  • Settings: AI model (standard or your own API key), support contact, chat widget title and position, suggested questions.
  • Settings: tone of voice - analyze pages of your own shop or choose a preset.
  • Category analysis: AI-suggested grouping of WooCommerce categories into subcategories, reviewed and confirmed by you.
  • Causal chain: coverage check showing product characteristics the decision model does not cover yet.
  • Causal chain: the decision model for a subcategory, with price tolerances and the questions that drive a recommendation.
  • The chat widget in the storefront, with suggested starter questions.
  • A conversation in the chat widget: the assistant asks about budget and taste, then recommends matching products with an add-to-cart button.

常见问题:

Do I need WooCommerce for this plugin to work?

Yes. This plugin is built specifically for WooCommerce stores and will not do anything useful without it active.

Does this plugin work offline, or without sending any data anywhere?

No. The actual AI processing happens on our hosted backend service, not inside WordPress. See the "External services" section above for exactly what is sent and when.

Is this plugin free?

The plugin itself is free and GPL-licensed. Every store also gets a free usage tier plus a one-time trial month on our backend service. Stores with larger catalogs or higher usage may need a paid plan with our service - your current tier and catalog usage are always visible in the plugin's Status tab.

What happens to my data if I deactivate the plugin?

Deactivating the plugin stops the scheduled check-ins described in "External services" above. It does not delete your account or data on our service - reactivating the plugin resumes where you left off.

Where can I get support?

Use the support contact configured in the plugin's settings page (email or a link of your choice) - this is the same contact your customers see when the assistant escalates a conversation to a human.

更新日志:

1.4.2 Requires Kern-API >= commit 1dfcb9a (unchanged from 1.4.1) - no Kern-API dependency change. 1.4.1 Requires Kern-API >= commit 1dfcb9a (unchanged from 1.4.0) - this is a documentation/translation-only release, no Kern-API dependency change. 1.4.0 Requires Kern-API >= commit 1dfcb9a - this version calls several new Kern-API endpoints (among others POST /chat/turn, POST /agent/continue-with-bestellhistorie, POST /agent/continue-with-uebergabe, POST /agent/uebergabe-autorisieren, POST /agent/uebergabe-fehlgeschlagen, GET /tenants/byok-modelle); an older Kern-API without these would reject or silently ignore the new capabilities below. 1.3.0 Requires Kern-API >= commit 9a769d8 - this version tracks a server-issued conversation identifier (konversation_id) across turns, shows the new mandatory AVV-consent checkbox/catch-up banner, and uses a new non-destructive category-save endpoint; an older Kern-API without GET /avv/aktuelle-fassung, POST /tenants/{tenant_id}/avv-zustimmung, POST /categories/aenderungen-speichern, or the konversation_id handling in POST /agent/turn/POST /agent/continue-with-live-data would reject or silently ignore these calls. 1.2.0 Requires Kern-API >= commit a2995ac - the plugin now requests a short-lived Storefront-Token (POST /tenants/{tenant_id}/storefront-token) instead of sending the permanent tenant secret directly from the browser; an older Kern-API without this endpoint would reject every browser request once the plugin stops also offering the secret, so this is a hard requirement starting with this version. 1.1.3 Requires Kern-API >= commit 3c31fd7 (unchanged from 1.1.2) - this is a pure frontend/JS fix, no Kern-API dependency. 1.1.2 Requires Kern-API >= commit 3c31fd7 (unchanged from 1.1.1) - this fix calls only the already-existing GET /variation-attributes endpoint, no new Kern-API dependency. 1.1.1 Requires Kern-API >= commit 3c31fd7 - an older Kern-API simply ignores the new vollstaendiger_katalog field this version adds to its "process subcategory" request (safe, additive field), but without it the orphan-cleanup fix below has no effect server-side. 1.1.0 Requires Kern-API >= commit 06b1350 (current production state at release time) - older plugin versions keep working against this Kern-API, but the "In stock" label, the real search-hit count, and the "What I understood" box need this Kern-API version to actually show (both fields are purely additive, an older plugin simply ignores them). 1.0.14 1.0.13 1.0.12 1.0.11 1.0.10 1.0.9 1.0.8 1.0.7 1.0.6 1.0.5 1.0.4 1.0.3