Product cards rendered from your catalog

Catalogs change daily; design shouldn't lag behind. Map your product feed to a Rendry template; {title}, {price}, {old_price}, {photo}, {sku_barcode}, and render cards per SKU: for the storefront, marketplaces, social ads and shelf price tags. When the price changes, re-render; the design never drifts.

Components make rich cards fast: price bursts, sale ribbons, rating stars are ready-made blocks the editor (or your agent, via insert_component) drops into a template. Photo backgrounds strip clean with built-in background removal.

Start free; 100 renders/month · Documentation

Why teams and agents use it

  • Feed-driven. Any catalog that can POST JSON renders cards; direct API, n8n/Make flows, or an agent reading your feed over MCP.
  • Barcodes that scan. EAN-13 and Code128 layers validate content at render time, a wrong digit fails loudly instead of printing garbage.
  • Clean product photos. remove_background cuts the product from any photo; drop the cutout on a brand background with a soft shadow.
  • Every format at once. Card for the site, square for Instagram, tag for the shelf; separate templates, same data row, one batch call each.

Ready-made templates for this

  • Product Card: 1080x1350 product card. Light pastel mesh, product photo with soft shadow, red circle discount badge, gradient price, dark CTA pill. Mood: clean marketplace. Use for: e-commerce listings, catalogs. (1080x1350)
  • Spec Rows Card: Portrait spec sheet: four grouped rows, each an accent bar + label + value. Warm ink on cream, Unbounded headline. Use for: product specs, plan comparison, before/after numbers, menu of services. (1080x1350)
  • Price Tag: Shelf price tag with product name and big price. Use for: retail shelves and markets. (500x300)
  • Round Product Label: Circular die-cut label: the canvas itself is masked to a circle, so the PNG ships with transparent corners and prints as a sticker. Wax-seal ring, arched brand line, centred product name. Use for: jars, bottles, jam and honey labels, packaging seals. (800x800)
  • Sale Burst: Loud square sale post: starburst behind the price, curved arrow pointing at the CTA, scattered sparkles. Near-black + acid yellow. Use for: flash sales, discounts, limited drops. (1080x1080)
  • Restaurant Menu Item: Menu item card with photo, name and price. Use for: cafe/restaurant menus and food delivery. (800x1000)
  • Real Estate Listing: Property listing card: photo, price, address, specs. Use for: real estate listings. (1080x1350)

Built for AI agents, not just humans

Rendry ships a native remote MCP server (https://rendry.io/api/v1/mcp) with 25 tools. Your agent designs templates from raw JSON DSL, previews them for free, then renders batches. Full control over every pixel stays with the agent, while a human can always open the same template in the visual editor and adjust it. No headless browser, no screenshot hacks, no glue code.

Machine-readable: llms.txt · llms-full.txt · openapi.json · mcp.json

Frequently asked questions

Can prices update automatically?
Yes: render is stateless: re-POST with the new price and overwrite the stored image. Nightly re-render of changed SKUs is a common cron pattern.
Do you support marketplace image requirements?
Canvas size is exact per template (up to 4096×4096 px), so you set the dimensions a marketplace demands and every render complies.
Can an AI agent build our card design?
Yes: agents design templates from raw JSON DSL over MCP, with free previews to iterate. Your team then adjusts the result in the visual editor if needed.

Related