Snoodlr AI Assistant for WooCommerce connects a WordPress site to Snoodlr's external AI assistant service after explicit administrator authorization.<\/p>\n\n
Version 2.5 provides the local plugin bootstrap, activation\/deactivation handlers, settings defaults, permission-gated admin screens, nonce-protected admin view state, local admin assets, local database tables, local source detection and confirmation, signed query routes, optional WooCommerce commerce routes, and optional frontend widget enablement.<\/p>\n\n
Before an administrator connects Snoodlr, the plugin does not contact Snoodlr from WordPress, auto-inject a widget, require WooCommerce, copy full site content to Snoodlr, call AI\/LLM APIs from WordPress, add analytics or tracking, or process online payments.<\/p>\n\n
Snoodlr is an external AI assistant service. This plugin connects to Snoodlr only after an administrator explicitly clicks Connect to Snoodlr during setup.<\/p>\n\n
Data shared with or exchanged with Snoodlr is limited to these categories:<\/p>\n\n
https:\/\/app.snoodlr.com\/en\/app\/integrations\/wordpress\/connect<\/code> receives the site URL, WordPress admin URL, callback URL, plugin version, WordPress version, PHP version, locale, timezone, site name, generated site public ID, WooCommerce active flag, connection state value, and source identifier. Because the administrator's browser opens Snoodlr's hosted onboarding page, Snoodlr may also receive standard browser request metadata such as IP address, user agent, and referrer.<\/li>\n- Connection callback and credentials. Snoodlr returns a connection status, connection ID, connection secret when provided, and widget public key when provided. These values are stored locally in WordPress. The connection secret is used for HMAC request signing and is not exposed to frontend JavaScript.<\/li>\n
- Connection verification and disconnect. WordPress admin status screens may call
https:\/\/api.snoodlr.com\/v1\/public\/wordpress\/connection-verify<\/code>. Disconnecting may call https:\/\/api.snoodlr.com\/v1\/public\/wordpress\/connection-disconnect<\/code>. These calls send the Snoodlr connection ID, timestamp, nonce, HMAC signature, and, for disconnect, a disconnect reason and source identifier.<\/li>\n- Signed health and capability responses. After connection, Snoodlr may send signed requests to the local WordPress REST routes. WordPress may return plugin version, schema version, table verification status, indexed\/dirty\/failed object counts, last indexed time, enabled source-role counts, entity and mention counts, widget enabled\/supported status, WooCommerce availability, commerce capability names, currency, and whether query routes are ready.<\/li>\n
- Signed content query responses. Snoodlr may send search queries, entity subjects, object IDs, WordPress object IDs, object kind\/subtype filters, role filters, language, sort, limits, and an
include_body<\/code> flag. WordPress may return the echoed sanitized query parameters, relevant result IDs, WordPress object IDs, object kind\/subtype, title, sanitized snippet or summary, URL, source role, published\/modified dates, matched fields, evidence notes, relevance score, entity IDs, canonical entity names, entity type, confidence, source count, ambiguity candidates, primary context, latest updates, reference context, and, only when include_body<\/code> is requested, a sanitized body excerpt limited by the plugin.<\/li>\n- Signed WooCommerce product responses. If WooCommerce is active, Snoodlr may send product search text, filters, product ID, variation ID, quantity, requested attributes, order\/sort values, and stock\/category\/tag filters. WordPress may return public product evidence including product ID, variation ID, product title, summary, URL, image URL, price, regular price, sale price, display price, currency, stock status, availability, published\/modified dates, product attributes, categories, tags, matched fields, relevance score, and diagnostic counts for the product search.<\/li>\n
- Pending order and order status flows. If a visitor asks Snoodlr to create a pending order, Snoodlr sends the requested items, product IDs, variation IDs, quantities, attributes, customer name, customer email or phone, billing address fields, shipping address fields, and customer note to WordPress. WordPress creates a pending WooCommerce order and returns only the order ID, order number, status, total, currency, and created time. For order status, Snoodlr sends an order ID or order number plus an email or phone verification value; WordPress returns the same minimal order fields after verification.<\/li>\n
- Optional frontend widget. The frontend widget is disabled by default. If an administrator enables it after connecting Snoodlr, the plugin loads a local bootstrap script that loads Snoodlr's hosted widget from
https:\/\/app.snoodlr.com\/widget\/loader.js<\/code> on public site pages. The local bootstrap exposes only widget URL, API base URL, widget public key, plugin version, locale, and widget position to frontend JavaScript. Widget API calls use https:\/\/api.snoodlr.com<\/code>. Visitor conversations in the widget, and any information visitors type into the widget such as names, contact details, product requests, order requests, or order verification details, are processed by Snoodlr. Loading the hosted widget can also share standard browser request metadata with Snoodlr, such as IP address, user agent, and referrer\/current page URL depending on browser policy.<\/li>\n<\/ul>\n\nThe plugin creates local indexing tables inside WordPress and lets administrators confirm which detected content sources may be indexed locally. Source choices start disabled and are enabled only after an administrator saves selected sources. Full site content, full product catalogs, posts, pages, custom post types, existing orders, customers, and coupons are not bulk-copied to Snoodlr by default.<\/p>\n\n
When WooCommerce is installed, signed commerce routes can search locally indexed enabled product sources, check live product availability, create pending WooCommerce orders, and return minimal verified order status. Availability, price, stock, order creation, and order status use live WooCommerce APIs. The plugin does not process payment and does not return full customer profiles, full addresses for existing orders, private order notes, or payment metadata. Administrators can disconnect or revoke local access credentials without deleting local index tables or confirmed sources.<\/p>\n\n
Administrators can disable the widget at any time. The plugin does not add hidden frontend credits, tracking pixels, analytics scripts, remote fonts, or unrelated third-party scripts.<\/p>\n\n
Snoodlr Terms of Use: https:\/\/app.snoodlr.com\/en\/terms-of-use\nSnoodlr Privacy Policy: https:\/\/app.snoodlr.com\/en\/privacy-policy<\/p>\n\n
Privacy and Data Processing<\/h3>\n\n
The plugin stores source confirmations, local index rows, entity mentions, connection status, signed API metadata, and widget settings inside WordPress.<\/p>\n\n
Local indexing is limited to administrator-enabled, confirmed public sources. Drafts, private content, password-protected content, failed rows, not-indexable rows, orders, customers, and coupons are excluded from local content indexing.<\/p>\n\n
Signed query routes return structured evidence only. They do not return full body text by default. Object requests with include_body<\/code> return a limited sanitized excerpt, not unlimited raw content.<\/p>\n\nIf the optional widget is enabled, visitor conversations occur through Snoodlr's hosted widget and are processed by Snoodlr. The plugin exposes only non-secret widget configuration to the frontend: widget URL, API base URL, widget public key, plugin version, locale, and position.<\/p>\n\n
WooCommerce Support<\/h3>\n\n
WooCommerce is optional. The plugin activates and its settings pages work without WooCommerce.<\/p>\n\n
When WooCommerce is active and available, signed commerce routes can search locally indexed enabled product sources, check live availability and price, create pending orders, and return verified minimal order status. Product search may use local discovery snapshots, but availability, price, stock, pending-order creation, and order status are checked through live WooCommerce APIs.<\/p>\n\n
The plugin does not process payments, mark orders paid, export the catalog, expose broad order search, return full customer profiles, or expose payment metadata\/private order notes.<\/p>\n\n
Disconnect and Uninstall<\/h3>\n\n
Disconnecting Snoodlr removes local connection credentials and prevents signed Snoodlr requests from authenticating. It does not remove local index tables, confirmed sources, or plugin settings.<\/p>\n\n
Uninstall removes plugin options including connection credentials, settings, schema status, API error status, and widget settings. Local Snoodlr database tables are preserved by default to avoid unexpected merchant\/site data loss.<\/p>\n\n
Limitations<\/h3>\n\n
Production Snoodlr service URLs must remain accurate for the release build.<\/p>\n\n
The plugin returns structured evidence to Snoodlr. Final answer synthesis happens in Snoodlr's external service, not inside WordPress.<\/p>\n\n
Online payments are not supported. Orders created by the commerce API are pending WooCommerce orders only.<\/p>\n\n\n
\n- Upload the plugin folder to
\/wp-content\/plugins\/snoodlr-ai-assistant-for-woocommerce\/<\/code>.<\/li>\n- Activate Snoodlr AI Assistant for WooCommerce from the Plugins screen.<\/li>\n
- Open the Snoodlr admin menu to review the setup disclosure.<\/li>\n
- Confirm which detected public sources may be indexed locally.<\/li>\n
- Connect Snoodlr only when you are ready to allow signed, scoped server-to-server requests.<\/li>\n
- Enable the optional frontend widget only if you want Snoodlr's hosted widget to load on public pages.<\/li>\n<\/ol>\n\n
Activation does not contact Snoodlr and does not inject frontend assets.<\/p>\n\n\n
\nDoes activation contact Snoodlr?<\/h3><\/dt>\nNo. Activation is local only. It creates or repairs local plugin options and database tables, but it does not contact Snoodlr.<\/p><\/dd>\n
Does this plugin copy my full website to Snoodlr?<\/h3><\/dt>\nNo. The planned V1 architecture uses local WordPress indexing tables and signed scoped runtime requests. Full site content is not copied to Snoodlr by default.<\/p><\/dd>\n
Does this plugin work without WooCommerce?<\/h3><\/dt>\nYes. WooCommerce is optional. Commerce capabilities report unavailable and commerce routes return safe unavailable errors when WooCommerce is inactive.<\/p><\/dd>\n
Does this plugin process payments or complete orders?<\/h3><\/dt>\nNo. Commerce routes can create pending WooCommerce orders only. They do not mark payment complete or process online payments.<\/p><\/dd>\n
Does uninstall remove local Snoodlr database tables?<\/h3><\/dt>\nNo. The plugin preserves local Snoodlr database tables on uninstall to avoid unexpected data loss. Plugin options and connection credentials are removed.<\/p><\/dd>\n
Does this plugin inject a frontend chat widget?<\/h3><\/dt>\nNot by default. The widget is not injected on activation or connection. It loads only after an administrator explicitly enables it while Snoodlr is connected, and it can be disabled at any time.<\/p><\/dd>\n
How do I disconnect Snoodlr?<\/h3><\/dt>\nOpen the Snoodlr setup or settings page and use Disconnect Snoodlr. This revokes local connection credentials and stops signed requests from authenticating.<\/p><\/dd>\n
Does the plugin expose secrets in frontend JavaScript?<\/h3><\/dt>\nNo. The frontend widget config contains only non-secret public fields. HMAC secrets, connection secrets, private tokens, admin nonces, source data, order data, and customer data are not localized to frontend JavaScript.<\/p><\/dd>\n\n<\/dl>\n\n\n
2.5<\/h4>\n\n\n- Improved onboarding index progress so indexed and queued counts refresh through AJAX while indexing is running.<\/li>\n
- Added incremental onboarding indexing ticks so progress moves item by item instead of jumping after a full background batch completes.<\/li>\n
- Fixed Reindex to requeue failed index items and rebuild eligible local index content when there are no failed items to retry.<\/li>\n
- Simplified the onboarding index step actions to Continue to widget, Reindex, and Back.<\/li>\n
- Fixed indexing button labels, spinner alignment, and completion state so the button does not stay stuck in an animation.<\/li>\n
- Linked the setup logo and Plugins screen Application action to the Snoodlr app.<\/li>\n
- Updated plugin information links to use https:\/\/snoodlr.com for Snoodlr website details.<\/li>\n<\/ul>\n\n
0.2.2<\/h4>\n\n\n- Added WooCommerce cart awareness for the Snoodlr widget so shoppers can ask what is currently in their cart.<\/li>\n
- Added visitor-session cart REST routes for reading cart contents and adding, updating, or removing WooCommerce cart items through same-origin, nonce-protected requests.<\/li>\n
- Added WordPress cart bridge configuration to the frontend widget loader so Snoodlr can complete add-to-cart actions in the shopper's active WooCommerce session.<\/li>\n
- Improved cart-question handling so current-cart questions are not answered with broad product catalog listings.<\/li>\n
- Updated plugin release tag and version metadata.<\/li>\n<\/ul>\n\n
0.1.5<\/h4>\n\n\n- Hardened admin view query parameters behind nonce and capability checks.<\/li>\n
- Centralized admin POST permission, nonce, and input handling.<\/li>\n
- Refactored local query SQL to use fixed prepared statement templates.<\/li>\n<\/ul>\n\n
0.1.4<\/h4>\n\n\n- Aligned release metadata for WordPress.org packaging.<\/li>\n
- Hardened source consent so detected sources are not enabled until an administrator saves the choice.<\/li>\n
- Expanded external service disclosure for connection verification and disconnect calls.<\/li>\n
- Cleaned uninstall option removal and escaping in source cards.<\/li>\n<\/ul>\n\n
0.1.1<\/h4>\n\n\n- Updated release metadata for SIRAPIX attribution and plugin version alignment.<\/li>\n<\/ul>","raw_excerpt":"Connect WordPress to Snoodlr's external AI assistant service with local indexing, signed access, WooCommerce support, and an opt-in widget.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/317636","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=317636"}],"author":[{"embeddable":true,"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/sirapix"}],"wp:attachment":[{"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=317636"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=317636"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=317636"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=317636"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=317636"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ky.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=317636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}