Listing

Beta

Listing is in beta. It requires an Amazon Selling Partner API (SP-API) connection for the selected seller profile. The workflow and its Amazon write availability may change while it is being completed.

Listing is the Storefront workspace for improving the copy on your Amazon products. It keeps the content currently on Amazon beside a proposed version, so you can see what changed before anything is sent.

The Agent prepares a draft. The Reviewer scores it. You decide what to edit and whether to send it to Amazon. A draft, a passing score, or a completed Agent run does not publish anything by itself.

Before you start

• You need access to the Storefront area and an active seller profile selected in the App.
• You need an Amazon Selling Partner API (SP-API) connection for the selected seller profile. SP-API supplies the current Amazon title, Item Highlight, bullets, description, Search Terms and marketplace images. Until the first usable sync is available, Listing may have no current content to review; any stored fallback copy can be older than Amazon and is not a substitute for the required connection.
• To send a change to Amazon, the listing must belong to a live SP-API connection and you need Ads Manager edit access for that same seller profile. The App checks this again when you send.
• A healthy SP-API sync gives the App the freshest starting point. See Amazon connections and Missing or delayed data when the current content is missing or stale.

Find work on the Listing board

Open Listing from the Storefront group. The board shows the products and seller SKUs that need attention, with the most actionable rows surfaced first.

Use the table to search by product, ASIN or seller SKU. The default view hides listings that are not currently buyable; clear the Selling status filter to inspect them. Useful columns include:

• Status — Agent writing, Reviewer scoring, Draft ready, Published, or no open work.
• Needs fixing — only the content gaps found for that listing, such as a missing title, Search Terms over the byte limit, or an unassigned Product Group.
• Agent assessment — the latest score, verdict and weakest axis when the draft needs work.

Select a row to open its detail view. If a product has variants, each seller SKU remains a separate listing. The SP-API board opens each listing separately; an older fallback board may also expose a product-level action that queues one run per existing variant.

Read a listing detail

The detail view has three tabs.

Content

The Current column is the copy the App is using as the live baseline. The Proposed column is the newest Agent or manually edited draft. The copy is split into the same fields Amazon uses:

• Title
• Item Highlight
• Bullet Points
• Description
• Search Terms — backend terms, shown separately from the visible copy

The Agent can rewrite Title, Item Highlight, Bullet Points and Description. Search Terms are produced as a separate suggestion after the visible copy is written; there may be no suggestion when no safe terms are available. The App shows counters for the Amazon limits and marks the parts the Reviewer identified as changed when an audit is available.

Keywords

Keywords provide context for a rewrite. When a Product Group exists, this tab combines Amazon keyword evidence for the group with the imported keyword bank for its base SKU. The Agent prefers Product Group and ASIN performance evidence, then falls back to the imported bank when those sources are unavailable. The metric groups stay separate because SQP, Ads and imported CSV data use different measurement methods.

An administrator can download or import the keyword bank as a CSV. The expected columns are keyword, orders, clicks, and impressions. An imported bank is used by future Agent runs when higher-priority Product Group or ASIN performance sources are unavailable; it does not publish listing copy.

History

History keeps previous drafts, Reviewer audits, failed attempts and comparisons between versions. It also records whether a draft was sent to Amazon and whether the later SP-API sync confirmed the published content. Use it when you need to understand what changed or return to an earlier version for reference.

Ask the Agent to rewrite

From the board, choose Improve for one listing. On the older fallback board, a product row may also offer Improve all variants, which queues one run for each existing variant. Each variant is processed separately, so a problem with one SKU does not silently change its siblings.

You can add an optional instruction, for example which product benefit to emphasize or which phrase to remove. Keep the instruction about the listing; the Agent still has to stay within the product facts and Amazon field limits it receives.

The Agent uses the current listing plus available keyword evidence. Product Group performance is the preferred source, followed by ASIN performance, the imported keyword bank, and current Amazon Search Terms when those higher-confidence sources are unavailable. It does not need you to paste the listing into the dialog.

Runs start in the background. You can leave the page; the board and detail view show writing, scoring, completion or failure as the run progresses. If a run fails, it remains in History and Retry queues a fresh attempt with the same request. A failed run does not create a usable proposal.

Review the proposal

When writing finishes, read Current and Proposed side by side. The automatic Reviewer scores these six axes:

1. SEO
2. Readability and humanization
3. Compliance
4. Brand voice
5. AI clarity
6. Conversion

The current quality indicator passes only when every axis is at least 3/5 and the six-axis average is at least 4/5. This is an Agent assessment, not your approval and not a performance guarantee. Read the field notes and callout, especially for Compliance, before sending anything.

You can ask for a rewrite of all four writable fields or target one field with its own instruction. The latest draft remains visible even when the Reviewer needs work, so you can edit it, request a more focused rewrite, or leave it unchanged.

Edit a draft yourself

Use the pencil control on a field to edit the proposal in the App. Save each field when it is ready; the App keeps the edit as a new draft version and labels manually edited fields in the detail view. Search Terms can be edited too. The field counter uses UTF-8 bytes for Search Terms, because that is how Amazon measures the limit.

Manual editing changes the proposal only. It does not change Amazon until you complete the send flow below.

Send a change to Amazon

1. Open the latest draft on the Content tab and read the proposed values.
2. Choose Publish to Amazon. The App builds a partial update containing only fields that differ from the current Amazon content.
3. The App asks Amazon to validate that exact payload first. If validation fails, no live change is sent. Fix the draft or refresh the listing snapshot and try again.
4. In deployments that show the payload preview, inspect the exact seller SKU, marketplace and fields to change, then confirm Send LIVE. In Production, the same checks happen server-side and the explicit Publish to Amazon click submits after validation without a separate preview step.

There is no background publish, Agent publish, or “approve means publish” step. Sending is an explicit user action and is checked against the selected seller’s permissions. The write path is also protected when the live Listing runtime is unavailable, the connection is not live, the draft is stale, or Amazon’s current content changed after the snapshot. These stops prevent an old draft from overwriting newer content.

After Amazon accepts the request, the detail view shows Sent to Amazon. It changes to Published on Amazon only after a later SP-API sync confirms that the live content matches the submitted draft.

Amazon limits and safe expectations

For the current Amazon channel, the App and Agent enforce these representation limits:

Field	Limit
Title	75 characters
Item Highlight	125 characters
Bullet Points	5–6 bullets, depending on supported information
Description	2,000 characters
Search Terms	Up to 3 lines, 250 UTF-8 bytes per line

The Agent may leave a field unchanged or return no Search Terms when it cannot make a safe proposal. Shorter supported copy is better than invented product facts. Treat every proposal as a draft to verify against your product, Amazon category rules and your brand voice.

What this workflow does not cover

• It does not edit or publish A+ Content; that surface is not available in this workflow yet.
• It does not automatically change images. Image audits, when present, are recorded in History for reference.
• It does not replace Amazon’s own validation or category requirements. Amazon can still reject a submitted field after the App’s preflight checks.

When a connection or sync looks wrong, start with Amazon connections. For a broader explanation of how data becomes a proposed action, see How Vendlen works.