Connect an Amazon Store

After you connect an Amazon store, StoreClaw can read orders, inventory, products, reviews, and other data within the scope you authorize. This data is used for business analysis, business briefings, and automation tasks.

This article explains how to connect StoreClaw through official Amazon OAuth authorization. OAuth is the recommended connection method. It does not require you to manually create an app or copy credentials such as LWA Client ID, LWA Client Secret, or Refresh Token. If OAuth is not available for your account yet, you can also use manual credential connection as a fallback method.

StoreClaw only reads Amazon store data within the scope you authorize. The connection process will not modify, delete, or publish data in your Amazon store.

StoreClaw currently supports two ways to connect an Amazon store:

• Amazon OAuth authorization, recommended
• Manual credential connection

Recommended method: Connect through Amazon OAuth authorization

If your StoreClaw page already shows the Amazon authorization entry, we recommend using OAuth authorization first. This method does not require you to manually create an app, nor does it require you to copy LWA Client ID, LWA Client Secret, or Refresh Token. The overall process is shorter and less error-prone.

Before OAuth authorization

Before you start, make sure the following requirements are met:

• You are using an Amazon Professional Seller Account.
• You are currently logged in as the primary account, or the primary account has granted you permission to authorize applications.
• You know which Seller ID you want to connect.
• If you operate multiple Seller IDs, make sure the account you are currently logged in with corresponds to the Seller ID you want to connect to StoreClaw.

OAuth authorization process

1. Log in to StoreClaw and go to Connectors.
2. Find Amazon and click Connect Amazon.
3. In the pop-up window, select the region where you sell, such as North America, Europe, or Far East.
4. StoreClaw redirects you to the official Amazon Seller Central authorization page based on the region you selected.
5. Log in with the Amazon seller account you want to connect.
6. On the Amazon authorization page, select the seller account and marketplace you want to authorize.
7. Confirm the authorization scope, then click to agree to the authorization.
8. After authorization is completed, the page automatically returns to StoreClaw.
9. Back in StoreClaw, confirm that the Amazon connection status is displayed as Connected.

About Seller ID and marketplace selection

Amazon’s unified authorization page may require you to select one marketplace, but StoreClaw’s Amazon connection is managed by Seller ID.

This means:

• The same Seller ID only needs to be authorized once.
• As long as StoreClaw receives authorization for that Seller ID, StoreClaw can read all accessible marketplace data under that Seller ID within the authorized scope.
• If one Seller ID operates the US, Canada, Mexico, and other marketplaces, StoreClaw identifies and supports those marketplaces after authorization succeeds.
• If you have multiple Seller IDs, they usually need to be authorized separately according to Amazon’s authorization logic.

Therefore, when the Amazon authorization page only allows you to select one marketplace, select any marketplace under the seller account you want to connect and continue authorization. This selection is mainly used to complete the Amazon authorization process. It does not mean StoreClaw can only read data from that one marketplace.

Current support scope

Please note: Currently, one StoreClaw account can connect only one Amazon Seller ID.

If you operate multiple Seller IDs, prioritize the Seller ID that you currently need most for business analysis, briefings, and automation tasks. We expect to support multiple Seller IDs in the next version, so you will be able to create separate connections for different Seller IDs.

What you can do after authorization

After authorization succeeds, StoreClaw can read Amazon data within the scope you authorize and use it for:

• Store business analysis
• Daily or weekly business briefings
• Diagnostics across products, inventory, orders, reviews, and other dimensions
• Automated operations tasks and exception alerts

StoreClaw will not modify Listings, prices, inventory, ads, promotions, or any other content that may affect your store status without your confirmation.

Optional method: Manual credential connection

If OAuth authorization is not available for your account yet, or if the StoreClaw team asks you to use the manual method to troubleshoot a connection issue, you can manually obtain the required credentials through Amazon SP-API.

Manual connection usually includes the following 5 stages:

1. Prepare your account and information.
2. Complete developer profile registration or review.
3. Create an app.
4. Obtain Seller ID, LWA Client ID, LWA Client Secret, and Refresh Token.
5. Enter the credentials in StoreClaw.

Tip: The most time-consuming part of manual connection is usually Amazon’s review of your developer profile. We recommend starting the review first, and then becoming familiar with the following steps while you wait.

Before manual connection

Before you start, make sure the following requirements are met:

• You are using an Amazon Professional Seller Account.
• You are currently logged in as the primary account, or the primary account has granted you permission to develop applications.
• You have confirmed the Seller ID you want to connect.
• You have confirmed the site region you want to connect, such as North America (NA), Europe (EU), or Far East (FE).

Note: StoreClaw manages Amazon authorization by Seller ID. If the same Seller ID includes multiple marketplaces, StoreClaw can read all accessible marketplace data under that Seller ID within the authorized scope.

Information to prepare in advance

To avoid getting blocked midway, we recommend preparing the following information before you start:

• Company registered name.
• Company business license or business registration information, such as registration number, registered address, legal representative information, and so on.
• Identity document information of the legal representative or account administrator.
• Company website URL.
• Business email address and technical contact name.
• Amazon store name and site region you plan to connect, such as North America, Europe, or Far East.
• Business explanation of how StoreClaw uses Amazon data, such as for store business analysis, inventory analysis, order analysis, product performance analysis, business briefings, and automation tasks.

Manual connection process

Stage 1: Go to Develop Apps

1. Log in to Amazon Seller Central.
2. In the top or side navigation, find Apps and Services.
3. Go to Develop Apps.
4. If you do not have a developer profile yet, complete the developer profile form and review first.

If you cannot see Develop Apps, check whether the current account is the primary account, or whether it has permissions related to application development.

Stage 2: Complete developer profile registration or review

This is the most important part of the entire process and the part most likely to take time. You can create a production app only after your developer profile has passed review.

Fill in the developer profile

If this is the first time the account uses application development capabilities, the system may ask you to complete the developer profile or the onboarding flow in the new Solution Provider Portal.

Pay special attention to the following sections when filling in the information:

• Contact Information: We recommend using a real and stable business email address that can receive emails.
• Application type selection: If the page asks you to select an application type, refer to the “Select application type” section below. When a regular merchant connects their own store, they usually select Private application / Private developer.
• Data Access / Roles: These roles determine which data StoreClaw can read.
• Security Questionnaire: Amazon may ask about data encryption, access control, log retention, employee permissions, breach response, and related topics.

Select application type

In Amazon Solution Provider Portal or on the developer profile page, if you need to select an application type, select Private application / Private developer.

This method applies when a merchant creates an internal access app for their own Amazon store and uses the authorization information for StoreClaw to read authorized store data.

Do not select Public application, unless you are developing a public app for other Amazon sellers and plan to provide services to external sellers through the OAuth authorization process and Amazon’s related reviews.

In simple terms:

• If you only want to connect your own Amazon store to StoreClaw, select Private application / Private developer.
• If you are a software service provider developing a public app for multiple Amazon sellers, then you may need to consider Public application.

Select data access roles

Data access roles determine which Amazon store data StoreClaw can read. We recommend selecting roles based on the business scope you want StoreClaw to analyze.

For StoreClaw’s basic business analysis, inventory analysis, order briefings, and product analysis, we recommend prioritizing the following roles:

• Product Listing: Used to read product and Listing information.
• Pricing: Used to read product prices, sale prices, and price-related data.
• Inventory and Order Tracking: Used to read inventory and order status-related data.
• Amazon Fulfillment: Used to read FBA fulfillment, inventory, and delivery-related data.
• Buyer Communication: Select this role if you need to analyze buyer communication or message-related data.
• Tax Invoicing: Select this role according to site needs if you need to process invoice or tax-related analysis.
• Tax Remittance: Select this role according to site needs if you need to process tax remittance-related analysis.

Fill in the security questionnaire

The security questionnaire is usually a key part of the review and one of the areas most likely to cause materials to be returned. Common questions usually involve:

• Data encryption methods
• Access control mechanisms
• Log retention period
• Employee permission management
• Data breach response process

If you are not sure how to fill it in, we recommend getting a standard response template from the StoreClaw customer success team before submitting it.

Submit and wait for review

After submission, the system usually enters the review status. The review result is generally sent to the contact email address you entered in the profile.

Common review timeline:

• Developer profile review: About 3–5 business days

After the review is approved, you will usually see an entry to continue creating an app, such as Add new application, Add new app client, or a similar button.

Stage 3: Create an app

After the review is approved, return to the application development page and create your first app.

1. Go back to the Develop Apps or Solution Provider Portal page, and find the app list area.
2. Click Add new application, Add new app client, or a similar button to start creating an app.
3. Fill in the app information according to the page instructions.

When creating the app, you usually need to fill in:

• App Name: We recommend using StoreClaw - [your company abbreviation], so it is easy to identify later.
• API Type: Select Selling Partner API.
• App Type: Select Production.

Pay attention to the environment type when creating the app:

• Sandbox: Returns only test data and is used for development and debugging.
• Production: Returns real store data and is used by StoreClaw.

Important: If you are connecting StoreClaw, first make sure the subsequent authorization and data reading use the Production environment. If you create only a Sandbox app, the data you receive will be test data only.

Stage 4: Obtain the 4 credentials required by StoreClaw

After the app is created, open the app details page and extract all credentials one by one.

You need to obtain and save the following 4 pieces of information:

• Seller ID
• LWA Client ID
• LWA Client Secret
• Refresh Token

1. Obtain Seller ID

Seller ID is the unique identifier of an Amazon seller account. On some pages, it may also be displayed as Merchant Token or seller token.

You can find it on the app details page or on the related account information page in Seller Central.

A common path is as follows:

1. Click the settings icon in the upper-right corner and select Account Info.
2. In the left navigation, select Business Information.
3. Click Your Seller Token.
4. On the seller token page, find Seller ID.
5. Copy Seller ID to StoreClaw.

When copying, pay attention to the following:

• Do not include leading or trailing spaces.
• Keep it complete and do not truncate it.
• Make sure the Seller ID you enter in StoreClaw matches the store you want to connect.

2. Obtain LWA Client ID and LWA Client Secret

On the app details page, find the LWA credentials section:

• Client identifier is the LWA Client ID.
• Client secret is the LWA Client Secret.

Important: LWA Client Secret is equivalent to a password. Do not send it in group chats, public documents, or screenshots. We recommend copying it and entering it directly in StoreClaw.

3. Obtain Refresh Token

Refresh Token is the most important of the 4 credentials. It allows StoreClaw to read your store data later.

The usual approach is to click Authorize, Self Authorize, Create Token, or a similar button on the app details page.

After authorization is completed, the page returns a very long token string. This is the Refresh Token.

Important: Refresh Token is often displayed in full only at the moment it is generated. Copy and save it immediately. If you forget to copy it, you usually need to go through the authorization process again, and the old token may become invalid.

4. Checklist before leaving Amazon

Before leaving the Amazon backend, make sure you have copied all 4 items:

Credential	Description
Seller ID	Seller identifier
LWA Client ID	App identity identifier
LWA Client Secret	App secret
Refresh Token	Authorization token

Stage 5: Enter the credentials in StoreClaw

After you obtain the 4 credentials:

1. Return to StoreClaw.
2. Go to Connectors.
3. Find Amazon.
4. Select the manual credential connection method.
5. Enter Seller ID, LWA Client ID, LWA Client Secret, and Refresh Token.
6. Click connect.
7. Confirm that the connection status is displayed as Connected.

If the connection fails, check the following first:

• Whether Seller ID matches the authorized account.
• Whether LWA Client ID was copied completely.
• Whether LWA Client Secret was copied completely.
• Whether Refresh Token was copied completely.
• Whether the current app has completed review and has the required permissions.
• Whether the current Seller ID belongs to the Amazon store you want to connect.

Security notes

StoreClaw only reads data within the scope you authorize, and uses it for business analysis, briefings, and automation tasks.

StoreClaw will not perform the following actions without your confirmation:

• Modify or publish Listings.
• Adjust prices.
• Modify inventory.
• Create or modify promotions.
• Adjust ad budgets or bids.
• Delete, publish, purchase, incentivize, or manipulate reviews.

You can manage the connection status in Amazon Seller Central or StoreClaw. If you no longer use StoreClaw, you can disconnect the connection or revoke authorization.

Frequently asked questions (FAQ)

If this Seller ID includes multiple accessible marketplaces, StoreClaw can read data from those marketplaces within the authorized scope.

If you have multiple Seller IDs, prioritize the Seller ID that you currently need most for business analysis, briefings, and automation tasks. Separate authorization for multiple Seller IDs will be supported in a later version.