CartAgent Site Operator

AI shopping assistant and approval-gated site-operations workflow for WooCommerce stores.

CartAgent Site Operator helps WooCommerce merchants and ecommerce agencies handle two practical jobs:

• help shoppers move from natural-language intent to relevant products and cart action;
• turn website-change requests into structured previews that a merchant approves before anything goes live.

The product is deliberately merchant-controlled. CartAgent can prepare, preview and log changes, but production publishing should remain scoped, permissioned and approval-gated.

What It Does

Shopper Assistance

CartAgent gives a WooCommerce store a catalogue-aware assistant. A shopper can ask questions such as:

I need a gift under $50 for someone who likes coffee.

CartAgent searches the store catalogue, recommends relevant products with short reasons, and guides the shopper toward cart or checkout.

Approved Site Operations

Store owners and agencies already receive website-change requests by email, chat and tickets. CartAgent converts those requests into a structured workflow:

1. read the request;
2. identify the affected product, page or field;
3. draft the proposed change;
4. show a preview and risk notes;
5. wait for approval;
6. apply through scoped permissions and log the change.

Agent Commerce / MCP

CartAgent can expose controlled shopping tools for approved AI agents, including product search, product detail lookup, cart preparation and checkout handoff.

Production access should be token-gated, scoped and logged.

Public Endpoint

The public product site is:

https://www.cartagent.store/

The MCP-compatible demo endpoint is documented from the product site. Production users should use issued store identifiers and access controls rather than public demo settings.

Guardrails

CartAgent should not be described as:

• a guaranteed revenue-uplift tool;
• an unchecked autonomous publisher;
• a replacement for the merchant, agency or developer;
• a place to paste production secrets into a public demo.

Use language such as:

• merchant-approved;
• catalogue-aware;
• chat-to-checkout;
• approval-gated site operations;
• scoped permissions and audit trail.

Example Site-Operation Change

{
  "request": "Update the espresso bundle product page for the weekend offer and add a short note about free shipping.",
  "operator_output": {
    "target": "Espresso Starter Bundle",
    "proposed_change": {
      "sale_badge": "Weekend offer",
      "shipping_note": "Free standard shipping on this bundle this weekend."
    },
    "risk_flags": [
      "Confirm offer dates before publishing",
      "Confirm margin impact before applying sale language"
    ],
    "status": "preview_ready",
    "approval_required": true
  }
}

Repository Boundary

This public repository is for product positioning, public documentation and demo-safe examples. It should not contain:

• live customer data;
• store API keys;
• Stripe, Coinbase, OpenRouter or WooCommerce credentials;
• internal Oakhampton operations files;
• private deployment configuration.

Contact

• Website: https://www.cartagent.store/
• GitHub: https://github.com/Oakhampton1111/cartagent

Licence

MIT, unless otherwise stated in individual files.