Product Data for Writing Instruments: Variants and Refill Systems
One pen line becomes dozens of variants, and every refillable pen belongs to a family of matching cartridges — where classifications help, and where the refill web forces manual work.
- ✓Writing instruments carry two data logics at once: deep variant matrices (color, ink, tip width, finish) and a refill web — which cartridge or lead fits which pen.
- ✓Refill compatibility is a linked attribute, not a column: it drives cross-selling and cuts returns, but supplier Excels ship pen and refill as unrelated rows.
- ✓Classifications like eCl@ss and ETIM group the assortment but don't carry tip widths, ink shades or the pen-to-refill cross-references — that's the longtail gap.
- ✓Productbay collapses variants into clean families and uses AI to build the refill links as linked attributes, then syncs to Shopify, Shopware and the marketplaces.
A single fineliner model looks like one product. Then you list it properly and it fractures: four ink colors, three tip widths, a black barrel and a white one — one line becomes a dozen SKUs, each with its own EAN/GTIN. Now add the part that catches every stationery retailer out: that mechanical pencil needs 0.5 mm leads, that fountain pen takes a specific cartridge format, that rollerball has exactly one matching refill. The pen and its refill are two products that only make sense together.
Product data for writing instruments is a variant problem tangled up with a refill-compatibility problem. That's what separates pens from most of the assortment on the office supplies shelf, and it's why a flat feed of articles never captures what a customer actually needs to know before buying.
Why do variants and refills make writing instruments so hard?
The core problem every multi-supplier retailer knows — no two suppliers deliver alike — is amplified for pens because you're maintaining articles and the relationships between them:
- Variant explosion: barrel color, ink color, tip width (F, M, B, or 0.3/0.5/0.7 mm), grip and finish multiply into a matrix. One model, dozens of SKUs — classic variant pain.
- The refill web: every refillable pen belongs to a family of matching leads, cartridges, ink converters or replacement tips. That's a relationship, not a column — and it runs both ways.
- Split supplier rows: most supplier Excels ship the pen and its refill as two unrelated lines, with no field that says „these belong together“.
- Longtail volume: a full stationery range is thousands of low-value SKUs, so the per-article margin can't justify hours of manual linking.
Do this by hand and it doesn't scale. The fix is the same as everywhere: consolidate, normalize, enrich and publish — but here the enrichment has to include the links between products, not just the products.
Do office-supply standards like eCl@ss or ETIM cover this?
Bürobedarf does have classification grids: eCl@ss and ETIM both classify office supplies into groups and give the industry a shared vocabulary. That's genuinely useful for structuring an assortment. But it's worth being honest about where a classification stops — especially for the variant-and-refill logic of writing instruments:
| Data layer | What eCl@ss / ETIM deliver | Where it stops |
|---|---|---|
| Group classification | Pen, marker, refill sorted into a class | No deep variant matrix per model |
| Variant attributes | Some standard properties defined | Tip width, ink shade, finish often thin or missing |
| Refill compatibility | Not modeled as a link | Pen-to-refill cross-references absent |
| Sales content | Not the job of a classification | Descriptions, SEO text, benefit copy missing |
| Longtail brands | Thin coverage | No-name and own-brand refills = Excel/PDF |
In short: eCl@ss and ETIM give you a classification skeleton and a shared language. What they don't give you is the deep variant depth, the sales content, or — most importantly — the refill cross-references that turn a loose list of pens and cartridges into a shoppable, cross-sellable catalog. That's the gap.
How does Productbay model variants and refill links?
The throughline is a three-step job, and the refill web is handled as first-class linked data — which is exactly what Productbay is built for:
- Consolidate: import every source once — supplier CSV, Excel, feed URL, FTP, API — and match on SKU or EAN/GTIN so variants collapse into clean product families instead of loose rows.
- Enrich: AI parses tip width, ink color and finish out of titles and datasheets, writes descriptions, assigns eCl@ss/ETIM-aligned categories, translates via DeepL, and builds the refill cross-references as linked attributes — so a refill knows its pens and every pen knows its refills. 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 — each with per-channel transformations.
Productbay starts where the classification ends: the variant depth, the sales content, and above all the pen-to-refill relationships no standard carries. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — from mid-sized shops to large chains.