FAQ · Merchanaut

Question 1

What does an agent actually do on the floor?

Accepted Answer

Each of the six agents (A-01 Inventory Sentinel, A-02 Catalog Spy, A-03 Price Officer, A-04 Restock Buyer, A-05 Order & Refunds Desk, A-06 Campaign & Inbox) owns one lane — stock, competitor catalog, pricing, replenishment, post-sale ops, and customer comms. They read the channels you wire in, watch the signals they were built for, draft their decisions, and route them through the governance bus. Agents never act outside their lane and never hit a customer-facing surface without passing Bob-Test.

Question 2

What do agents NOT do?

Accepted Answer

They do not talk to customers unprompted — A-06 fires segmentation-driven upsell loops only inside the tone and approval policy you set. They do not sign new supplier contracts; A-04 works the negotiated terms you already have. They do not overwrite pricing bands; A-03 reprices inside them. They do not bypass Bob-Test on a high-risk decision, even if the math would prefer it. Anything outside those lanes routes to the right human approver with full context.

Question 3

Can we see why a decision was made — and export it?

Accepted Answer

Yes. Every agent decision carries a per-row audit entry: which agent, against which signal, inside which pricing band or guardrail, with the timestamped input snapshot. The audit log is searchable in the dashboard, filterable by agent, SKU, and time window, and exportable as CSV or JSON for your board or auditor. Editor seats see decision detail; auditor seats get a read-only view of the same trail with the export button.

Question 4

How does Bob-Test keep us inside FTC, Colorado AI Act, Sherman, and CFAA?

Accepted Answer

Every high-risk decision runs through Bob-Test before it ships. FTC refusal happens when a move would breach Section 5 on unfair or deceptive practices. Colorado AI Act refusal happens when a high-risk automated decision would lack an impact assessment or consumer notice. Sherman refusal happens when the move looks like coordinated pricing across retailers — the system runs on your data, on your rails, by design. CFAA refusal happens when the Catalog Spy would ignore robots.txt, rate limits, or a CAPTCHA. Blocked moves are logged with the reason a regulator or board can read.

Question 5

Which tier fits a retailer at our size?

Accepted Answer

Launch (£1,800/month) fits retailers from £5M to £15M GMV running the Inventory Sentinel and Campaign & Inbox agents on a Shopify/Amazon/NetSuite stack. Scale (£6,500/month) is the upper-mid-market sweet spot from £15M to £120M GMV — the full six-agent fleet with Bob-Test on every pricing move. Enterprise (£18,000/month + onboarding) is for £120M to £1B retailers with board-grade governance needs. The three tiers line up in detail on /pricing — no per-SKU or per-decision fees that creep up when the agents perform well.

Question 6

How does the four-to-eight week pilot work?

Accepted Answer

Week one is data-source wiring against one category on one channel — ERPs, marketplaces, supplier catalogs, inboxes. Weeks two-to-three are guardrail setup: pricing bands, refund policy matrix, escalation paths. Week three is the dry-run — agents draft decisions, humans review them, no customer-facing surface fires. Week four onward we progressively enable live moves as your team signs off on each agent. By week eight the floor is operating, the audit trail is exporting, and your team owns it.

Question 7

Where does our data live, and who can see it?

Accepted Answer

Your data stays inside the deployment we set up for you. Editor seats map to named users on your team with role-based access — pricing agents cannot read refund-only data, for example. Auditor seats get a read-only view of the audit trail and export. SSO is included on Enterprise. We never sell data, never enrich it through a broker, and never feed it into a model trained on other retailers' floors — that is the structural promise of the per-tenant architecture.

Question 8

How do we trace a single SKU's lineage through the system?

Accepted Answer

Open the SKU page in the dashboard and you will see the full chain: the stock unit reading from A-01, the competitor deltas A-02 captured, the pricing band A-03 is working inside, the replenishment order A-04 placed, and any post-sale ticket A-05 closed against it. Every link carries the timestamped signal and the guardrail verdict below it. That view is what the board asks for first, and it is what regulators and PE diligence teams ask for second.

The eight questions retailers ask first.

Click a question. Read the answer.

Write to the team directly. We reply same-week.