🖊️ Max Sigurdson-Scott at ASIN Audit OS
👉 The 8 secondary image font rules you should not break

Let's have the biggest impact we possibly can on our Amazon buyers (who are all buying on their phones). The rules:

1. Limit text overlays to 5 words or less

2. Key callouts should be at least 40pt

3. Secondary callouts (if necessary) should be at least 30pt

4. Unless your brand has a specific "luxury style," avoid serif fonts. Arial, Helvetica or Open Sans are great choices

5. Never place text over busy backgrounds

6. No more then 2 lines of text

7. Maintain high contrast colors that don't blend in with other elements

8. Only place the text in the top third of the image (if possible)

🖊️ George Reid, Founder at GBMedia
👉 How to lower your cost per design without impacting quality

For the past two years, the focus has been on maximizing design efficiency to scale high-converting designs across hundreds or thousands of SKUs. The key to achieving this is implementing a Design System, rather than relying solely on traditional designers.

Instead of just hiring designers, the strategy involves recruiting Figma developers to build proprietary systems that enhance speed and reduce costs. By leveraging components, variables, and custom plugins, assets remain consistent while allowing bulk updates in seconds—critical for adapting to changes like Rufus updates.

A major design principle applied here is Design Tokens, widely used in web development. This approach allows for centralized design decisions that can be updated across all designs instantly when needed.

Looking ahead to AI in Amazon design (2025), the focus isn’t on trendy AI tools but on Figma’s AI integration, which enhances efficiency much like a chainsaw improves on a manual saw—most effective in expert hands. To stay competitive, design teams must adopt Figma and AI-driven design systems.

🖊️ Vincenzo Toscano, Founder & CEO @ Ecomcy
👉 The “Stealth Ranking” strategy to dominate keywords at a low cost

Instead of aggressively bidding on your main keywords from the start, use long-tail variations and lower-competition search terms to build momentum first. Amazon’s algorithm rewards consistent conversions, so by focusing on cheaper, less competitive keywords at first, you can generate sales without overpaying. Once your listing gains relevance and sales velocity, Amazon will organically rank you on your main keywords without the need to bid aggressively.

After a few weeks of steady conversions with long-tail keywords, gradually introduce high-volume keywords with lower bids, allowing your organic ranking to improve while keeping CPCs low. This strategy helps you gain visibility in competitive niches without wasting budget on expensive clicks, making it a powerful and cost-effective way to dominate your market.

🖊️ Connor Mulholland Co-Founder at Jarvio
👉 Keyword Harvesting

Success on Amazon isn’t about one big move. It’s about nailing the small tasks every single day.

Here’s what top-performing brands never miss:

• Stay in stock: it can take weeks to recover BSR.

• Resolve issues fast: unanswered policy violations or stranded inventory can kill momentum.

• Remove negative feedback: every point on your seller rating impacts the Buy Box.

If you’re not tracking these daily, you’re leaving growth on the table. Check out how Jarvio looks across your account to identify the tasks you need to complete, puts that in your today's to-do.

🖊️ Max Sinclair, Founder at Ecomtent
👉 How much are Amazon Shoppers actually using Rufus?

274.3 million daily questions, or ~13.7% of total Amazon searches by my maths.

Amazon has not released any data on Rufus usage publicly; except from stating that Rufus had serviced "hundreds of millions of purchases" in beta testing when announcing the full rollout of Rufus onstage at Amazon Accelerate in September '24.

However, whilst they have not given us raw numbers, in October '24, in an AWS blog they did tell us how much compute they had to allocate for Rufus queries during Prime Day: 80,000 AWS Inferentia and AWS Training chips, collectively processing 3 million tokens per minute.

In true Amazonian style, we can therefore work backwards to calculate how many queries Rufus got during this period. Assuming the average query length on Rufus is similar to that on Perplexity (10-11 words) and each word comprising approximately 1.5 tokens (common in natural language processing), this results in an average of 15.75 tokens per query.

Given that Rufus' infrastructure was built to process 3 million tokens per minute, Rufus' handled approximately 190,476 queries per minute. Over a 24-hour period, this translates to a capacity of 274.3 million queries per day.

Amazon receives approximately 2 billion searches per day, thus Rufus accounts for ~13.7% of these in October '24. This percentage is growing rapidly, and we expect it could reach 25-35% by the end of 2025.

To stay ahead, Brands clearly need to be thinking about optimizing for AI powered search and you can use Ecomtent for that!