▪ Completed Audit · June 2026

Equinavia Backend Optimization Report

📅 Generated June 22, 2026 🛒 1,611 SKUs audited 📋 500 parent families · 9,888 child variants 🆘 Marketplace: Amazon US

Total SKUs Audited

10,388

500 parents + 9,888 variants

Group A — Flat File Ready

2,131

Attribute fixes deployable today

Group B — Case Required

5,854

Fields need case or PIM data

Titles Brought to Compliance

491

99% of parent families updated

Est. Band Score Lift

+94

Points across catalog (heuristic)

Pre-Audit Avg. Listing Score

Out of 1,000 — critical baseline

✅

Group A — Flat File Upload

Fixes deployable directly via Seller Central flat file. No case or Amazon support required.

2,131

Total attribute fills ready

Titles brought to compliance 491

Brand name fixes 491

QA content updates 466

Variation theme corrections 460

Material type fills 173

Generic keyword updates 44

Product description drafts 6

Coverage — 495 of 500 parent families (99%)

⚠️

Group B — Case Required

Fields blocked due to missing PIM data or attributes that require Amazon Seller Support case.

5,854

Total blocked attribute fields

Compatibility (missing PIM) 508

Occasion (missing PIM) 508

Item type keyword 495

Target audience keyword 495

Intended use (missing PIM) 495

Bullet points (blocked) 495

Product description (blocked) 489

Generic keywords (no source) 464

Color / dimensions per-child 495

All 496 families have at least 1 blocked field

Catalog Quality Baseline (Pre-Audit)

500 parent ASINs analyzed

Avg Listing Score

Out of 1,000 (critical)

Missing Description

99%

493 of 500 parents

Missing Keywords

91%

456 of 500 parents

Score 0–200

353

71% of catalog critically low

Score 201–400

120

24% — below median

Score 401–600

5% — near-passing

Group A Fixes by Priority Tier

2,131 total actionable

Tier	Description	Key Attributes	Fixes Ready	% of Group A
Tier 1	Highest Rufus & search ranking signal	material_type variation_theme	633	30%
Tier 2	Listing completeness & conversion	title qa_content	1,007	47%
Tier 3	Supporting brand & taxonomy fields	brand generic_keywords	491	23%

Attribute-Level Detail

All 496 parent families

Attribute	Status	Group A Flat File	Group B Case / PIM	Coverage
title	Ready	491	4	99%
brand	Ready	491	4	99%
qa_content	Ready	466	42	94%
variation_theme	Ready	460	35	93%
material_type	Partial	173	322	35% ready
generic_keywords	Partial	44	464	9% ready
product_description	Partial	6	489	1% ready
bullet_points	Blocked	—	495	0%
item_type_keyword	Blocked	—	495	0%
target_audience_keyword	Blocked	—	495	0%
intended_use	Blocked	—	495	0%
compatibility	Blocked	—	508	0%
occasion	Blocked	—	508	0%
color_name / dimensions	Blocked	—	495	Per-child PIM needed
customer_reviews_aggregate	N/A	—	508	Not operator-settable

🛠️ Recommended Next Steps

1

Deploy Group A flat file immediately. 2,131 attribute fills are ready — titles, brand, QA content, variation themes, material types. No case required. Upload via Seller Central > Inventory > Add Products via Upload. Est. 1–2 business days to process.
2

Open Group B cases for top-priority blocked fields. Start with item_type_keyword (495 ASINs), target_audience_keyword (495), intended_use (495), and bullet_points (495). These are the highest Rufus ranking signals. Batch by product type to keep case counts manageable.
3

Supply PIM data for compatibility + occasion fields. 508 ASINs are blocked on compatibility and occasion — these require Equinavia to provide values in Salsify PIM. Once PIM is updated and re-exported, the pipeline can auto-resolve these in Stage A.
4

Unlock SP-API for Helium 10 / keyword sourcing. 464 ASINs need generic_keywords but are blocked because no keyword source data is available. Carl LWA SP-API access (Gate G2) unlocks automated keyword inference for the remaining catalog.
5

Approve and deploy content drafts (bullets + descriptions). Bullet points and product descriptions are drafted for high-priority families but gated on operator approval. Review drafts in content_drafts.json per family, approve, and add to operator_overrides.yaml to unlock paste-back.

Methodology note: Audit conducted by the Rankona Terminal CLR-001 pipeline using Salsify PIM export (2026-06-12), Amazon CLR .xlsm templates, and Stage A/B/C deterministic + LLM inference. Scores based on Cosmo field-completeness weighting (Amazon internal ranking signal). Band score lift estimates are heuristic (+0.07/Tier-1 fill, +0.04/Tier-2, +0.02/Tier-3) — real lift varies with Rufus and A10 algorithm weights. Customer_reviews_aggregate excluded from operator-actionable counts as it is set by Amazon, not sellers.