Product Data for Photo: Getting Lens & Body Compatibility Right

In photo retail the sale hinges on one question — does this lens fit this body? That's a compatibility problem: mount, sensor format and system have to be modeled as clean, linked attributes, not buried in a description.

Jakob Feinböck, ProductbayJuly 4, 20267 min read
☝️Key takeaways
  • Photo retail is a compatibility problem first: the sale hinges on which lens fits which body — mount, sensor format and system, not just brand.
  • ICEcat covers the big camera and lens brands well, but thins out on third-party lenses, adapters, accessories and the used longtail — still Excel and PDF by hand.
  • Compatibility is relational data: mount and system have to be modeled as linked attributes, or the on-site filter returns wrong results.
  • Productbay maintains mount and system as structured, linked attributes and uses AI enrichment where ICEcat stops — the accessory and used longtail.

A customer walks into your shop — physical or online — with a Sony A7 IV and a budget for a telephoto lens. Everything they buy next depends on one invisible fact: the mount. Pick a lens with the wrong mount and it simply does not attach. That single relationship — which lens fits which body — is the beating heart of photo retail, and it is also the single hardest thing to get right in your product data.

Product data for photo is compatibility data first: mount, sensor format and system decide the sale before any spec or price does. This is a sub-category of the broader consumer electronics challenge, and it shares its optics-and-compatibility DNA with hunting & archery optics, where the same "does this fit that" logic drives scope and rail data.

Why is compatibility the hardest part of photo product data?

Most product data is descriptive — a weight, a color, a material. Compatibility is different: it is relational. A lens does not just have specs; it has a relationship to a set of bodies, defined by a small stack of attributes that all have to be correct at once:

  • Mount: the physical and electronic interface — Sony E-Mount, Canon RF and EF, Nikon Z, the L-Mount alliance (Leica/Panasonic/Sigma), Fujifilm X, Micro Four Thirds (MFT). This is the make-or-break attribute.
  • Sensor format / image circle: full-frame, APS-C or MFT. A lens can share a mount but not cover the sensor — an APS-C lens on a full-frame body vignettes. The filter has to know both.
  • System / adapter support: some lenses fit natively, some via a whitelisted adapter, some with autofocus caveats. The nuance belongs in the data, not in a support call.

Miss or mislabel one of these and the consequence is concrete: the product never appears in the right on-site filter, or it appears in the wrong one and gets returned. In photo, a wrong-mount return is not a rounding error — it is a costly, avoidable mistake baked into your data.

Does ICEcat cover it — and where does it stop?

Consumer electronics has a genuine data backbone: ICEcat, the open catalog that delivers clean, structured records for major manufacturers. For the marquee camera and lens brands — Sony, Canon, Nikon, Panasonic — ICEcat is genuinely strong and carries a lot of technical spec. But it is important to be honest about where its coverage thins:

Data layerWhat ICEcat deliversWhere it stops
Big-brand bodies & lensesClean, structured records with specsMount/system mapping may not match your filter logic
Third-party lenses (Sigma, Tamron, Samyang)Partial coverageMount variants and adapter support often incomplete
Adapters & filtersThin, brand-dependentCompatibility relationships rarely modeled
Accessories (bags, batteries, cages)SparseLongtail arrives as Excel / PDF
Used & vintage gearNoneYou are the data source — no feed exists

In short: ICEcat covers the core of the big brands well and gives you a spec skeleton. What it does not reliably give you is a working compatibility model across mounts and systems, nor the accessory and used longtail. That is exactly the gap that costs you sales and returns.

How does Productbay help photo retailers?

The throughline is a three-step job — and the difference for photo is that step two treats compatibility as first-class data, not free text:

  • Consolidate: import every source once — ICEcat, supplier CSV, Excel, feed URL, FTP, API — and match by SKU or EAN/GTIN so existing products update and new ones are created. Bodies, lenses and accessories land in one catalog.
  • Enrich — with linked attributes: instead of a free-text field reading Sony E, Productbay maintains mount and system as structured, linked attributes. A body and a lens that share a mount are actually connected in the data — which drives correct on-site compatibility filtering and cross-selling. AI writes descriptions, assigns categories, fills missing attributes from whitelisted sources, translates via DeepL and reads specs out of PDF datasheets — always with a review queue before anything publishes.
  • Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp) and feed exports for Amazon, OTTO and Kaufland — and the compatibility attributes survive the export instead of collapsing into a description string.

Productbay starts where ICEcat ends: it takes the clean big-brand records and adds the compatibility model, the third-party lenses, the adapters, and the accessory and used longtail no catalog carries. For the wider picture across TVs, audio and computing, see the consumer electronics overview. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — from mid-sized shops to large chains.

Frequently Asked Questions

Let's look at your product data process

Mounts, sensor formats, systems, adapters and a deep accessory longtail — photo data is compatibility data. See how Productbay models it as linked attributes and enriches the longtail in a 30-minute walkthrough.

Get started