Store Deputy: a deputy for your store

Store Deputy connects an existing shop to agents running in Agentfy. The owner works through chat; the module gives the agent controlled access to real store data. OpenCart is the first platform.

Owner journey

The owner connects the module, signs in or creates an account, and returns to OpenCart. Store Deputy pairs the shop and automatically provisions its Admin Agent. The app contains a default team, agents, per-agent chat, account and billing.

Two agents

Admin Agent helps the owner with catalog and operational work. Frontend Agent helps shoppers with products and their own cart; it belongs to the Pro plan. These are product roles, not a claim that every function is available today.

How it works

Agentfy owns the harness and conversations. Store Deputy owns the interface, central MCP, permissions and approvals. The module exposes REST 1.0 and executes supported shop operations. The owner sees proposed changes and verified outcomes.

Delivery scope

First prove connection, real catalog reads and one approved base-price change. Supplier-file updates, product creation, reports, scheduled checks and shopper workflows follow as separate capabilities. The earlier supplier-update MVP was research, not the definition of the whole product.

Where to read next

Docs → Product → User Flow → Architecture → REST 1.0 → Plan.