For the complete documentation index, see llms.txt. This page is also available as Markdown.

Changelog

New updates and improvements

Google Shopping fields

googleGoogle Shopping fields

Product Pelican can now fill the Google Shopping field set on your products — the data your Google feed is built from. Category, condition, gender, age group, custom product and five custom labels, written where every feed tool already looks for them.

Find it on AI Prompts → Category (for the Google product category) and AI Prompts → Metafields → Google Merchant Center (for everything else).

📸 Screenshot needed — the Google Merchant Center section on AI Prompts → Metafields with a few fields ticked.

The Google product category is looked up, not guessed

Shopify's product taxonomy already carries a matching Google category for every category it knows. So Product Pelican doesn't ask the AI twice — it sets the Shopify category, then reads the Google one straight off the mapping.

Switch it on and accepting a category suggestion sets both. The suggestion list shows the Google category underneath each candidate, so you see what will be written before you accept it. Products that already have a category pick theirs up in the Descriptions check, so there is no need to re-categorise a catalogue that is already done.

The rest fills alongside your descriptions

Field
What goes in it

Condition

new · refurbished · used

Gender

male · female · unisex

Age group

newborn · infant · toddler · kids · adult

Custom product

true for handmade, made-to-order or own-brand items without a barcode

Custom label 0–4

Whatever you segment your campaigns by

Each one gets its own row and its own accept checkbox in the results, and the fields with a fixed vocabulary are shown as a dropdown — the AI cannot invent a value Google would reject.

The fields appear in your Shopify admin too. The first time a value is written, Product Pelican creates the field's definition in your store, so you can see and edit it on the product page. If you already have one, yours is left untouched.

Image analysis

Product Pelican can now look at your product photos. Turn image analysis on and your photos are shown to the AI alongside the product data, so what it writes is based on the product as it actually appears — not just its title, type and tags.

Available to all stores, on every plan. Find it on AI Prompts → Description, under Image analysis.

Image analysis

What it improves

Once it is on, photos feed three things:

  • Product descriptions — colour, material, cut, pattern, styling details and what is actually in the shot.

  • Generated metafields — the fields generated alongside the description are grounded in the same photos, so attributes like colour or material stop being guesses.

  • Image alt text — alt text is written from the image being described rather than from filename clues, which is what makes it genuinely useful for accessibility and SEO.

Choose how many photos to check

Set Images checked per product to anywhere from 1 to 5. More photos give the AI a fuller view — useful for products where a second or third shot shows the back, the fabric, or the scale — at the cost of more of your monthly allowance.

Alt text always uses the single image it is writing for.

Your monthly allowance

Each analysed photo counts once against a monthly limit that depends on your plan.

Plan
AI image analyses / month

Free

10

Standard

1,000

Pro

3,000

Max

6,000

The allowance resets on the 1st of every month.

Running out never blocks you. If you use your allowance up, generation carries on exactly as before — from the product data, without the photos — and the description panel tells you the images were skipped. Nothing fails and nothing is lost.

Also in this release
  • See the AI's reasoning. A Show thinking link now sits next to the generated description and next to each generated metafield, revealing the reasoning behind the suggestion — including on generations that fail, so you can see what went wrong.

  • Accept the description and the metafields separately. The description has its own checkbox, so you can apply only the metafields you want without touching the description.

  • Missing metafields are called out. If a configured field comes back empty, it is listed rather than silently dropped.