DOCS · CONNECT

Connect the assistant you already use.

Hosted assistants use account sign-in. Command-line clients use a per-person, per-account access key. Both paths enforce the same account, workspace, billing, review, usage, and revocation rules.

Open your Retail Reason account →Troubleshoot a connection →

SUPPORTED AT LAUNCH

Three clients. Two connection paths.

01 · HOSTED SIGN-IN

Claude hosted

Use Retail Reason account sign-in, choose the intended account and workspace, then return to the assistant.

See durable requirements →

02 · ACCOUNT ACCESS KEY

Claude Code

Create a personal account key, add it through the client’s secret or environment configuration, reload the client, and verify the connection.

See durable requirements →

03 · ACCOUNT ACCESS KEY

Codex CLI

Create a personal account key, add it through the client’s secret or environment configuration, reload the client, and verify the connection.

See durable requirements →

ChatGPT is planned, disabled, and not a supported launch client. Its status does not affect Claude hosted, Claude Code, or Codex CLI.

CONNECTION PATHS

Use the path for your client.

CLAUDE HOSTED · SIGN IN

Authorize the account and workspace.

From Claude’s connection controls, choose Retail Reason and complete the Retail Reason account sign-in. If your Claude workspace limits who can add connections, its owner or administrator must make the connection available. Choose the intended Retail Reason account and workspace during authorization, return to Claude, and ask a test question.

Client labels and screen placement can change. These are the durable requirements, not a promise that every Claude interface uses the same button names.

CLAUDE CODE · ACCESS KEY

Install the Retail Reason plugin.

  1. Create a personal Retail Reason access key and keep it out of chats, files, and repositories.

  2. Add the Retail Reason marketplace in Claude Code:

    /plugin marketplace add https://github.com/RetailReason/retail-reason-plugins

  3. Install the plugin:

    /plugin install walmart-advisor@walmart-advisory
  4. When prompted, paste the access key and leave the shipped server URL at https://mcp.retailreason.com/mcp. The plugin and marketplace identifiers remain unchanged for compatibility even though the product is Retail Reason.
  5. Restart Claude Code, confirm the plugin is available, and ask a Walmart supplier, Sam’s Club supplier, or Walmart Marketplace question.

Setup verified September 1, 2026. If Claude Code changes its interface, the marketplace and plugin identifiers above remain the durable installation values.

CODEX CLI · ACCESS KEY

Add the hosted MCP server.

  1. Create a personal Retail Reason access key.

  2. Set it in the environment before launching Codex:

    export WADV_LICENSE_KEY="YOUR_RETAIL_REASON_ACCESS_KEY"

  3. Add this block to ~/.codex/config.toml, or to .codex/config.toml in a trusted project:

    [mcp_servers.walmart_advisor]
url = "https://mcp.retailreason.com/mcp"
bearer_token_env_var = "WADV_LICENSE_KEY"
tool_timeout_sec = 360
  4. Restart Codex and run codex mcp list to confirm the server appears. Then ask a Walmart supplier, Sam’s Club supplier, or Walmart Marketplace question.

Setup verified September 1, 2026. The 360-second timeout allows the service’s bounded retry and answer-review path to finish.

AFTER CONNECTION

Choose the context, test it, and keep the limits visible.

Choose the account and workspace

A person may belong to more than one account, but each sign-in session or key is bound to one account. If you can reach one workspace, it is selected automatically. If you can reach several, Retail Reason asks you to select one before answering; a session cannot be reused against a different workspace.

Know what the service can reach

Retail Reason never connects to retailer systems or retrieves their data. What travels is what you choose to type or paste: the question, plan, draft, or situation you describe. Retail Reason holds no portal credentials and has no Walmart account access. The security page has the full data flow.

Verify the connection

List your workspaces, select the intended one, and ask one test question for Walmart suppliers, Sam’s Club suppliers, or Walmart Marketplace sellers, as applicable. A connected account returns an answer ID, workspace name, review status, public usage state, as-of date, and confidence class.

Reconnect or revoke

An owner or administrator can revoke account access; a CLI user can also revoke an individual access key. Account and workspace configuration remains recoverable for 30 days after access ends. If a working setup stops authenticating, repeat the relevant path above, then use troubleshooting.

IF YOU GET STUCK

Support comes directly to Matt.

Include your account name, the client you are connecting, and roughly when the problem happened. Never include an access key. Matt aims to reply within one business day when working; an away message gives the return date.

[email protected] →