SShortSingh.
Back to feed

Low-resolution supplier photos can't be fixed into compliant Amazon main images

0
·4 views

A seller who built a preflight checker for Amazon main images explains that source resolution is the check that surprises sellers most. Amazon requires at least 500px on the longest side, and 2000px or more to enable buyer zoom, so the tool flags originals under 500px as FAIL and those under 2000px as WARN. Upscaling a small photo to 2000 x 2000 only stretches the same pixels, leaving edges soft and label text blurred even though the file dimensions look correct. The author advises requesting original, uncompressed files from suppliers, since messaging apps often downscale images, and reshooting if the original is unavailable. The checks cover technical requirements such as a pure white background and frame fill, while content rules like no text, props, or watermarks remain the seller's responsibility.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Why AWS VPC Peering Matters for Private Cross-Network Communication

A developer explores how Amazon VPC Peering lets isolated virtual networks communicate privately using internal IP addresses. Using an example of Sales, HR, and IT Support departments each in their own VPC, the article shows that multiple peering connections can be set up, but peering is not transitive, so two VPCs linked to a third cannot automatically reach each other. Peering can also span separate AWS accounts and even different AWS Regions. Inter-Region traffic travels over the AWS global backbone instead of the public internet, which the author highlights as a key cloud networking principle.

0
ProgrammingDEV Community ·

How Idempotent APIs Prevent Duplicate Payment Charges on Retries

Network failures such as dropped connections and timeouts often leave clients unsure whether a payment went through, so they retry, which can charge customers twice. Idempotent APIs address this by ensuring that repeating an operation produces the same result as performing it once. The common approach, used by providers like Stripe and Adyen, has clients attach a unique key to each request, which the server checks against a fast store such as Redis before processing. Cached responses are returned for repeat keys, and a temporary lock can block concurrent duplicate requests that arrive while the original is still running. Implementing this logic in middleware keeps core payment code decoupled from caching concerns.

0
ProgrammingDEV Community ·

Sendclap Lets AI Agents Pay Creators via x402 USDC Endpoint and MCP Server

Sendclap offers two ways for an AI agent to pay a creator without a browser: an HTTP 402 payment endpoint that accepts USDC on Base at a flat 1% fee, and a stateless MCP server for discovering creator offerings and generating checkout links. Neither endpoint requires the payer to create an account, and on Base mainnet the agent needs no ETH for gas because Sendclap submits the signed transfer. A tester checked both endpoints live on November 22, 2026, and reviewed the relevant server and contract code. The MCP server exposes nine tools, with six requiring a creator's API key, and get_checkout omits the payer's email to prevent exposure of buyer details. Errors share the same machine-readable codes as Sendclap's REST API.

0
ProgrammingDEV Community ·

Why shell=False Does Not Prevent Argument Injection in Subprocess Calls

A developer found that a subprocess call using shell=False and an argument list still produced a bug when a user-supplied value began with a dash, causing grep to treat it as an option. A second failure appeared on Windows under Git Bash, where the MSYS compatibility layer expanded a wildcard in the argument before the program received it. The author explains that both issues originate in arguments rather than the shell, so shell=False addresses command injection but not argument injection. Recommended mitigations include placing -- before user-supplied values, escaping glob characters on Windows, and re-reviewing calls after code changes. The author also released a scanner, sg audit, to detect these patterns in code repositories.