Buy MerchKit if you're pushing a few thousand SKUs onto Shopify, Amazon and Google with channel-tuned copy and imagery; buy Anglera if 100k+ SKUs of multi-supplier spec data must be made complete and cited inside your PIM.
Both claim to enrich product data. This page is about where that claim stops.
Merchkit lists AI Product Data Enrichment as one of its three capability areas and Anglera does enrichment work too, so the comparison isn't the first pass over a supplier file — it's who owns the schema six months later, when buyers start asking for things the rules you wrote were never written to describe.
Mine every spec from every source.
Every value traced to a document you can open. The catalog is only as honest as what it was built from.
Aim the catalog at the buyer who actually buys.
Grounded data still loses if it answers questions nobody asked. Alignment is what turns specs into conversion.
Product data is a practice, not a project.
Markets move, suppliers reissue, buyers change what they ask for. A catalog that is right in March is wrong by August unless something is watching.
Scored against public documentation. Grouped by the three acts — so you can see which ones MerchKit leaves on your desk.
Mines supplier PDFs, spec sheets, manuals, images, sites
PDFs, spec tables, drawings, manuals, images, sites
Fills customer-defined attributes; no new-field discovery
Proposes fields your schema never had
Acceptable-value constraints; normalizes units, formats, naming
Normalizes and governs allowed values, versioned
Auto-categorization plus channel and marketplace category mapping
Auto-classifies; channel and marketplace mapping
No documented source citations on enriched values
Every value cites its source doc and page
Serves B2B and B2C; no persona-tailored output
B2B specifier and B2C shopper enriched differently
Optimizes listings from channel performance data; limited signal sources
Reviews, search, competitor rails, social — fed back
Titles, descriptions, bullets, FAQs, SEO metadata, translations
Original copy per persona and channel
Generates lifestyle images, infographics, diagrams, videos; Growth tier+
Generates studio-grade imagery for photoless SKUs
Markets continuous enrichment; autonomous re-run cadence undocumented
Re-enriches on its own after go-live
Per-channel readiness scoring; gaps prioritized by sales impact
Scored against your standards; nothing publishes below bar
Syncs to Shopify; PIM/ERP connectors on Scale tier
Writes back to PIM, ERP, warehouse, commerce
API and webhooks on Scale tier only; no MCP
API, webhooks, and MCP servers
Software with review queues; customer's team owns work
Anglera owns the work; review is a guardrail
“Buyer signals” is the emptiest phrase in this category, so here is the literal thing. Each of these is an observation from a live market, the gap it exposes, and the field that gets created as a result.
Four reviewers in a row say a version of "the sofa fits, the box doesn't — the crate was about a foot deeper than the sofa and it wouldn't make the turn at the top of the stairs."
The catalog carries assembled depth only. Carton dimensions exist on the supplier's freight sheet and never made it onto the listing, so nobody can answer the question buyers are actually asking before delivery day.
carton_depth_in (with carton_width_in, carton_height_in and assembled_depth_in kept as separate fields)Numeric, inches, one decimal; assembled and carton dimensions must never be written to the same field.A recurring cluster of queries on a jewelry catalog: "nickel free hoops", "hypoallergenic 14k", "earrings for sensitive ears". They return either nothing or the whole gold department.
Metal is modelled as one flat value — "14K Gold", "Sterling Silver" — which describes the surface, not the alloy substrate or the post. Nickel is the thing being shopped for and it isn't a field, so it can't be filtered, faceted, or answered by a shopping agent.
nickel_declaration (paired with post_material for pierced styles)Nickel-free (tested) | Nickel-safe plating over nickel-bearing base | Contains nickel | Not declared by supplierOn an identical 65W USB-C wall charger, their bullets read "GaN, PPS 3.3–21V / 5A, PD 3.1" and their filters let you narrow to PPS. Ours reads "fast charging for phones, tablets and laptops."
Charging protocol lives in prose, not in a field. A buyer who needs PPS to fast-charge a specific handset can't filter for it, and an AI shopping agent parsing the page has nothing structured to match on — the spec is in the supplier's datasheet, just not in the catalog.
charging_protocols_supported (multi-select) plus pps_voltage_range_v and pps_max_current_aUSB PD 3.1 | USB PD 3.0 | PPS | Quick Charge 4+ | Quick Charge 3.0 | Proprietary | Not declared by supplierAn enrichment run is a snapshot of what you knew to ask for the day you ran it. Merchkit's attribute creation page describes two inputs: business rules you define in plain English, and computer vision that extracts color, texture, and style straight from product images. Enriched data is validated against those rules before it's applied to the catalog. That's a sound loop. The rules are still the part that ages. Six months on, a supplier renames a spec column, a marketplace adds a required field, and buyers start searching a term nobody modelled. Fill rate reads green, because every field you defined is populated. The miss is the field you never defined, and nobody files a ticket for an attribute that was never there. That's the work after the first pass: watch what buyers ask, what channels now demand, what suppliers changed — then re-cut the schema and back-fill the SKUs already live.
Values are normalized into a governed, versioned set of allowed values — so a filter works, and keeps working after the next import.
3/4 in0.75"3/4"19mm3/4 inchDN200.75 in (DN20)Six suppliers, six spellings, one physical size. Filters only work once they agree.
BlkblackBLACK MATTEMatte BlkRAL 9005Black — MatteFree text makes a colour filter useless. A governed value makes it a facet.
SS316316 StainlessStainless Steel 316A4 StainlessStainless Steel — 316 / A4Same alloy, four vocabularies, plus a trade name. Buyers search all of them.
Filling the fields you defined has an invisible ceiling: a catalog can hit 100% complete and still miss the attribute that loses the sale, because completeness is measured against a schema someone drew years ago. Schema Foundry reads competitor listings, buyer searches, review complaints and your supplier docs, and proposes the fields you never defined — which is where MerchKit stops.
How Schema Foundry works
Merchkit is an AI-powered product catalog platform that ingests product data from CSVs, PDFs, images, spec sheets, and APIs, enriches attributes and generates channel-optimized content, then syndicates listings to Shopify, Amazon, Google, and AI shopping engines. It targets B2C and B2B retailers, brands, and distributors with catalogs from 500 to 5M SKUs. Listed integrations include Shopify, WooCommerce, BigCommerce, Commercetools, Salesforce, Akeneo, and Salsify.
Pricing: Public pricing: Core plan at 999 USD per month covers up to 1,000 SKUs updated monthly on one channel with one seat; Growth (up to 10,000 SKUs) and Scale (unlimited) are custom-priced. A 5,000 USD four-week go-live onboarding package is also offered.
MerchKit websiteRetailers and brands pushing a small-to-mid catalog to Shopify, Amazon and AI shopping engines, who need per-channel titles, bullets, SEO copy and lifestyle imagery more than PIM-grade spec data.
We'd rather tell you here than in month three of an implementation.
Capability verdicts reviewed against MerchKit's public documentation on July 14, 2026. Vendors ship quickly — if something here is out of date, tell us and we'll correct it.
Bring one category and your supplier files. In 30 minutes you'll see it enriched — complete, structured, and consistent enough to launch on — plus the attributes your schema didn't have yet.
Book a demo