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.
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.
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:
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.
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:
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.
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:
| Attribute | Supplier 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 engine | free-text marketing phrase | Sampling / Modeling (fixed list) |
| Polyphony | ‚256-stimmig', ‚256 poly', in PDF only | 256 |
| 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.
Productbay runs the same three-step job that structures every category, aimed at exactly this attribute problem:
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.
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