Amazon Seller Central

eCommerce Insights is read-only against Amazon Seller Central as of v19. Recommendations from Rufus Score translate to specific edits the merchant applies inside Seller Central. This page explains the suggested workflow and what is on the roadmap for a direct write integration.

Current state

eCommerce Insights reads from Amazon Seller Central but does not write back. The reads cover catalogue data, A+ content blocks, brand-store hierarchy, and (in early access) SP-API sales data. The writes are manual: each recommendation has a "Copy for Seller Central" button that gives you the proposed change in the format the relevant Seller Central field expects.

The suggested workflow

1. Open the Rufus Score detail

   For an Amazon SKU, the Score detail opens to the fifteen-relation breakdown with ranked recommendations.

2. Triage by relation

   Each recommendation is tied to one of the fifteen COSMO relations. Start with the lowest-scoring relations.

3. Copy proposed content

   Per recommendation, click "Copy for Seller Central." eCommerce Insights copies the text formatted for the specific field type.

4. Paste into Seller Central

   Navigate to the corresponding field (A+ block, bullet, brand store module, Q&A draft).

5. Mark applied

   Back in eCommerce Insights, click "Mark applied." The recommendation moves out of the open queue; the Rufus Score re-checks the relation on the next scheduled audit.

A+ content updates

A+ content recommendations come as block-level proposals. Each block has a template type (image+text, comparison chart, brand story), proposed image guidance, proposed copy, and a notes section. The "Copy for Seller Central" copies the copy directly; the image guidance is a brief you can hand to a designer or paste into your image-generation tool.

Bullet updates

Five bullets, each within Amazon's character limit. The structured pattern (spec → benefit → use case) is applied where the underlying data supports it. The "Copy for Seller Central" copies all five bullets in the correct order.

Brand store updates

Brand store recommendations cover module copy, not module structure. If the recommendation says "your brand story module's opening sentence is undifferentiated," you get a proposed replacement opening sentence. Module rearrangement is a manual judgement call.

Q&A submissions

Q&A is the most overlooked Rufus signal. Coverage in Q&A directly improves the COSMO relations 4 (Q&A coverage) and 8 (use-case relation). Recommendations come as paired Q and A drafts that you can submit as the brand-verified answer to existing questions or as new questions if no question exists in the relevant category.

Roadmap

• Direct SP-API write integration — in certification.
• Sales data overlay on Rufus Score — early access on Pro.
• Brand Analytics ingest — planned.
• Walmart Sparky-specific scoring — in development (Sparky is currently scored as a retailer rather than a marketplace).

Common questions