Why developers build product creative generation with Pixelixe


The problem is not making one product card. It is rendering reliable, branded product visuals every time catalog data, prices, offers, collections, localization, or campaign logic changes.



Feed-ready inputs

Map product feed rows, PIM records, CSV exports, backend payloads, or merchandising data directly to named template layers.

Promo and price logic

Generate sale images, price-drop creatives, discount badges, collection banners, and campaign variants from changing offer data.

Market localization

Switch currency, language, legal lines, CTA text, product assortments, and market-specific offers without duplicating layouts.

API-first output

Return product visuals as hosted image URLs, image files, base64 strings, PDFs, or editable HTML variants for downstream systems.


Product visuals your system can generate


Use this page for catalog-driven product creative automation: the developer implementation path behind ecommerce promos, feed-based merchandising, and product visual generation at scale.



Price-drop creatives

Render sale graphics from current price, original price, discount percentage, product image, and offer copy.

Collection banners

Generate category, collection, bundle, or seasonal banners from product sets and merchandising rules.

Product highlights

Create product cards for new arrivals, best sellers, back-in-stock items, bundles, or featured product modules.

Marketplace assets

Produce channel-specific product visuals for storefronts, marketplaces, ads, email, social, and landing page sections.

Localized product promos

Use the same template for FR, UK, DE, ES, US, or regional variants while changing language, currency, pricing, and legal text.

Recurring catalog refreshes

Trigger new renders when catalog rows change, prices move, products are featured, inventory updates, or campaign feeds refresh.


Catalog fields teams usually map


The Product Image Automation API works best when your template layer names match the fields your ecommerce stack already owns. That keeps the creative system predictable and easier to debug.



SKU or product ID

Attach each generated visual to your product record, SKU, slug, variant ID, or internal campaign key.

Product name

Insert product names, collection titles, category names, or merchandising headlines.

Product image URL

Map product shots, lifestyle images, packshots, or generated product visuals into image layers.

Price and sale price

Render regular price, sale price, discount label, price suffix, currency, or market-specific pricing.

Offer title

Use campaign copy, seasonal labels, promo names, shipping messages, or urgency labels.

Category or collection

Group outputs by collection, category, campaign, channel, or merchandising module.

Locale and market

Route language, currency, country, market, legal text, or store-level values into localized product creatives.

CTA and URL

Keep generated assets connected to landing URLs, campaign URLs, product links, or downstream tracking IDs.


Product image automation request examples


Save the product creative template once in Pixelixe Studio, then call the Image Automation API from a catalog job, backend route, feed processor, or merchandising workflow.



cURL

Feed row
curl -sS -X POST "https://studio.pixelixe.com/api/graphic/automation/v2" \
  -H "Content-Type: application/json" \
  --data '{
    "api_key": "YOUR_API_KEY",
    "document_uid": "product-promo-template",
    "format": "json",
    "image_type": "png",
    "custom_field": "sku:DRIP-042|market:us",
    "modifications": [
      { "name": "product_name", "text": "Copper Drip Coffee Maker" },
      { "name": "offer_title", "text": "Spring Deal" },
      { "name": "price", "text": "$79" },
      { "name": "sale_price", "text": "$59" },
      { "name": "product_image", "image_url": "https://cdn.example.com/products/drip-042.png" },
      { "name": "cta", "text": "Shop now" }
    ]
  }'

Typical when a feed processor needs a hosted image URL for each product, price-drop, or merchandising record.

JavaScript

Catalog job
async function renderProductCreative(product) {
  const response = await fetch(
    "https://studio.pixelixe.com/api/graphic/automation/v2",
    {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({
        api_key: process.env.PIXELIXE_API_KEY,
        document_uid: "product-promo-template",
        format: "json",
        image_type: "png",
        custom_field: `${product.sku}:${product.locale}`,
        modifications: [
          { name: "product_name", text: product.name },
          { name: "offer_title", text: product.offerTitle },
          { name: "price", text: product.priceLabel },
          { name: "sale_price", text: product.salePriceLabel },
          { name: "product_image", image_url: product.imageUrl },
          { name: "cta", text: product.ctaLabel }
        ]
      })
    }
  );

  const payload = await response.json();
  return payload.image_url;
}

Useful when your ecommerce backend, PIM, or internal merchandising app owns the product data and triggers creative rendering.

Python

Batch render
import json
import urllib.request

def render_product_visual(row):
    payload = {
        "api_key": "YOUR_API_KEY",
        "document_uid": "product-promo-template",
        "format": "json",
        "image_type": "png",
        "custom_field": f"{row['sku']}:{row['market']}",
        "modifications": [
            {"name": "product_name", "text": row["name"]},
            {"name": "offer_title", "text": row["offer"]},
            {"name": "price", "text": row["price"]},
            {"name": "sale_price", "text": row["sale_price"]},
            {"name": "product_image", "image_url": row["image_url"]},
            {"name": "cta", "text": row["cta"]}
        ]
    }

    request = urllib.request.Request(
        "https://studio.pixelixe.com/api/graphic/automation/v2",
        data=json.dumps(payload).encode("utf-8"),
        headers={"Content-Type": "application/json"},
        method="POST"
    )

    with urllib.request.urlopen(request) as response:
        return json.loads(response.read().decode("utf-8"))["image_url"]

Good for scheduled catalog refreshes, spreadsheet exports, PIM synchronization, marketplace image jobs, and localization batches.


From catalog input to generated product creative


The stable part is the approved template. The variable part is the product record. Developers usually connect Pixelixe after the merchandising system has already decided which product, price, offer, locale, or collection needs a visual.

  • Read product fields from a feed, PIM, CMS, spreadsheet, database, or internal API.
  • Map those fields to named text, image, shape, or background layers in a Pixelixe template.
  • Render one or many product creative variants as PNG, JPEG, JSON, base64, PDF, or HTML.
  • Attach the returned output to a campaign, product record, storefront, marketplace, email, ad, or workflow queue.

This developer page is the implementation layer. For the ecommerce team view, see Product Feed Promo Automation. For the broader platform, start with the Image Automation API.

{
  "sku": "DRIP-042",
  "product_name": "Copper Drip Coffee Maker",
  "category": "Kitchen",
  "collection": "Spring Deals",
  "image_url": "https://cdn.example.com/products/drip-042.png",
  "price": "$79",
  "sale_price": "$59",
  "currency": "USD",
  "locale": "en-US",
  "offer_title": "Spring Deal",
  "cta": "Shop now",
  "destination_url": "https://example.com/products/drip-042"
}

Common API triggers for catalog-driven creative


Product creative automation usually starts from a data event. Pixelixe fits after that event, when the system knows which template and product fields should be rendered.



Price or promo changes

Render new visuals when sale prices, discount percentages, campaign labels, or offer rules change.

Product status events

Generate product images for new arrivals, best sellers, back-in-stock updates, bundles, or clearance items.

Collection refreshes

Build category, collection, seasonal, or campaign banners when merchandising sets are updated.

Localization runs

Render variants per market when currency, language, assortment, legal text, or channel copy changes.

Merchandising calendars

Schedule recurring product creative jobs around drops, holidays, retail moments, weekly offers, and marketplace campaigns.


How this differs from adjacent Pixelixe pages


This page should rank for the developer intent around product feeds, catalog data, ecommerce assets, and API-rendered product creative. Related pages cover wider or more business-facing workflows.



Product Image Automation API

  • Developer implementation path for catalog-driven product creative rendering.
  • Best for product feeds, PIM data, ecommerce backends, marketplace jobs, and API payloads.
  • Focused on product image fields, price updates, sale visuals, SKU identifiers, and merchandising assets.
  • Designed for teams that need predictable rendering inside backend or feed pipelines.

Product Feed Promo Automation

  • Business use-case page for ecommerce, merchandising, growth, and catalog operations teams.
  • Best when the question is how to operationalize recurring product promos.
  • Explains workflows, use cases, teams, and business outcomes without focusing on endpoint details.
  • Useful for buyers before they need code-level implementation examples.

Product image automation FAQ


These are the practical questions developers and ecommerce platform teams ask when moving product creative generation into an API workflow.



Can I generate product images from a product feed or catalog?

Yes. Save the branded product template once in Pixelixe Studio, then call the Image Automation API with product feed fields such as product name, image URL, price, offer, category, locale, and CTA.

Can Pixelixe generate price-drop creatives automatically?

Yes. Pixelixe can render price-drop images by mapping regular price, sale price, discount badge, product image, currency, and campaign copy into reusable templates.

Can I localize product visuals by market or currency?

Yes. Product image automation workflows can change currency, language, offer labels, legal text, CTA copy, and country-specific product fields while keeping the same approved layout.

Which outputs can the API return?

The API supports image, json, base64, pdf, and html response formats, so teams can use rendered files, hosted image URLs, editable HTML variants, or downstream automation outputs.

How is this different from the product feed promo automation use case?

This developer page explains the API implementation path for catalog-driven product image generation. The product feed promo automation page explains the business workflow for merchandising and ecommerce teams.


Explore related ecommerce and developer workflows


Use this page for product image automation, then move into broader ecommerce, spreadsheet, personalization, and dynamic banner workflows depending on who owns the data source.



Product feed promo automation

Use the business workflow view when ecommerce and merchandising teams are evaluating catalog-driven promo production.

Dynamic banner generation

Use the broader developer guide for template-based banner rendering across campaign, ad, and marketing use cases.

Spreadsheet image generation

Use spreadsheets when merchandising or ecommerce teams want a lower-code path for recurring product creative runs.

Image Personalization API

Use personalization when product visuals depend on customer segment, lifecycle stage, CRM attributes, or recipient-level data.




Ready to generate product creatives from catalog data?

Start with one approved product template in Pixelixe Studio, connect the Image Automation API, and let your feed, catalog, PIM, or ecommerce backend generate product visuals when merchandising data changes.


Start a 10-day trial
Read the docs