Autopilot fully automates the process of optimizing your Amazon listings, driving organic sales with minimal effort.

Our Getting Started section outlines the account setup onboarding process

Autopilot is your AI to make brand operations across Amazon & Shopify easier, better, and more profitable. Sellers can also assign access to the insights to third parties such as aggregators or agency partners.

Getting Started

• The details for sellers to connect their account are outlined inCreating a User Account

• Details around sharing access with third parties such as aggregators or agencies are detailed in Manager Accounts

If you still wish to disconnect an existing Amazon Seller Central, Amazon Advertising or Shopify account from Autopilot, then the following pages outline how to revoke access to each account type:

Disconnecting Amazon Advertising Accounts

Disconnecting Amazon Seller Central Accounts

Disconnecting Shopify Accounts

1. On the Organization dashboard page, click Add Seller

2. Under Create, enter the Seller name and click +

3. The new Seller name will now appear on the Sellers list and you can move on to the account onboarding, starting with

1. Autopilot will create a dedicated organization for you and invite you to create your organization's first user account

2. On the Organization dashboard page, click Add Seller and choose between the following options:

• Create a Seller: for sellers your organization owns and has full access to - simply enter the seller name and move on to connecting to the relevant sources such as Amazon Seller Central

• Invite a Seller: for sellers who want to share data with you - simply copy the link to clipboard and share it with them

Organization and User Settings can be accessed via the user icon that is always visibile in the top right-hand corner.

Various options are available on this page, details of which can be read below:

In order to connect ecommerce stores to Autopilot for generating brand performance insights, sellers need to create a Autopilot user account:

1. Navigate to the relevant sign-up page

• if you plan to share insights with another existing organization (such as an aggregator or brand house), they will share a specific invite link with you so that brand insights are automatically shared with them. The ecommerce partner company name will be included on the sign-up page (Acme Corporation in the example screenshot below)

• to sign-up directly to Autopilot, visit the Autopilot sign-up page

2. Enter the required details

• E-mail: this acts as the Autopilot account username for logging into the platform

• Company name: this should reflect the name of the specific ecommerce store you will be connecting and will be used as the seller name in reports and visualizations generated by Autopilot

• First Name / Last Name

• Password: create and confirm a strong password for your account

• Accept Terms & Conditions: please read and agree to the Terms of Service, Privacy Policy and Terms of Conditions in order to complete the account creation process

3. Enter the Settings page and onboarding guide

You will now automatically enter the Settings page and onboarding process.

The settings page guides you through the required onboarding steps.

Click on the relevant links below for more details on each:

• Confirmation of your Autopilot account (via the email received in your inbox)

• ​in their active regions (Amazon Regions: Europe & India, North America, Far East)

• ​ in their active regions (Amazon Regions: Europe & India, North America, Far East)

4. What if I forgot my login password?

No problem, simply navigate to the and click on Forgot your password?, after which you will be asked to define a new password.

Revoking Amazon Advertising API Access

• You can revoke Amazon Advertising API authorizations by visiting the section in their Amazon account titled Manage Login with Amazon or via this link:

• Note: to avoid mix-ups, we suggest opening the link in an incognito/privacy tab of your browser and signing in with relevant account credentials

• Seller Reporting by Xapix will appear under the listed Apps and Websites, with the Remove button enabling users to revoke the authentication

Uninstalling a custom app

If you are part of the beta program and wish to de-install the custom app, you can find the detailed steps on .

Revoking access / uninstalling the Xapix DTC & Amazon Performance app

• After installation, the DTC & Amazon Performance application will appear under Settings > Apps and sales channels in your Shopify admin account as shown in the screenshot above

• The app can be uninstalled by clicking on Remove and then Delete in the prompt that appears, or by clicking Delete on the application specific page directly

1. On the Organization dashboard page, click Add Seller

   • Under Invite, click on the clipboard icon to copy the link

2. Share the invite link from your dashboard page with the sellers you wish to invite, please note:

   • The same registration link can be shared with any number of different sellers

   • The invited seller should have relevant access levels (ideally admin access) to the accounts you want to receive insights for

1. Upon receiving the link, the Seller is asked to share brand insights with your company via Autopilot by creating an Autopilot user account

   • The account registration page confirms that your company (Acme Corporation in the example below) has invited the seller

   • In order to proceed, the seller is asked to create an Autopilot user account by confirming their email address, company name, password and accepting the terms & conditions

   • For more details on the seller account creation process for sellers, see here

1. The Seller is then guided through the required account authentication and COGS upload process

The Settings page guides sellers through the required steps. Click on the relevant links below for more details on each:

• Confirmation of their Autopilot account

• Connecting to Amazon Seller Central Accounts in their active regions (Amazon Regions: Europe & India, North America, Far East)

• Connecting to Amazon Advertising Accounts in their active regions (Amazon Regions: Europe & India, North America, Far East)

• Uploading Cost of Goods Sold (COGS) data

5. Successful seller connections are confirmed on the Seller Settings page

• On the Settings page > Data Services section, you can confirm which accounts the seller has successfully connected to Autopilot as shown in the screenshot below

• Furthermore, you can use the CoGS upload component to upload CoGS data in the same way that the seller can, as outlined here

1. Connect to an Amazon Advertising Account from Autopilot

• In the Autopilot Settings page > Data Services section, choose the Amazon Advertising service for the relevant region and click Connect to enter the account authentication process via your Amazon Advertising account

2. Complete the authentication process in the Amazon Advertising account

• Once you click on Connect, you will be redirected to the Amazon Advertising Account login page or directly to the account if you are already signed-in

• The consent page will ask you to grant Xapix (the legacy name for Autopilot) access to the data outlined in the page description by clicking on Allow

• You will now be redirected back to the Autopilot settings page

3.Confirm your successful account connection

• Upon successful authentication, the relevant Amazon Advertising Account will appear in the Data Services section of the Settings page as shown below

• Autopilot can now access Amazon Advertising API for the listed Advertising account in order to generate brand performance insights

For details on how to disconnect your Amazon Advertising account from Autopilot, please see the following

Keyword Impact Report

The Keyword Impact Report shows the measurable impact that Autopilot’s listing optimizations have on your products. Each optimization adds new, high-value keywords to your Amazon listings. Over time, we track how these keywords perform using Amazon’s SQPR (Search Query Performance Report) data and show the resulting lift in traffic, purchases, and revenue.

This report helps you see exactly how Autopilot’s optimizations translate into real business outcomes such as more clicks and increased revenue.

How to Read the Report

Each row in the report corresponds to a specific keyword that Autopilot added for a product. The fields are defined below:

General Product Information

• Seller – The seller account name.

• ASIN – The specific product identifier on Amazon.

• Parent ASIN – The parent ASIN that groups product variations (e.g., size, color).

• Marketplace – The Amazon marketplace (e.g., US, DE, UK).

• Brand – The brand associated with the product.

• Value Rating – 1,2,3 rating based on revenue tier, indicating the relative importance of that ASIN to the overall seller portfolio

Optimization Details

• Optimization Date – The exact date Autopilot implemented the keyword optimization.

• Keyword – The keyword added to the listing. New keywords not previously in the listing copy.

• Autopilot Rank – The relative priority of the keyword within Autopilot’s optimization model.

• Avg Purchase Price – The average price at which the product was purchased during the tracked period.

Performance Impact (Amazon SQPR Data)

• After Optimization SQPR ASIN Clicks (All Time) – Total number of customer clicks your ASIN received for this keyword since the optimization date.

• After Optimization SQPR ASIN Purchases (All Time) – Total number of purchases attributed to your ASIN for this keyword since optimization.

• After Optimization SQPR ASIN Clicks (L90D) – Customer clicks for this keyword in the last 90 days.

• After Optimization SQPR ASIN Purchases (L90D) – Purchases from this keyword in the last 90 days.

Revenue Attribution

• After Optimization Revenue Impact (All Time) – The total revenue impact (clicks × average purchase price) generated from this keyword since optimization.

• After Optimization Revenue Impact (L90D) – Revenue impact from this keyword in the last 90 days.

Why This Matters

The Keyword Impact Report ties together Autopilot’s optimization actions with Amazon’s performance data. It demonstrates:

• Which keywords are driving incremental traffic and purchases.

• Impact on clicks over time

• The real revenue impact of adding optimized keywords.

Because SQPR data is refreshed regularly, keyword performance may continue to evolve, and new data points are updated automatically.

1.Connect to an Amazon Seller Central account

• In the Data Services section of the Settings page, choose the Amazon Seller Central service for the relevant region and click Connect to enter the account authentication process via your Amazon Seller Central account

2.Confirm the scope of the data insights that you want to connect

• In order to receive the full scope of data insights from Amazon Seller Central now or in the future (for example for inventory related alerts, product listing recommendations, financial data), we highly recommend selecting the Full Operations Assistant Scope

• If you only wish to connect the more limited financial data from Seller Central (e.g. for a Profit & Loss statement and Brand Valuation use-cases), you can click on More options and select the Basic Financial Reporting Scope option

3.Complete the authorization process in Amazon Seller Central

• Once you click on Connect, you will be redirected to the Amazon Seller Central login page or directly to your account if you are already signed-in

• The overview of data to be accessed by Autopilot will be listed, reflecting the scope chosen in step 2

• The consent page will ask you to grant Autopilot access to the data by clicking on Confirm

4.Confirm your successful account connection

• Upon successful authentication, the relevant Amazon Seller Central account will appear in the Data Services section of the Settings page as shown below

• You can use the Selling Partner ID listed in the card to double-check that you connected the correct account

• The marketplaces (countries) that are part of the Amazon Seller Central connection are also listed as shown below

• Autopilot can now access Amazon Selling Partner API for the listed Amazon Seller Central account in order to generate brand performance insights

For details on how to revoke access, please see here

For details on how to upgrade the from the Basic Financial Reporting Scope to the Full Operations Assistant Scope for additional insights, please see here

Revoking Access

Seller Central Account: Amazon Selling Partner API

• You will see the Seller Reporting by Xapix and/or Operations Management by Xapix apps listed in Seller Central under Apps & Services > Manage Your Apps: https://sellercentral.amazon.com/apps/manage/

• You can revoke access at any time by clicking on the Disable action for the Seller Reporting by Xapix application

Our AI Operations Assistant provides daily email summaries with updates on the available profit opportunity and details on new alerts. If you would like to opt-out or in of these notifications, you can do so on the User & Organization Settings page, under Notifications.

1. To upgrade to a paid plan, you can click on the the FREE / UPGRADE icons that appear whenever you click on the User Icon in the top right hand corner of the application. Alternatively, you can navigate to the Settings Page and access the upgrade flow via the Subscription component

1. You will then be taken through the pricing options and simple process for accessing your free 14 day trial

For details on pricing, please see our

What is the SEO Score?

The SEO Score is Autopilot’s key indicator for how well your Amazon product listings are optimized for organic search visibility. It reflects both the quality of your listing content (Titles, Bullet Points, Descriptions, and Search Terms) and the relevance of keywords included, based on Autopilot’s continuously updated Keyword Bank.

By condensing complex keyword data into a single score, Autopilot makes it easy to see whether your listings are moving in the right direction for improved discovery and traffic.

How Autopilot Uses the SEO Score

• Optimization Drafts: Every optimization Autopilot generates for your listings is scored before and after the update. This ensures that new versions are only recommended when they improve your SEO performance.

• Reporting & Transparency: SEO Scores are presented in your customer reports to show the measurable impact of Autopilot’s optimizations across your catalog.

• Comparability: Because the score is normalized across attributes (Title, Bullets, Description, Search Terms), it can be compared across products, brands, categories, and time periods.

What Impacts the SEO Score?

Several factors influence your SEO Score:

1. Keyword Placement

   • Titles (highest impact): The most important keywords are prioritized here.

   • Bullet Points: Next most impactful for search visibility and readability.

   • Search Terms (backend): Capture additional eligible keywords not shown to shoppers.

   • Description: Lower direct SEO weight, but still contributes to discoverability.

2. Keyword Ranking

   • Each keyword in the Autopilot Keyword Bank is ranked by relevance using Amazon SQPR, ad performance, and other data sources.

   • High-ranking keywords drive larger improvements to the SEO Score when included.

3. Compliance & Constraints

   • Amazon’s style guides (e.g. max 200-character titles, 250-character bullet points, no word repetition >2x) determine how many keywords can realistically be included.

   • Autopilot balances keyword coverage with natural, compelling content.

4. Keyword Bank Updates

   • Autopilot updates the Keyword Bank monthly with new Amazon SQPR data, ad performance, and relevancy signals.

   • Because keyword rankings change, your SEO Score can move up or down even if the listing content itself hasn’t changed.

   • This ensures your optimizations always reflect Amazon’s latest search behavior and performance trends.

SEO Score Reporting

Autopilot delivers SEO Score insights to your team via reports. Each report highlights:

• Before vs. After Scores

  • For each ASIN, the report shows the SEO Score prior to optimization and the new score after Autopilot’s update.

  • Improvements are clearly highlighted so you can see the impact at a glance.

• Catalog-Level Impact

  • Aggregated metrics show total improvements across all listings for your brand.

  • This allows you to track progress not just at the product level, but across your entire portfolio.

Why the SEO Score Matters

• Measurable Improvement: You can clearly see how your listings are becoming more competitive in Amazon search.

• Trust & Transparency: Every optimization is supported by a before/after SEO Score and keyword movement data.

• Future-Proof: Regular keyword bank updates ensure your listings stay aligned with Amazon’s evolving search algorithms and shopper behavior

The upgrade option is available for sellers that started on the Basic Financial Reporting Scope and want to upgrade to the Full Operations Assistant Scope in order to receive all available insights from features such as the AI Operations Assistant - including product rating, inventory and product performance data not available in the basic scope.

The current scope of you Seller Central account is showing on the Seller Settings page, with the Basic icon shown along with the Upgrade button if you are on the Basic Financial Reporting Scope and the Ops icon showing if the account is already on the Full Operations Assistant Scope (see screenshots below).

How to Upgrade:

1. On the Seller Settings page, click on the Upgrade button for your Amazon Seller Central account connection

• The Basic icon indicates that this connection has not been upgraded so far

• The Upgrade button allows you to initiate the upgrade process

2. Confirm the new scope of data access in Amazon Seller Central

• Once you click on Upgrade, you will be redirected to the Amazon Seller Central login page or directly to your account if you are already signed-in

• The consent page will ask you to grant Autopilot access to the data outlined in the page description by clicking on Confirm

• As outlined on the page, this includes the previous data consented to (e.g. Product Listing) when you first authenticated to the Seller Reporting by Xapix application, plus the additional access required for providing new reports and insights (e.g. Amazon Fulfilment)

3. Confirm the successful connection on the Settings page

• The successful upgrade will result in the Ops icon being displayed instead of Basic

• The Upgrade button will no longer be visible

4. Revoking Access

You will now see the Operations Management by Xapix app listed in Seller Central under Apps & Services > Manage Your Apps: https://sellercentral.amazon.com/apps/manage/

• You can revoke access at any time by clicking on the Disable action for the Operations Management by Xapix application

1. You can invite other users to your organization via the + Invite User button, which is always visible in the top right hand corner of the application. Alternatively, you can use the Send Invitation button on the Organization Settings page.

1. Simply enter the email address of the user you would like to invite and click Send Invitation

1. The user will now receive an invitation email, which specifically mentions that you invited them, and be taken through the sign-up process

2. Once they accept the invitation, you will receive a confirmation email too

🔧 Technical Details

We’re using HTTPS to deliver a JSON payload to a provided URL using the POST method. The payload structure depends on the event type. We recommend choosing different URLs for different event types.

The supported event types are:

• Product listing patch published

• Product listing issue change (new / removed issues)

🔐 Authentication

For authentication we support adding a shared secret to the request header, for instance Authorization: Token <shared secret>. This allows you to easily validate any incoming request to the provided URL.

🛠️ Implementation Considerations

You can use your favorite tech stack to process the incoming notification and trigger the necessary actions to your internal systems.

We recommend that you process any complex operations in the background, i.e. after confirming that the webhook was correctly received by returning a 2xx HTTP result code (usually 200 or 201).

In case we receive a 4xx/5xx HTTP result code, the webhook will be retried up to 20 times with a progressive backoff.

We include a X-Request-Id header in every request which we recommend logging in case of issues with the received payload.

We’re using an at-least-once delivery paradigm so any actions on your side should be idempotent. Further, the ordering of delivery isn’t guaranteed. For instance in case of error responses from your endpoint the delivery will be retried at a later time. All our payloads include timestamps which will help you resolve those cases.

📝 Payload Schemas

In this section you can find the JSON schemas for the different event types.

Product listing patch published

//
id: https://product_historian.apps.autopilotbrand.com/models/notifications/patch_notification
title: Autopilot Patch Notification
description: Contents of notifications we're sending after a patch was sent to Amazon

"$ref": "#/components/schemas/ListingChangeNotification"

components:
  schemas:
    ListingChangeNotification:
      type: object
      properties:
        seller_id:
          type: string
          description: Selling partner identifier, such as a merchant account or vendor code
        sku:
          type: string
          description: Selling partner provided identifier
        marketplace_id:
          type: string
          description: Amazon marketplace identifier
        created_at:
          type: string
          format: date-time
          description: Timestamp when change was created
        confirmed_at:
          type: string
          format: date-time
          description: Timestamp when change was confirmed submitted
        patch:
          "$ref": "#/components/schemas/ListingPatch"
      required:
      - seller_id
      - sku
      - marketplace_id
      - created_at
      - confirmed_at
      - patch

    ListingPatch:
      type: object
      properties:
        patches:
          description: "One or more JSON Patch operations to perform on the listings item."
          type: array
          items:
            "$ref": "#/components/schemas/PatchOperation"
          minItems: 1
      required:
      - patches

    PatchOperation:
      description: "Individual JSON Patch operation for an HTTP PATCH request."
      type: object
      properties:
        op:
          description: "Type of JSON Patch operation. Supported JSON Patch operations include add, replace, and delete. Refer to [JavaScript Object Notation (JSON) Patch](https://tools.ietf.org/html/rfc6902) for more information."
          enum:
          - add
          - replace
          - delete
          type: string
        path:
          description: JSON Pointer path of the element to patch. Note that for Amazon listings, JSON Patch documents can only add, replace, or delete entire attributes. Patching content within attributes is not supported.
          type: string
        value:
          description: JSON value to add, replace, or delete.
          type: array
          items:
            type: object
            additionalProperties: true
      required:
      - op
      - path

Product listing issue change

// 
id: https://product_historian.apps.autopilotbrand.com/models/notifications/issues
title: Autopilot Issues Notification
description: Contents of notifications we're sending when change to issues is detected

components:
  schemas:
    issue:
      type: object
      properties:
        code:
          type: string
          description: An issue code that identifies the type of issue.
        message:
          type: string
          description: A message that describes the issue.
        severity:
          description: The severity of the issue.
          type: string
          enum:
          - "ERROR"
          - "WARNING"
          - "INFO"
        attribute_name:
          type: string
          description: The names of the attribute associated with the issue, if applicable.
        enforcement:
          type: object
          description: Enforcement actions taken by Amazon that affect the publishing or status of a listing. It also includes details about any associated exemptions.
          properties:
            action:
              description: |
                The enforcement action name.
                Possible values:
                - `LISTING_SUPPRESSED` - This enforcement takes down the current listing item's buyability.
                - `ATTRIBUTE_SUPPRESSED` - An attribute's value on the listing item is invalid, which causes it to be rejected by Amazon.
                - `CATALOG_ITEM_REMOVED` - This catalog item is inactive on Amazon, and all offers against it in the applicable marketplace are non-buyable.
                - `SEARCH_SUPPRESSED` - This value indicates that the catalog item is hidden from search results.
              type: string
              enum:
              - LISTING_SUPPRESSED
              - ATTRIBUTE_SUPPRESSED
              - CATALOG_ITEM_REMOVED
              - SEARCH_SUPPRESSED
            exemption:
              description: The status of the listed enforcement actions and, if applicable, provides information about the exemption's expiry date.
              type: object
              properties:
                status:
                  description: Current exemption status. It can take values such as `EXEMPT`, signifying permanent exemption, `EXEMPT_UNTIL_EXPIRY_DATE` indicating temporary exemption until a specified date, or `NOT_EXEMPT` signifying no exemptions, and enforcement actions were already applied."
                  type: string
                  enum:
                  - EXEMPT
                  - EXEMPT_UNTIL_EXPIRY_DATE
                  - NOT_EXEMPT
                expiry_date:
                  description: Specifies the time when temporary exemptions will expire, and Amazon will begin enforcing the action.
                  type: string
                  format: date-time
              required:
              - status
          required:
          - action
          - exemption
      required:
      - code
      - message
      - severity
    issue_list:
      type: array
      items:
        "$ref": "#/components/schemas/issue"

type: object
properties:
  seller_id:
    type: string
  sku:
    type: string
  asin:
    type: string
  marketplace_id:
    type: string
  detected_at:
    type: string
    format: date-time
  new_issues:
    "$ref": "#/components/schemas/issue_list"
  resolved_issues:
    "$ref": "#/components/schemas/issue_list"
required:
- seller_id
- sku
- asin
- marketplace_id
- detected_at
- new_issues
- resolved_issues