ContentHubGPT vs Lily.ai for Retailers: What the Comparison Is Missing
If you are comparing ContentHubGPT and Lily.ai for your retail ecommerce business, you are already asking the right question: which AI product content tool is actually built for my problem? The answer, for most UK mid-market retailers, is that neither was.
Not because they are bad tools. They are not. But ContentHubGPT and Lily.ai were each designed for a specific type of buyer, and the fit matters considerably when you are putting your product catalogue through an AI system.
This guide explains what each tool does, where it is strong, and what to look for when neither fully fits your requirements.
What ContentHubGPT is
ContentHubGPT is a generative AI content platform built by GSPANN, a US-based technology consultancy. It generates product descriptions, marketing copy, blog posts, and social content from product data. It integrates with Shopify, BigCommerce, Salsify, Amazon, and Walmart.
The platform is designed for enterprise content operations at omnichannel scale. It emphasises compliance governance (ensuring AI-generated content meets internal brand and regulatory standards), hyper-personalisation (generating different content variants for different audience segments), and SEO optimisation. It is positioned as a horizontal content platform that happens to include product descriptions, rather than a specialist retail merchandising tool.
Pricing on the Shopify App Store runs from £25/month for 50 product calls to £125/month for 500, with enterprise pricing for higher volumes. The GSPANN enterprise platform has separate custom pricing.
ContentHubGPT is a strong fit if: you are a larger organisation managing content across multiple channels (email, social, blog, and product) and need a single platform with compliance governance. If product descriptions are one output among many content types your team produces, the horizontal approach makes sense.
ContentHubGPT is less well suited if: your primary challenge is catalogue-scale retail product content, you need configurable product attribute schemas, you need image-to-attribute extraction, or your team is in the UK and wants a platform that understands UK retail taxonomy and ecommerce norms.
What Lily.ai is
Lily.ai is a US-based AI platform focused on product attribution and discovery. Its core capability is taking vague consumer-language search queries (“flowy summer dress in coral”) and matching them to retailer inventory using enriched product attributes. It is best known for its M&S deployment, where it improved product discoverability across a large fashion catalogue.
The underlying technology is about bridging the gap between how retailers describe products (in trade or spec language) and how consumers search for them (in emotional or occasion language). This is “product attribution” rather than “product description generation.”
Lily.ai is a strong fit if: you are a fashion retailer with an existing product catalogue where descriptions exist but product discoverability in search and on-site is poor. You want to layer better product attribute enrichment on top of what you already have, not generate content from scratch.
Lily.ai is less well suited if: you have thin or missing product content (descriptions do not exist or are incomplete), you need multilingual output, you are not in the fashion or apparel vertical, or you are a UK mid-market retailer rather than a large enterprise.
Where the comparison usually falls short
Buyers comparing ContentHubGPT and Lily.ai are often doing so because they appeared in the same roundup article or category listing. But the products serve different use cases at different price points for different buyers.
The comparison that is often missing is with purpose-built retail catalogue content platforms: tools designed specifically to generate structured, schema-compliant product content at catalogue scale, from product images or minimal source data, ready for PIM or ecommerce platform import.
The specific capabilities that matter for catalogue-scale content operations are:
Configurable product attribute schema. Each retailer has a different data structure. Flooring retailers need wear rating, coverage, installation method, and thickness. Fashion retailers need size range, fabric composition, fit type, and occasion. A purpose-built platform lets you define exactly which attributes to generate, in which format, for your product type. Generic content tools produce prose; they do not map outputs to schema fields.
Image-to-attribute extraction. Retailers frequently hold product images but incomplete spec data. Supplier data sheets have gaps. Internal records are inconsistent. A purpose-built retail AI platform reads product images to extract material, colour, finish, and design attributes before generation begins. A £5,000 sofa photographed against a white background can yield a complete product record from the image alone.
Batch processing at catalogue scale. Processing 3,000 SKUs requires a pipeline, not a prompt interface. A purpose-built retail platform accepts a product feed (via CSV, spreadsheet, ZIP, or API), processes it end to end, and returns a structured import file. No manual prompting per product, no copy-pasting into a spreadsheet.
Multilingual generation (not translation). Retailers selling in multiple markets need content generated natively in each language, not machine-translated from English. Native generation means culturally appropriate copy and SEO-relevant phrasing in each market. Translation at scale introduces quality inconsistencies that native generation avoids.
How merchi.ai fits into the comparison
merchi.ai is a purpose-built retail catalogue content platform designed for UK retailers. It generates structured product content from product images and data, applying your product attribute schema to produce titles, descriptions, technical attributes, taxonomy classifications, and meta content, all in one batch run.
The key differences in practice:
| Capability | ContentHubGPT | Lily.ai | merchi.ai |
|---|---|---|---|
| Product description generation | ✅ Yes | ❌ Not primary | ✅ Yes, at catalogue scale |
| Configurable attribute schema | ❌ Not retailer-configurable | ❌ Not retailer-configurable | ✅ Fully configurable |
| Image-to-attribute extraction | ❌ No | ❌ No | ✅ Core capability |
| Taxonomy classification | Partial | ✅ Fashion-specific | ✅ ETIM, Shopify, GS1, custom |
| Batch processing from a feed | ❌ Limited | ❌ No | ✅ Core capability |
| Multilingual generation | ❌ Translation only | ❌ Limited | ✅ 40+ languages, natively |
| Blog / social / marketing copy | ✅ Yes | ❌ No | ❌ Not in scope |
| Compliance governance | ✅ Enterprise-grade | ❌ No | ✅ AI Provenance Protocol |
| UK mid-market retail focus | ❌ US enterprise focus | ❌ US enterprise focus | ✅ Built for this |
merchi.ai is not a horizontal content platform and it is not a product attribution layer. It is the specialist tool for the specific problem most mid-market retailers actually face: a product catalogue with thin content, missing attributes, no multilingual variants, and a team that cannot scale the manual work.
A UK retailer deploying merchi.ai cleared a 1,000-product backlog without adding headcount, contributing to 976% online revenue growth. That outcome was not produced by a general content platform or an attribution enrichment layer. It came from a tool that handled the complete content pipeline: images in, structured catalogue content out, directly importable into the ecommerce stack.
How to choose
Use ContentHubGPT if: you are an enterprise managing multiple content types across channels, compliance governance is a requirement, and product descriptions are one content type among many.
Use Lily.ai if: you are a large fashion retailer with existing catalogue content where the problem is product discoverability rather than content creation, and you are primarily interested in attribute enrichment for your existing descriptions.
Use merchi.ai if: your primary challenge is generating or improving product content at catalogue scale, you need configurable schema output ready for PIM import, you have a multilingual requirement, and you want a platform built specifically for retail merchandising rather than general content.
For a deeper look at how the broader landscape of AI product content tools compares, see The Best AI Tools for Ecommerce Product Content in 2026 and Lily.ai Alternatives for Retailers.
See what merchi.ai does with your products
The best way to evaluate any AI content platform is to run it against your own catalogue. Book a free 30-minute demo and we will show you exactly how merchi.ai handles your product types, your schema, and your volume requirements. Or start a 30-day free trial with no upfront commitment.
Frequently Asked Questions
What is the difference between ContentHubGPT and Lily.ai?
ContentHubGPT is a horizontal AI content platform that generates product descriptions, marketing copy, blog posts, and social content, with a focus on compliance governance and omnichannel publishing. Lily.ai is an AI product attribution platform focused on enriching existing product data to improve ecommerce search and discoverability, primarily for fashion retailers. The two tools serve different buyers: ContentHubGPT suits enterprise teams managing multiple content types; Lily.ai suits large fashion retailers trying to close the gap between how products are described and how consumers search.
Is ContentHubGPT suitable for UK retailers?
ContentHubGPT is designed primarily for the US enterprise market. It integrates with US platforms including Walmart and Amazon, and its compliance and governance features are oriented toward US enterprise requirements. UK retailers with Shopify or WooCommerce stores can use the Shopify app, but the broader platform is a US enterprise product. UK mid-market retailers managing a product catalogue are generally better served by a platform built for UK retail contexts, taxonomy, and compliance requirements.
Does Lily.ai generate product descriptions from scratch?
No. Lily.ai’s core capability is product attribute enrichment and attribution: it takes existing product data and enriches it with additional attributes to improve search and discovery. It is not primarily a content generation tool. If your catalogue has thin or missing product descriptions, Lily.ai is not the right starting point. You need a generation-first platform that can create content from product images or minimal source data.
What is the best alternative to ContentHubGPT for a UK retailer?
For UK retailers whose primary need is product catalogue content at scale, a purpose-built retail content platform is a better fit than ContentHubGPT’s horizontal approach. merchi.ai generates structured, schema-compliant product content from product images in up to 40 languages, with configurable attribute schemas and batch processing pipelines designed for catalogue-scale operations.
What is the best alternative to Lily.ai for smaller retailers?
Lily.ai is designed for large fashion enterprises. Smaller retailers and non-fashion verticals typically need a different solution. For retailers with thin or missing product content who need to generate complete product records at scale, merchi.ai is the fit: it generates descriptions, technical attributes, taxonomy classifications, and multilingual variants from product images, without requiring an existing content layer to enrich.
How does the AI Provenance Protocol relate to ContentHubGPT and Lily.ai?
The AI Provenance Protocol is an open standard for attributing AI-generated content, developed by merchi.ai. It is relevant to the EU AI Act’s Article 50 transparency requirements, which require disclosure when AI has been used to generate content that consumers interact with. merchi.ai tags every piece of generated content with provenance metadata (model, prompt version, generation timestamp) by default. ContentHubGPT has its own compliance and governance layer. Lily.ai’s attribution enrichment layer operates at a different point in the content lifecycle and is not primarily a generation compliance tool.
Can I use more than one of these tools together?
In some deployments, yes. A retailer might use merchi.ai to generate complete product records from scratch, then use Lily.ai’s enrichment layer to further improve attribute quality for on-site search. In practice, for mid-market retailers, the overhead of managing two platforms rarely justifies the marginal improvement. merchi.ai handles the full generation and enrichment pipeline in a single workflow for most retail use cases.
