Title: StoreGauge AI for WooCommerce Author: StoreGauge AI Published: 27 سبتمبر، 2026 Last modified: 30 سبتمبر، 2026 --- البحث عن الإضافات ![](https://ps.w.org/storegauge-ai/assets/banner-772x250.png?rev=3715368) ![](https://ps.w.org/storegauge-ai/assets/icon-256x256.png?rev=3715368) # StoreGauge AI for WooCommerce بواسطة [StoreGauge AI](https://profiles.wordpress.org/storesidekick/) [تنزيل](https://downloads.wordpress.org/plugin/storegauge-ai.0.9.0.zip) * [تفاصيل](https://ar.wordpress.org/plugins/storegauge-ai/#description) * [المراجعات](https://ar.wordpress.org/plugins/storegauge-ai/#reviews) * [التنصيب](https://ar.wordpress.org/plugins/storegauge-ai/#installation) * [التطوير](https://ar.wordpress.org/plugins/storegauge-ai/#developers) [الدعم](https://wordpress.org/support/plugin/storegauge-ai/) ## الوصف StoreGauge AI for WooCommerce adds a private AI assistant to your WordPress dashboard. Ask questions like “How did sales trend last week?”, “Which products are running low?” or “Who are my best customers?” — and get answers from your live store data, with automatic charts, quick prompt chips and a short daily briefing on issues that deserve attention. Bring your own key: connect Google Gemini, OpenRouter or any OpenAI-compatible provider— including a custom endpoint like GMI Cloud or your own local server. Your API key and your store data travel directly from your server to the provider you choose: no middleman service, no data passing through us. Safe by design: the assistant is read-only — it can analyze revenue, orders, stock, customers, coupons and reviews, but it can never modify anything. Customer emails are masked, every AI access is written to an audit log, and everything is OFF until you enable it. Also included: read-only store abilities for the WordPress 7.1 Abilities API, so external AI assistants (via an MCP adapter) can query the same data — with the same masking and audit trail. StoreGauge AI connects your WooCommerce store to the AI assistant of your choice— safely. * **AI chat sidebar in wp-admin** — ask about your shop in plain language. Answers stream in live, and the AI calls the read-only store tools itself with its own arguments: “compare last 7 days vs last 30 days” just works. Pick the model per chat from a dropdown with capability badges (Vision, Tools, context size), attach a product photo or a text file, and every conversation is stored in your own database. Uses YOUR API key with any OpenAI-compatible provider (OpenAI, Gemini, OpenRouter, Groq, Mistral, Ollama, LM Studio…). Your key and your data never pass through us. * **Read-only store abilities** for the WordPress Abilities API / official MCP adapter: revenue summaries, recent orders, low-stock products, top sellers, product prices with unit costs (so the AI can reason about pricing and margins). Every ability is OFF by default and re-checks permissions on every single call. * **Local audit log** — every AI-visible action is recorded in your own database, with customer contact details masked and automatic pruning after 30 days (filterable). #### External services This plugin contacts one external service: the AI provider **you** choose and configure in the settings. Nothing is sent anywhere until you enable a feature and paste your own API key. When you use the chat sidebar (or connect an MCP client), your own server sends requests directly to the provider base URL you configured, for example: * Google Gemini (`https://generativelanguage.googleapis.com/v1beta/openai`) — [Terms of Service](https://policies.google.com/terms), [Privacy Policy](https://policies.google.com/privacy) * OpenAI (`https://api.openai.com/v1`) — [Terms of Use](https://openai.com/policies/terms-of-use), [Privacy Policy](https://openai.com/policies/privacy-policy) * OpenRouter (`https://openrouter.ai/api/v1`) — [Terms of Service](https://openrouter.ai/terms), [Privacy Policy](https://openrouter.ai/privacy) What is sent with each chat request: * Your chat message and the recent conversation history (last 10 messages). If you attach a product photo or a text file, that attachment is included too — the AI provider needs it to answer. * The results of read-only store tools the AI requests: revenue summaries, order lists (customer contact details masked), low-stock products, top sellers, product prices and costs. This data is included in the request so the provider’s AI model can answer. * Your API key, as an authorization header, sent only to the base URL you configured. The plugin author receives nothing: no telemetry, no analytics, no proxy server. The API key is stored in your own site’s database and never leaves your server except to call the provider you configured. #### Privacy Store data goes directly from your server to the AI provider YOU configure. The plugin author receives nothing. #### Roadmap * One-click Claude Desktop connect via the official MCP adapter (STDIO config) * Pro: weekly AI reports, restock lists, bulk product content, cart-recovery drafts— with dry-run + human approval on every write ## لقطات الشاشة [⌊Connect any AI provider with your own API key — OpenRouter, Google Gemini, or any OpenAI-compatible endpoint.⌉⌊Connect any AI provider with your own API key — OpenRouter, Google Gemini, or any OpenAI-compatible endpoint.⌉[ Connect any AI provider with your own API key — OpenRouter, Google Gemini, or any OpenAI-compatible endpoint. [⌊Ask about your store in plain language: daily sales for the last 90 days with an automatic chart and the top-performing days.⌉⌊Ask about your store in plain language: daily sales for the last 90 days with an automatic chart and the top-performing days.⌉[ Ask about your store in plain language: daily sales for the last 90 days with an automatic chart and the top-performing days. [⌊Attach a product photo and a vision model writes SEO descriptions, keywords and alt text for it.⌉⌊Attach a product photo and a vision model writes SEO descriptions, keywords and alt text for it.⌉[ Attach a product photo and a vision model writes SEO descriptions, keywords and alt text for it. [⌊Customer privacy is built in: emails are always masked in every answer.⌉⌊Customer privacy is built in: emails are always masked in every answer.⌉[ Customer privacy is built in: emails are always masked in every answer. [⌊A daily briefing surfaces what deserves attention — stuck orders, low stock — with one-click follow-ups.⌉⌊A daily briefing surfaces what deserves attention — stuck orders, low stock — with one-click follow-ups.⌉[ A daily briefing surfaces what deserves attention — stuck orders, low stock — with one-click follow-ups. ## التنصيب 1. Install WooCommerce and WordPress 6.9+. 2. Install it: from Plugins Add New, search “StoreGauge AI”, click Install, then Activate. WordPress handles the download, and from then on every future update shows up in Dashboard Updates — or installs itself in the background if you leave auto-updates on. There is nothing to re-upload and no settings to redo. 3. Alternatively, download the ZIP from the plugin page and upload it via Plugins Add New Upload Plugin. 4. Go to Settings StoreGauge AI, enable what you need, and paste your AI provider API key. 5. Optional, for MCP only: if you want to connect an external AI agent — Claude, Cursor, ChatGPT, Codex or any other MCP client — to your store, you also need the official WordPress MCP Adapter. Without it there is no MCP endpoint and external agents cannot connect; the chat sidebar above is unaffected and needs nothing extra. Open Settings StoreGauge AI Connect AI assistants (MCP) and click “Install adapter” to add it in one click, with a manual download link if you prefer. ## الأسئلة المتكررّة ### Who pays for the AI usage? You do — directly to the provider you choose (Google, OpenAI, OpenRouter, Groq…). Free tiers work fine. The plugin author never sees your key or your data. ### Can the AI change my store? No. StoreGauge AI is read-only by design. Every ability only describes data, and everything is logged locally. ### Where is the audit log? Settings StoreGauge AI shows the most recent audit events. Entries are stored as private records in your own database and pruned automatically after 30 days. Developers can change retention with the `storegauge_audit_retention_days` filter (set it to 0 to disable pruning). ### Where are my conversations stored? In your own site’s database — never on our servers and never in the cloud. Each wp-admin user sees their own conversation; it is trimmed to the last 50 messages and pruned after 30 days. The “＋” button in the chat starts a fresh one. ### Can it read images? Yes, when the selected model supports vision (look for the Vision badge in the model dropdown). Attach a product photo and ask for a description or alt text; plain-text files (.txt, .csv, .md, .json) are also supported. ## المراجعات لا توجد مراجعات لهذه الإضافة. ## المساهمون والمطوّرون “StoreGauge AI for WooCommerce” هو برنامج مفتوح المصدر. وقد ساهم هؤلاء الأشخاص بالأسفل في هذه الإضافة. المساهمون * [ StoreGauge AI ](https://profiles.wordpress.org/storesidekick/) [ترجمة ”StoreGauge AI for WooCommerce“ إلى لغتك.](https://translate.wordpress.org/projects/wp-plugins/storegauge-ai) ### مُهتم بالتطوير؟ [تصفّح الشفرة](https://plugins.trac.wordpress.org/browser/storegauge-ai/)، تحقق من [مستودع SVN](https://plugins.svn.wordpress.org/storegauge-ai/)، أو الاشتراك في [سجل التطوير](https://plugins.trac.wordpress.org/log/storegauge-ai/) بواسطة [RSS](https://plugins.trac.wordpress.org/log/storegauge-ai/?limit=100&mode=stop_on_copy&format=rss). ## سجل التغييرات #### 0.9.0 * New: profit by product. Ask which products actually made money over a period and get a real per-product figure, taken from the cost recorded on each order at the time it was paid, not from today’s price. Each product reports its own cost coverage, and a product with no recorded cost reports no profit rather than a misleading zero. The totals match the store-wide gross profit exactly. * The installation instructions now describe the normal route (search for the plugin in WordPress and install it in one click) and explain that future updates arrive through the WordPress dashboard, so there is nothing to re-upload each time. #### 0.8.9 * Gross profit now also reports covered_revenue, the part of revenue that actually has a recorded cost. The margin is calculated from that figure, and the result now says so explicitly, so an assistant connecting over MCP cannot misread the margin as a share of total revenue. #### 0.8.8 * The setup reminder now also appears if you remove your last connected AI provider later, not only on a brand-new install. #### 0.8.7 * The chat assistant is now available as soon as you activate the plugin, and if no AI provider is connected yet it opens with a single button that takes you straight to the settings screen. Connecting an external AI agent over MCP is still opt-in. #### 0.8.6 * The installation instructions now spell out that the WordPress MCP Adapter is required only for connecting an external AI agent, that it can be added in one click from the settings screen, and that the chat assistant does not need it. #### 0.8.5 * Privacy fix: replies no longer cause WordPress to load emoji images from WordPress. org. The assistant writes emoji often, and WordPress was turning each one into a request to its own servers — one reply measured eleven of them, revealing the shop manager’s IP address to a third party. Emoji still display, using your system’s own characters. No images are loaded from anywhere outside your site. #### 0.8.4 * Replies render more of the formatting the assistant uses. Task lists (“- [ ] add your costs”) now show real checkboxes instead of raw brackets, nested lists keep their structure instead of flattening, and a plain typed web address becomes a clickable link. * An image in a reply is shown as a normal link rather than loading the remote picture. This keeps the promise that StoreGauge makes no external requests from your admin. #### 0.8.3 * Fixed: raw markdown syntax showing in replies. A heading that the assistant ran onto the end of a sentence (“I’ll pull the data.## Best day”) displayed its ## markers instead of a heading, and a stray escaped asterisk (*) appeared literally when the assistant left emphasis unclosed. Headings are now recognised mid-line and stray escapes are cleaned up. Ordinary text containing a # is unaffected, and code is untouched. #### 0.8.2 * Fixed: the Copy for LLM prompt split the Windows Claude Desktop config path across a line break, so an assistant following it received a broken path. The prompt also now lists all 14 abilities including gross profit. #### 0.8.1 * Fixed: gross profit and the other period tools disagreed on revenue whenever a refund existed. Gross profit nets refunds, because a refunded sale is not revenue and WooCommerce does not rewrite the stored cost snapshot either, while the revenue, daily and category tools report revenue before refunds. Rather than leave two different revenue figures unexplained, every gross profit answer now also returns revenue_gross and refunded, so the two reconcile exactly. #### 0.8.0 * New: realised gross profit. The assistant can now report what the store actually made over a period, per month, using the cost (COGS) snapshot WooCommerce stores on each order when it is paid, rather than today’s catalogue prices. * Profit is only ever calculated on order lines that have a recorded cost. Every answer carries a coverage percentage alongside the profit, and revenue on lines with no recorded cost is reported separately and excluded, because its cost is genuinely unknown. When no line has a cost, the assistant says the records are missing instead of reporting zero profit. * Coverage is assessed per order line rather than per order, so an order mixing a costed and an uncosted product is never counted as fully costed. * Refunds are netted out of both revenue and cost for the period. #### 0.7.11 * The assistant no longer invents totals it cannot support. Asked “so what profit would that have been?” it used to multiply a margin percentage by revenue and present the result as a rough estimate, and it could also subtract its way to a COGS figure. Both are now forbidden outright, even when labelled rough, ballpark or indicative: when the data cannot support a total, the assistant says so, names what is missing, and stops. #### 0.7.10 * Top sellers now accepts a day range like the other period tools (1-365, default 30). It previously reported 30-day numbers no matter what a client asked for, because the window was hardcoded and the parameter was not declared. #### 0.7.9 * The Copy for LLM prompt now states in one line that the endpoint also lists WordPress and WooCommerce abilities, so the 13 StoreGauge tools are never mistaken for the whole list. #### 0.7.8 * Fixed: all period tools (revenue, daily sales, categories, top sellers/customers, refunds) now share one reporting window of N calendar days including today, so their totals always reconcile; previously the daily chart silently dropped orders paid on the partial first day of the window. * Fixed: the refund rate is now measured against PAID orders (the only ones that can be refunded); pending, on-hold and cancelled orders no longer dilute the base. * Improved: ability and tool descriptions now state their exact scope (for example inventory value covers stock-managed products only) so assistants do not read different tools as contradicting each other. #### 0.7.7 * The connect prompt now carries the hard-won details from a real OpenCode session: desktop CLI path, no hot reload (restart required), “oauth”: false on remote entries, strip the spaces from the application password before base64, the correct verify command, and an honest inventory of everything the endpoint lists (13 read-only StoreGauge tools + WordPress/WooCommerce abilities, whose write tools the endpoint refuses; a WordPress user without edit rights makes that permanent). #### 0.7.6 * Fixed: UI alignment polish — provider logos are now identical in size (the Google tile grew 2px from its border), action buttons line up across cards, icons sit centered in buttons and pills, and chat bubbles are exactly the same width. #### 0.7.5 * The connect wizard now uses clean, generic line icons (adapter, abilities, credential, actions) and a row of supported client names — no third-party logos are bundled, by design. #### 0.7.4 * The Copy for LLM prompt now also offers the direct Streamable HTTP route (for clients with native remote-MCP support and a custom Authorization header) before falling back to the official stdio proxy, ends with one concrete self-test call, and is shown on the page so you can read it before copying. * The wizard now lists what the assistant can do (13 read-only tools) and where each client config lives. #### 0.7.3 * Improved: the Copy for LLM prompt now targets the client it is pasted into (Claude Code, OpenCode, Claude Desktop, Cursor), follows each client official config location and CLI syntax, and prefers the user-scope file so the connection works in every project. #### 0.7.2 * Fixed: the Copy for LLM button now produces the full setup prompt (a copy error stopped it from working). #### 0.7.1 * New: product prices and recorded unit costs are now exposed to external MCP assistants( 13th read-only ability). * The connect wizard follows the official MCP client configuration formats (one mcpServers config for Claude Desktop/Claude Code/Cursor + one for OpenCode), uses copy icons, and can copy a ready-to-paste setup prompt for other AI assistants— with the application password deliberately left as a placeholder so it never ends up in a chat. * The wizard explains that a lost application password can simply be replaced ( old ones revoked from the profile). #### 0.7.0 * New: Connect AI assistants (MCP) wizard — one-click install of the official WordPress MCP Adapter, application-password creation, ready-to-paste client configuration for Claude Desktop, Claude Code and Cursor, and a connection test. * The wizard detects what is already set up and only asks for what is missing; every step is audit-logged. #### 0.6.4 * Fix: charts no longer break on long ranges — 90-day views now render as clean weekly buckets with readable date labels, instead of hairline bars with clipped fragments. #### 0.6.3 * Fix: the settings page now shows the reason when a provider cannot be added ( for example adding a provider that is already connected) instead of failing silently. #### 0.6.2 * New: provider model catalogs auto-refresh once a day when the chat opens — new provider models appear without a manual reload. * New: friendly guard against adding a connected provider twice as a custom provider. * Improvement: empty text files and unreadable images are now caught before sending, with clear warnings. #### 0.6.1 * New: margin insights — a 12th read-only ability computes per-product profit margins from recorded unit costs (COGS), with honest counts of products missing cost data and guidance to enable it. #### 0.6.0 * Renamed the plugin to StoreGauge AI for WooCommerce. #### 0.5.6 * Fix: attaching an unsupported file now shows a clear message about allowed file types instead of the generic API-key error. #### 0.5.5 * Fixed: math formulas sent by the AI now render as plain readable text instead of raw LaTeX code, and the assistant is instructed to avoid LaTeX markup altogether #### 0.5.4 * Fixed: text domain now matches the plugin slug and all database queries use identifier placeholders (full WordPress.org Plugin Check compliance) * Improved: clearer settings screen — the MCP/API toggle now explains that an external MCP adapter plugin connects AI assistants, and every access is audit-logged; the chat toggle explains where conversations live * Improved: consistent button and input heights across the provider cards, and card action buttons optically aligned with the provider subtitle * Improved: the “Load models from provider” button now has a tooltip explaining it re-fetches the current list (run it again when a provider adds models) #### 0.5.3 * Fixed: removing a model in the settings now immediately removes it from the chat model picker (the picker re-fetches instead of using a page-old list) * Fixed: if your saved chat model is removed from its provider, the assistant falls back to another model of the same provider instead of silently using the removed one * Fixed: asking the AI to reveal a customer now gets a polite privacy explanation together with the masked data, instead of a bare refusal * Fixed: monetary amounts always follow the store currency set in WooCommerce ( verified with EUR and USD) #### 0.5.2 * Fixed: the quick prompt chips are no longer cut off by their own scrollbar or squeezed on short screens * Fixed: wide tables and long date ranges no longer create a horizontal scrollbar that covers the last chat lines — tables wrap to fit and long ranges shrink the chart bars #### 0.5.1 * Fixed: the coupon usage ability silently reported “no coupons” on WooCommerce 11, where an API it relied on was removed — coupons are now listed correctly with their discount type and usage count * Fixed: charts now survive a page reload — the daily-sales series is stored with the message and redrawn on restore, for every provider and model * Fixed: replies now reliably follow the language you write in, even for small free models that previously drifted mid-conversation * Improved: conversation memory is now safe for every model — earlier assistant replies no longer re-enter the AI context (weak models copied stale numbers from them or drifted into another language); your questions stay in context and the assistant re-fetches live data for follow-ups * Improved: clearer custom-provider form examples (GMI Cloud endpoint) and a generic“ Model name” hint, since model ids differ per provider * Improved: new server icon for custom providers (Lucide, ISC) #### 0.5.0 * New: 7 more read-only abilities — daily sales series (with automatic charts in the chat), top customers (masked), coupon usage, refund rate, review summaries, sales by category, inventory value. The assistant now answers trends, customers, coupons, refunds and inventory questions from real data * New: quick prompt chips above the input — one tap for revenue, sales trend, low stock, top sellers and pricing analysis * New: proactive daily briefing — a badge on the chat bubble shows deterministic findings (stuck orders, stock running out, revenue drops, refund spikes), each with a one-tap follow-up question; findings are computed locally from your database, never invented by the AI * Improved: the assistant is now explicitly instructed never to invent or estimate numbers — when data is missing it says exactly what it cannot see #### 0.4.2 * Improved: chat footer alignment — paperclip, input text and send arrow are now properly centered #### 0.4.1 * Improved: full visual redesign of the chat panel — purple brand header, restyled bubbles, model dropdown, badges, attachment chips with file size, and message timestamps #### 0.4.0 * New: multiple AI providers side by side — connect Google Gemini, OpenRouter and any custom OpenAI-compatible endpoint, each with its own API key * New: per-provider model lists — load the catalog automatically, remove models you don’t want, or add models by hand * New: the chat model dropdown groups models under each connected provider * Improved: providers that disconnect and models the provider can’t run are remembered and hidden * Improved: existing single-provider setups migrate automatically #### 0.3.2 * Improved: the whole chat UI now uses one consistent inline SVG icon set (Lucide, ISC license) — send/stop, plus, paperclip, copy, close, chevron and check marks #### 0.3.1 * Fixed: models selected from the dropdown now work on providers whose /models returns prefixed ids (e.g. “models/gemini-2.5-flash”) * Improved: answers render with smooth typewriter pacing so streaming is always visible, even with very fast models * Improved: model dropdown shows chat models first — non-chat models (TTS, music, robotics…) hide behind “show more” * Improved: settings field renamed to “Default model” with clearer description #### 0.3.0 * New: streaming replies — answers appear live as the AI writes them, with a stop button * New: model dropdown in the chat header, with capability badges (Vision, Tools, context size) loaded from your provider’s /models endpoint — with OpenRouter, one key unlocks hundreds of models. Non-chat models (TTS, music, robotics…) are tucked behind “show more” * New: attachments — product photos (vision models) and text files (.txt, .csv,. md, .json) * New: conversations persist in your own database, per wp-admin user, with “new chat” to clear * New: pricing analysis — the AI can read product prices, sale prices and unit costs (COGS, when recorded) to compute margins and suggest pricing * Fixed: customer PII masking now also enforced in the pricing ability #### 0.2.2 * New: full Markdown rendering in chat replies — headings, ordered/unordered lists, tables, links, inline code, code blocks, blockquotes, bold/italic/strikethrough; raw markers never leak into the UI * Housekeeping: dev-only files moved out of the release build #### 0.2.1 * Security: permission-denied probes from anonymous visitors no longer write audit rows (prevents database flooding via the abilities REST endpoint) * Audit log is pruned automatically after 30 days (filterable via `storegauge_audit_retention_days`; 0 disables pruning) * Abilities now declare explicit MCP exposure meta for the official MCP adapter * wp.org submission hardening: Requires PHP lowered to 7.2, directory-standard readme with external-services disclosure #### 0.2.0 * New: tool-calling chat — the AI requests store data itself with dynamic arguments( any date range 1–365 days) * New: retry with backoff on transient provider errors (429/500/503) * New: markdown rendering (bold/italic) in chat replies * New: replies always follow the language you write in * Improved: provider errors now fully logged to the audit trail #### 0.1.0 * Initial release: read-only store abilities, BYOK chat sidebar, audit log. ## ميتا Meta * Version **0.9.0** * Last updated **قبل 20 دقيقة** * Active installations **أقل من 10** * WordPress version ** 6.9 أو أعلى ** * Tested up to **7.1.2** * PHP version ** 7.2 أو أعلى ** * Language * [English (US)](https://wordpress.org/plugins/storegauge-ai/) * Tags * [AI](https://ar.wordpress.org/plugins/tags/ai/)[assistant](https://ar.wordpress.org/plugins/tags/assistant/) [chatbot](https://ar.wordpress.org/plugins/tags/chatbot/)[mcp](https://ar.wordpress.org/plugins/tags/mcp/) [woocommerce](https://ar.wordpress.org/plugins/tags/woocommerce/) * [عرض متقدم](https://ar.wordpress.org/plugins/storegauge-ai/advanced/) ## التقييم لم يتم تقديم أي مراجعات بعد. [Your review](https://wordpress.org/support/plugin/storegauge-ai/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/storegauge-ai/reviews/) ## المساهمون * [ StoreGauge AI ](https://profiles.wordpress.org/storesidekick/) ## الدعم لديك شيء لتقوله؟ بحاجة الى مساعدة؟ [عرض منتدى الدعم](https://wordpress.org/support/plugin/storegauge-ai/)