DOCS · CONNECT

Connect the assistant you already use.

This guide covers optional assistant connections. You can instead open Retail Reason chat without a separate AI subscription. The chat guide covers files, saved conversations, and downloads. Hosted assistants use account sign-in; command-line clients use a per-person, per-account access key. Both connection paths enforce the same account, workspace, billing, review, usage, and revocation rules.

Open your Retail Reason account →Troubleshoot a connection →

SUPPORTED CONNECTIONS

Choose the connection for your assistant.

01 · HOSTED SIGN-IN

Claude hosted

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

See setup and 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 setup and 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 setup and requirements →

04 · HOSTED SIGN-IN

ChatGPT

Follow the steps below to connect using your Retail Reason sign-in. Setup help is available if you need it.

See setup and requirements →

ChatGPT uses a custom app connection. See its current status and requirements before choosing a client for your trial or subscription.

CONNECTION PATHS

Use the path for your client.

CLAUDE HOSTED · SIGN IN

Authorize the account and workspace.

Open Claude’s connector settings with Retail Reason prefilled, confirm the connection, 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.

Add Retail Reason to Claude →Add it for my organization (owners) →

These links only prefill the connector name and the server URL; Claude asks you to confirm before anything is added. You sign in with your Retail Reason account, not an access key.

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.

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

Add the Retail Reason marketplace in Claude Code:

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

Install the plugin:

/plugin install retail-reason@retail-reason

When prompted, paste the access key and leave the shipped server URL at https://mcp.retailreason.com/mcp. If you installed before September 6, 2026 under the earlier walmart-advisor@walmart-advisory identifiers, remove that marketplace with /plugin marketplace remove walmart-advisory and repeat the two steps above.
Restart Claude Code, confirm the plugin is available, and ask a Walmart supplier, Sam’s Club supplier, or Walmart Marketplace question.

Setup verified September 6, 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.

Create a personal Retail Reason access key.

Set it in the environment before launching Codex:

export WADV_LICENSE_KEY="YOUR_RETAIL_REASON_ACCESS_KEY"

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

[mcp_servers.retail_reason]
url = "https://mcp.retailreason.com/mcp"
bearer_token_env_var = "WADV_LICENSE_KEY"
tool_timeout_sec = 360

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 6, 2026. The 360-second timeout allows the service’s bounded retry and answer-review path to finish.

CHATGPT · ACCOUNT SIGN-IN

Connect Retail Reason to ChatGPT.

Follow these steps in your ChatGPT account. You need access to custom apps and an active Retail Reason trial or subscription. Your ChatGPT access and provider charges are separate.

These steps were tested on an individual Pro account. Available controls depend on OpenAI’s account and workspace policies. If you use a managed workspace, your administrator may need to enable custom apps.

If Retail Reason is already installed, use its Manage → Connection → Connect controls to reconnect, then complete the sign-in and first-question steps below.

Sign in to ChatGPT and have access to the email address used for your Retail Reason account.
Open Settings → Security and login and enable Developer mode. If that control is unavailable, check your account’s custom-app access or ask your workspace administrator.
Open ChatGPT’s Plugins page and choose the plus button, then Create app.
Use Retail Reason as the name and choose Server URL as the connection type. Enter https://mcp.retailreason.com/mcp in MCP Server URL and choose OAuth authentication. Leave automatically discovered settings in place, create the connection, and review the tools ChatGPT discovers.
On the Retail Reason sign-in page, enter your Retail Reason email address and the email verification code sent to you. Complete authorization and return to ChatGPT. If you are already signed in, ChatGPT may connect using that existing session. This hosted connection uses account sign-in.
Start a new conversation, add Retail Reason from the tools menu, and ask it to list your Retail Reason workspaces. Select the intended workspace, then try one current question without confidential details.

Confirm that the answer identifies your intended workspace and includes an answer ID, review status, as-of date and confidence class. An installed plugin or a Connected label alone does not confirm that Retail Reason has answered successfully.

If setup stops, check the troubleshooting guide. You can also ask Matt for help and include the error wording. Enter verification codes only in the sign-in window.

Setup tested on an individual Pro account September 14, 2026. Interface labels may change. OpenAI’s connection documentation describes the current client controls and availability.

AFTER CONNECTION

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

Know what the service can reach

Retail Reason never connects to retailer systems or retrieves their data. In this assistant connection, what travels to Retail Reason is the question, plan, draft, or context the assistant submits. Retail Reason chat separately supports selected file uploads. 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.

FOR WORKSPACE OWNERS AND IT REVIEWERS

What a Claude workspace owner needs before enabling the connector.

On a Claude Team or Enterprise workspace, a member without connector permission sees a request rather than a connection. This section is written to be forwarded to the person who approves it.

Add it for the organization

This link opens the organization connector dialog with the name and server URL prefilled; Claude asks for confirmation before anything is added. The server is https://mcp.retailreason.com/mcp, streamable HTTP, first-party: Retail Reason operates the service and the API behind it.

What it can and cannot reach

Every tool is read-only from the workspace’s point of view; nothing the connector does writes to a customer system. It never connects to Retail Link, Supplier One, Scintilla, Seller Center, or any retailer account. What travels is the question, plan, draft, or context a person chooses to submit, and the answer that comes back.

How people sign in

Each person signs in to their own Retail Reason account through OAuth; there is no shared credential and no access key on the hosted path. Access is bound to one account and to the workspaces that account may reach, and an owner or administrator on the Retail Reason side can revoke it at any time.

Where the details are

Data flow and provider settings are on the security page, the named providers on the subprocessors page, retention and rights in the Privacy Policy, and procurement facts on the vendor facts page.

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.

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.

matt@retailreason.com →