Market and competitors
Updated 28 September 2026. The founder's direction now includes agents for both store operations and customer conversations. Store Deputy remains a concept, with no product implementation in this repository. Competitor capabilities below are based on public documentation, not hands-on tests.
Position Store Deputy as a complete agent product for running a store and serving its customers, with commerce skills and connected tools. Compare complete products with complete products; classify connectors, specialist extensions and workflow builders separately.
Primary benchmarks
| Benchmark | Main user and job | Relevance to Store Deputy |
|---|---|---|
| Shopify Sidekick | Merchant assistance inside Shopify: store tasks, recommendations, reviewed changes and background work | Primary benchmark for the owner/operator agent. Our proposed route starts with OpenCart and expands to other platforms as demand justifies it. |
| Gorgias | Customer conversations, pre-sale assistance and post-sale service, with a helpdesk for the merchant's team | Primary benchmark for the customer-facing agent. It becomes a direct competitor for that part of our intended offering. |
| StoreAgent | WooCommerce product combining customer chat, catalog content, insights and managed MCP access | Close competitor across customer and owner workflows in the self-hosted store segment; assess the complete product, not only its connector. |
This is our product-comparison shortlist, not a claim that every other product is broken or commercially irrelevant. The wider list below remains useful for tracking substitutes and integration options.
Gorgias: customer experience with operational actions
Gorgias is primarily organized around serving shoppers. Its product combines an AI Agent, a shared inbox, store/customer context and handoff to human support. It also promotes product recommendations and pre-sale engagement. It is broader than a storefront chat widget: the merchant's support team works in its helpdesk. Source: Gorgias.
It can also change backend data. Its action documentation describes cancellation, shipping-address changes and subscription operations, with multi-step actions, conditions and optional shopper confirmation. Actions can be attached to skills. The inspected action guide specifies connected Shopify stores; do not assume every listed platform supports identical actions. Source: Gorgias actions.
The useful distinction is the job being delegated: resolving a shopper request versus carrying out an owner's broader store work. Backend access alone does not make Gorgias a general store-administration agent, and its customer focus does not mean it lacks operational capabilities.
For Store Deputy, learn from context continuity, human handoff, merchant-defined policies and completion of a customer request. Having agents or skills is not unique by itself. We need to prove the quality and breadth of the actual workflows.
StoreAgent: a packaged WooCommerce competitor
Reviewed 28 September 2026. StoreAgent targets WooCommerce exclusively. It combines shopper conversations, catalog content and store insights inside WordPress, with connections to external AI assistants. This makes it relevant to both intended Store Deputy roles. OpenCart support is not advertised; our OpenCart-first route addresses a different platform, not an uncontested product category.
| Area | Published offering | Implication for Store Deputy |
|---|---|---|
| Customer service | Answers from store information, checks current price/stock and hands conversations to the team | Compare answer quality and escalation on real merchant questions |
| Catalog work | Bulk descriptions, tags, review summaries and image alt text; content drafts for approval | Content generation alone is insufficient differentiation |
| Store access | Managed MCP gateway for external assistants, including Claude and ChatGPT | A connector is one part of their broader product |
Sources: product overview and agent offering. The vendor also markets unattended work; that does not establish that our exact daily-comment-check scenario is available.
Agent product versus MCP integration
StoreAgent's own content and customer agents are distinct from using an external assistant through its gateway. Its MCP page lists 24 built-in abilities and support for additional registered WordPress abilities. It describes read-only access by default, separately enabled writes, revocation and a 30-day activity log. These are meaningful comparison points, not evidence of tested security or identical coverage across stores. Source: managed MCP.
Published pricing
Snapshot in USD, checked 28 September 2026:
| Plan | Listed monthly price | AI chat replies | AI tasks |
|---|---|---|---|
| Lite | Free | 50, one-time | 200, one-time |
| Growth | $19 | 500 | 500/month |
| Pro | $49 | 5,000 | 2,500/month |
| Business | $249 | 50,000 | 10,000/month |
The pricing page includes MCP on all plans, unlimited websites on paid plans and a shared task allowance for generators and MCP actions. Lite credits do not renew. Another agent page mentions a monthly free chat allowance; use the explicit pricing-page limits pending clarification. These prices are competitive context, not evidence of what merchants will pay us. Source: pricing.
What we should prove
Our proposed distinction is reliable owner work on OpenCart: supplier-file matching, reviewable price changes, verified execution and useful follow-up when a task needs the owner. Test these complete workflows against alternatives before claiming an advantage. StoreAgent already combines agents, tools and customer context; those nouns are not a moat.
Still unverified: supplier-file reconciliation, rollback after partial writes, configurable scheduled comment checks and the exact boundary of native owner chat versus an external MCP client. Missing evidence is not proof that StoreAgent lacks a capability. Installation and hands-on workflow tests remain outstanding.
WooCommerce: tools and a separate agent experiment
WooCommerce native MCP exposes store operations to an external AI client. The server supplies discoverable tools and applies permissions; it does not by itself supply a complete merchant-agent application. Its documented status is developer preview. Treat it as an integration option and a component of a do-it-yourself alternative, rather than a like-for-like Store Deputy product.
There is an important distinction: WooCommerce for Claude is a separate experiment adding store context and skills to an external agent. We should not describe the whole ecosystem as having no agent path or no skills. Claude plus that integration may substitute for part of our intended offering; the experiment does not establish a fully packaged, production-equivalent service.
“Half our functionality” expresses a qualitative distinction, not a measured feature ratio. Our comparison should explicitly separate these layers:
| Layer | Responsibility | Intended Store Deputy offering |
|---|---|---|
| Tools and connectors, including MCP | Read data and perform authenticated platform operations | Supported commerce connections with explicit capabilities |
| Skills | Describe how to carry out a commerce task, including rules, inputs and exceptions | Maintained procedures for owner work and customer service |
| Agents | Interpret intent, select skills/tools, follow multi-step work and resolve uncertainty | Agents with distinct roles and scoped authority |
| Product and operation | Onboarding, store context, task lifecycle, approvals, history, recovery and handoff | A service the merchant can delegate work to without assembling the pieces |
This table defines intended scope. Agentfy is the intended platform foundation; it does not establish that these Store Deputy workflows are already implemented. Skills guide work; enforced permissions must live outside the prompt.
One store, two agent roles
Accepted product direction; detailed workflows and release order remain proposals. The owner remains the buyer and authority holder. Store Deputy can serve the owner directly and serve shoppers on the owner's behalf.
| Role | Intended responsibilities | Boundary |
|---|---|---|
| Operations agent | Catalog preparation, supplier updates, price proposals, store questions and recurring tasks | Owner/team permissions, reviewable changes and recorded execution |
| Customer agent | Product questions, recommendations, delivery/returns policy explanations, scoped order lookup and escalation | Public knowledge plus authenticated access to that customer's permitted data; no inherited admin privileges |
Both roles should use maintained store knowledge and commerce skills. They need different conversations, permissions and information access. Supplier costs, margins and other customers' orders must never leak into shopper answers. Customer requests and imported content must not grant the agent additional authority.
Illustrative future workflow: shoppers repeatedly ask about a missing product specification; the customer agent records the gap and hands it to the operations agent; the latter prepares a source-backed catalog correction for owner review; once published, the customer agent can use the updated information. This is a proposed workflow, not a demonstrated integration.
For the customer direction, propose a first slice of product/policy answers, verified order-status lookup and human handoff. Order mutations, refunds and discounts need separately defined authorization before launch. A shared agent foundation does not eliminate the work of building channels, identity checks, evaluations and support operations.
The supplier-update MVP remains the current launch recommendation, not an approved limit on the whole product. The customer direction should be tested with merchants and sequenced explicitly rather than silently added to its delivery estimate. Measure owner work by time per correctly completed task, and customer service by correct resolution, appropriate escalation and successful handoff; message volume alone is not success.
Other alternatives and signals
| Alternative | Classification | Why retain it in the research |
|---|---|---|
| PrestaShop AskAI | Native assistant direction on a roadmap | Track availability; a roadmap is not a shipping claim |
| Knowband OpenCart AI Admin Assistant | Specialized admin extension marketed around questions and analytics | Relevant to OpenCart budgets and expectations; inspected material does not establish parity with our intended agent product |
| Metorik | Analytics and automation product | A substitute for reporting jobs, not the full intended scope |
| n8n with WooCommerce | Workflow-building alternative | Agencies can assemble automation; compare setup and maintenance effort |
| Imports, bulk editors and agencies | Existing ways to complete the work | A pilot must improve on the merchant's actual baseline |
These are secondary comparisons, not equivalent full-agent competitors. We have not tested them and should not label them nonfunctional.
Positioning and platform strategy
Proposed positioning: “Commerce agents for your team and your customers.” The differentiating hypothesis is a maintained commerce service that connects owner operations with customer requests, with useful skills and controlled execution across supported platforms. This is a direction to validate, not proof that no competitor could offer it.
OpenCart remains the first integration target. WooCommerce is both a future platform opportunity and a source of reusable integration primitives. MCP availability can reduce connection work but does not replace the agent product. Shopify Sidekick sets the owner-experience benchmark; Gorgias sets the customer-service benchmark; StoreAgent benchmarks a packaged WooCommerce agent offering across both roles. Avoid a claim of feature parity until measured on the same tasks.
OpenCart's marketplace and agencies are possible distribution channels. Pricing should reflect the delivered workflows and their cost; a connector or extension price is not directly comparable to a managed agent service. The current commercial tests cover the operations pilot; customer-agent packaging and conversation costs require a separate experiment.
Agent-mediated discovery and checkout is a further market, distinct from our two agent roles. Adobe's commerce standards announcement is a signal to monitor, not a reason to add checkout infrastructure to the first release.
Continue with customer needs, evidence and limits, and validation.