Product Data for Keyboard Instruments: Technical Attributes, Clearly Comparable

Digital pianos, stage pianos and keyboards are decided on specs — key count, action, sound engine. Here's how to turn inconsistent supplier feeds and PDF datasheets into one comparable attribute structure.

Jakob Feinböck, ProductbayJuly 4, 20267 min read
☝️Key takeaways
  • Keyboard instruments sell on technical attributes: key count (61/76/88), key action, touch sensitivity, sound engine, polyphony and connectivity — buyers compare exactly these fields.
  • Supplier feeds name the same spec differently (‚88 Tasten' vs ‚88-key') and often hide it in a PDF datasheet with no structured field — so filters and comparisons break.
  • The fix is one attribute group per category that forces every product onto the same fields and value lists, mapping each supplier's wording into it.
  • Productbay imports feed and datasheet, reads specs out of PDFs, and normalizes everything into comparable attribute groups — with a review step before publishing.

Two 88-key digital pianos sit side by side in your shop. One has a fully weighted hammer action and a sampled concert-grand engine; the other is semi-weighted with a lighter voice count. To the buyer, the only thing that decides between them is the spec sheet — and if your product data doesn't carry those specs cleanly, the customer can't compare, can't filter, and walks.

Product data for keyboard instruments is defined by a compact set of technical attributes — key count, key action, touch sensitivity, sound engine, polyphony and connectivity. Get those fields structured and consistent, and the whole category becomes comparable. Leave them as free text scattered across supplier Excels and PDF datasheets, and every filter breaks. This is a sub-category of the broader musical instruments challenge.

Which technical attributes actually drive the keyboard decision?

Unlike a variant-heavy category such as apparel, keyboard instruments are an attribute-rich world: one model, one SKU, but a deep spec sheet. The fields buyers compare are always the same:

  • Key count: 61, 76 or 88 keys — the first filter almost every buyer applies.
  • Key action: fully weighted / hammer action, semi-weighted, or synth-action — described differently by every brand (‚gewichtet', ‚hammer action', ‚GHS').
  • Touch sensitivity and sound engine: velocity response, sampling vs modeling, the sampled instrument behind the sound.
  • Polyphony, voices, speakers, connectivity: max notes, number of sounds, built-in amplification, USB / MIDI / Bluetooth — plus weight for stage use.

Because the value sits entirely in these attributes, inconsistent or missing fields don't just look messy — they make the products literally impossible to compare or filter in the shop.

Why do supplier feeds for digital pianos never align?

The core problem is that every distributor and brand describes the same attribute in its own words, and often hides the most important spec in an unstructured document. A single 88-key stage piano might arrive as:

  • An Excel price list with ‚88 Tasten' in a name column but no dedicated attribute fields.
  • A brand feed that writes ‚88-key, hammer action' — different wording, same meaning.
  • A PDF datasheet where polyphony and connectivity live only in the brochure text.
  • A CSV where the sound engine is a marketing phrase, not a structured value.

Import three suppliers like this and you get three different ways of saying ‚88 keys' and no shared value list. That's the manual work: someone reconciling wordings by hand before the range can go into a filter.

How do attribute groups turn this into a comparable catalog?

The fix is to define one attribute group per category and force every product onto the same fields with the same value list. Map each supplier's wording into it once, and comparability follows automatically:

AttributeSupplier wording (varies)Normalized value (attribute group)
Key count‚88 Tasten', ‚88-key', ‚88 notes'88
Key action‚gewichtet', ‚hammer action', ‚GHS'Fully weighted / hammer action
Sound enginefree-text marketing phraseSampling / Modeling (fixed list)
Polyphony‚256-stimmig', ‚256 poly', in PDF only256
Connectivity‚USB/MIDI', ‚Bluetooth MIDI'USB, MIDI, Bluetooth (multi-select)

Once ‚88 Tasten' and ‚88-key' collapse into one value, filters, spec tables and comparison views work — in the shop and in marketplace feeds. The attribute group is the skeleton; everything else hangs off it.

How does Productbay help with keyboard product data?

Productbay runs the same three-step job that structures every category, aimed at exactly this attribute problem:

  • Consolidate: import every source once — supplier Excel, CSV, feed URL, FTP, API — and match by SKU or EAN/GTIN so existing models update and new ones are created.
  • Enrich: AI reads specs like key count, action and polyphony out of PDF datasheets, maps each supplier's wording into your attribute group, writes descriptions and translates via DeepL — always with a review queue before publishing.
  • Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp) and feed exports for Amazon, OTTO and Kaufland, each with per-channel transformations.

The result is one comparable catalog where every keyboard carries the same structured fields, no matter which supplier it came from. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs. For the full instrument picture, start at the musical instruments overview.

Frequently Asked Questions

Let's look at your product data process

Key count, action, sound engine — keyboard buyers filter on specs, and every supplier names them differently. See how Productbay imports feeds and datasheets and normalizes them into one comparable attribute structure in a 30-minute walkthrough.

Get started