Features and Amazon integration

What Rufusly does

Rufusly helps Amazon selling partners write compliant, well-structured listings and understand how those listings perform. It is a subscription web application at rufusly.ai. Sellers sign in, add a brand profile, and use the tools described below on their own catalogue.

The platform has two halves. The first writes and checks content: listing copy, product imagery, and the brand rules that govern both. The second reads a seller's own Amazon data so that the content decisions are informed by real performance rather than guesswork.

Listing management

Listing Studio is the core of the product and is available today. You paste or upload your existing listing content and it rewrites it to be compliant and easier for shoppers and Amazon's own search tools to understand. Once the Amazon connection is approved, it will read that content directly from your catalogue instead.

What it does

• Rewrites listing content. Title, bullet points, product description, and backend search terms, one listing at a time or in bulk. A+ content copy is generated alongside a rewrite, with a dedicated A+ Content Builder on the Growth and Agency plans.
• Enforces Amazon's limits. Every generated field is checked against Amazon's rules before it is shown, including the 75 character title limit, banned characters, byte limits on backend search terms, and duplicate terms across fields.
• Listing Quality Score. Scores a listing out of 100 and lists exactly which fields fail and why, so a seller can see what to fix before publishing anything.
• Bulk rewriting from a flat file. A seller uploads their Amazon Category Listings Report and Rufusly rewrites the non-compliant rows, then exports a file that can be uploaded back to Amazon. Every other column is returned byte for byte as it came in. Free accounts are limited to 10 rows.
• Brand profile. Sellers record their brand name, product category, key claims, target customer, and certifications once. Every rewrite for that brand is written against those details, so generated copy stays consistent with the brand.
• Brand Safety Vault. Sellers keep a confidential list of forbidden claims, restricted words, and required disclaimers. Rufusly checks every generated field against that list after generation and flags anything that breaches it. The list is held server side and is never sent to the AI model.
• Version history. Previous versions of a listing are kept with their scores, so a seller can compare a rewrite against what came before.

Amazon data used

Listing content and attributes for ASINs in the seller's own catalogue, plus the product type schema Amazon publishes for each category, which we use to detect missing required attributes.

Inventory and orders

The inventory view shows a seller which of their products need attention, and connects those problems to the tools that fix them.

What it does

• Stock levels and cover. Current quantity, estimated days of cover, and low stock warnings per SKU.
• Suppressed listing detection. Reads the issues Amazon reports against a listing and identifies which ones are search suppressions. Where the cause is a main image that does not meet Amazon's guidelines, for example a lifestyle photo used where a plain white background is required, Rufusly flags it and offers to generate a compliant replacement image.
• Guided fixes. Suppression reasons that need seller action in Seller Central, such as category approval, are shown as read only with an explanation, rather than being presented as something the tool can fix.

Amazon data used

FBA and seller-fulfilled inventory quantities, listing status and the issues Amazon reports against each listing, and order volume used to estimate days of cover. We do not read buyer names, addresses, or contact details.

Brand Analytics

Brand Analytics data tells a seller which search terms actually convert for their own brand. Rufusly uses it so that listing copy is written around proven terms rather than guesses.

What it does

• Search query performance. Top search terms for the seller's brand with impression share, click share, and conversion share, reported by ASIN.
• Keyword intelligence. Search query performance for a chosen ASIN, ranked by purchase share, click share, and cart add rate, so the seller can see which keywords earn sales rather than only clicks. These terms are then offered to Listing Studio when the title and backend terms are written.
• Customer voice. Review and return themes for the seller's own ASINs, summarised into what customers consistently praise, what they complain about, and the most common return reasons. This is used to inform bullet points and to flag claims that reviews contradict.

Amazon data used

Aggregated Brand Analytics reports for the seller's own brand and ASINs only, retrieved on the seller's behalf and shown only to that seller.

Selling Partner Insights

Sellers need to see whether a listing change made a difference. The insights view reports performance over time so the effect of a rewrite is visible.

What it does

• Sales performance. Revenue, units sold, and order counts by ASIN over a chosen date range.
• Before and after context. Because listing versions are stored with the date they were published, a seller can line up a content change against the sales that followed it.

Amazon data used

Sales and traffic figures for the seller's own account and ASINs.

Finance and accounting

Content decisions have a margin consequence, and money Amazon owes back is easy to miss. Both are surfaced here.

What it does

• Fee and settlement summary. Referral and fulfilment fees, settlements, and resulting net margin per ASIN, so a seller can see which products are actually profitable before investing in new content or imagery for them.
• FBA reimbursement finder. Reviews financial events over a chosen window to surface inventory that was lost, damaged, or incorrectly charged, and reports pending and approved reimbursement totals with an itemised list. Rufusly reports what it finds. The seller decides whether to raise a case.

Amazon data used

Financial event and settlement data for the seller's own account. We do not access payment instruments or bank details.

Review requests

Reviews carry weight with shoppers deciding whether to buy. Rufusly lets a seller ask for them using Amazon's own mechanism.

What it does

• Amazon templated review requests. Submits Amazon's standard review request for orders that are eligible under Amazon's own rules. Eligibility is determined by Amazon: we submit the request and Amazon accepts or rejects it against its own permitted window.
• No custom messaging. Rufusly uses Amazon's Solicitations API and Amazon's own template. We do not write, alter, or add to the message, and we do not offer incentives or attempt to influence review content.
• You confirm before anything sends. Rufusly shows the eligible orders and sends only once you confirm.

Amazon data used

Order identifiers and eligibility status only, for the purpose of issuing the request. Rufusly does not receive or store buyer names, email addresses, postal addresses, or any other buyer personal data, and no buyer data is sent to any AI model.

Product imagery

Image Studio generates Amazon-ready product images from a seller's own photography. It does not require an Amazon role of its own, but it is used alongside the inventory tools to resolve image-based suppressions.

• Generates main images on a pure white background, lifestyle scenes, and infographic-style images with editable text labels.
• Removes or replaces backgrounds on an existing product photo.
• Where a listing is suppressed for a main image that breaks Amazon's guidelines, the replacement is previewed and only published to Amazon once the seller approves it.

AI search visibility

Some shoppers now ask an AI assistant instead of browsing search results. This part of the platform tracks how a brand is described when they do.

• Runs a set of buying questions against public AI assistants and records whether the brand is mentioned, how it is described, and which sources are cited.
• Reports share of voice against named competitors over time, and the sources those answers draw on.
• Assistant Radar simulates how an Amazon shopping assistant is likely to summarise a listing, based on the listing's own content. These are clearly labelled in the product as simulated responses, not live output from Amazon Rufus.

This feature uses public AI assistants and the seller's own listing content. It does not use Amazon Brand Analytics data. AI search visibility and Assistant Radar are available on every plan, including the free tier. Each check uses one AI Visibility credit, and the number of credits included is what differs between plans.

Agent access (MCP)

The tools described above are also available to AI assistants through a Model Context Protocol server at mcp.rufusly.ai, so a seller can work in an AI chat client instead of the web interface. Content tools such as listing rewriting work today. Tools that read Amazon account data become available once the Amazon connection is approved. Access is authenticated with either a scoped API key or OAuth 2.1, and an agent can only ever reach the data of the account that authorised it. The same approval step applies: an agent can draft content and can list the orders eligible for a review request, but anything that writes to Amazon or reaches a buyer requires the seller to confirm it first. MCP access is included on every plan.

Connecting your Amazon account

Rufusly reads Amazon data only after a seller explicitly connects their Selling Partner account, and only for the account that authorised it.

• Amazon's own consent flow. Connection uses Amazon's standard authorisation flow from within Seller Central or from the Rufusly app. The seller sees exactly which roles are being requested and must approve them.
• Least privilege. We request only the six roles listed at the top of this page, each of which maps to a feature described here.
• Read first, write only on approval. Reading data happens in the background so the tools have something to work with. Writing anything back to Amazon, whether listing content or a main image, always requires the seller to review the exact change and approve it.
• Revoke at any time. A seller can disconnect from within Rufusly, or revoke authorisation in Seller Central under Apps and Services. Access stops as soon as the authorisation is revoked.
• More than one account. Agencies can connect several selling accounts and keep each brand's data and rules separate.

How we handle data

Full detail is in our Privacy Policy. In summary:

• No buyer personal data goes to AI models. The content we generate is written from product information, not from buyer data. Buyer names, email addresses, and other contact details are never included in any prompt.
• Processing is server side. All AI processing happens on our servers, never in your browser. Amazon credentials and tokens are held server side and are never exposed to the browser.
• Not used for training. We do not use your content to train AI models without your explicit consent. The AI providers we use are listed in our Privacy Policy, along with exactly what each one receives.
• Not shared or sold. One seller's Amazon data is never shown to another seller, never pooled into benchmarks, and never sold or licensed.
• Encrypted at rest and in transit using TLS 1.2 or above, with access restricted to the account that owns the data.
• International transfers. Some processors are based in or transfer data to the United States. Where that involves a transfer of personal data outside the UK, we rely on Standard Contractual Clauses, the UK International Data Transfer Addendum, or an equivalent recognised safeguard.

Plans and pricing

Rufusly is sold as a monthly or annual subscription. Current plans and the full feature comparison are listed on our pricing section.

Agent access through our MCP server is included on every plan, including the free tier. Monthly and annual billing are both available, and annual rates are shown in the pricing section.

Prices are in pounds sterling and exclude VAT. UK customers pay VAT at the standard rate on top. You can cancel at any time from your account settings, which stops the next renewal. Because subscriptions are billed in advance, cancelling does not refund the current period, except where you have a statutory right to a refund. Your rights under the Consumer Contracts Regulations are set out in our Terms of Service.

Contact us

Questions about the platform, our Amazon integration, or this page:

• Email: hello@rufusly.ai
• Support for existing customers is available from within the app.

Rufusly is a trading name of LUMINOUS EMPORIUM LTD, registered in England and Wales, company number 16201976. Registered office: 124-128 City Road, London, EC1V 2NX, United Kingdom.