Rosiglioni Impianti — main case study
Medical Gas B2B · Operational Reorganisation · Ongoing

Rosiglioni Impianti — Product Identity & Operational Infrastructure

A catalog of 5,300 SKUs grown through accumulation. Non-uniform codes, incomplete descriptions, classification knowledge distributed across people. Before building the equipment configurator, we had to build the foundation — clean, structured, governable. This is the work we did with Sabrina Rosiglioni, COO of the company.

Challenge

Catalog grown without a common language: non-uniform codes, incomplete descriptions, no management of obsolete items. Knowledge existed in people, not in the system. Blocking prerequisite for any digitalization effort.

Approach

Structured diagnosis of the existing system, architecture redesign with internal team, new taxonomy in 12 functional categories, readable SKU coding, operational data integration and documented operational guide.

Result

Governed catalog: 12 functional categories, readable SKU coding for anyone, operational data integrated, personnel guidance document. Data foundation ready to power the equipment configurator in development.

5.300
SKUs analyzed and reorganized
12
Functional categories in the new taxonomy
71%
SKUs with empty or generic SPEC field — main problem identified
Rosiglioni Impianti — medical gas equipment
SKUs reorganized
5.300+
Categories
12 functional
Output
Live catalog
Journey — Ongoing
Diagnosis
2024
Architecture
2024
Coding
2025
Integration
2025
Configurator
2026→
Context

The real problem: knowledge lived in people, not in the system

Rosiglioni Impianti is a company with decades of history in medical gas equipment for hospitals and healthcare facilities. A highly regulated market, with long sales cycles and technical documentation that lives almost entirely in people's knowledge.

Like many SMEs that grow through accumulation — one customer after another, one supplier after another — Rosiglioni had built over time a product catalog of over 5,300 SKUs. It worked. But it was becoming a problem.

The catalog had grown without a common language. Non-uniform codes between categories and suppliers. Descriptions incomplete or written in different ways by different people. Duplicate or near-duplicate items that no one had stopped to consolidate. An "Accessories" category with 2,763 items — the classic signal of a system that stopped classifying and started accumulating.

The result: every quote required someone with years of experience to know exactly where to look. Knowledge was not in the system. It was in people. Sustainable as long as the people are there. Not sustainable when the company grows, changes, or wants to build digital tools.

FASE_01

Decode

Read the system before touching anything: structured diagnosis of the existing catalog

Our entry didn't start with a brief. It started with a harder question: before communicating better externally, can you speak clearly internally?

The Decode phase involved quantitative and qualitative analysis of the existing catalog — structure, classification logic, data completeness, description consistency, distribution by category. The goal wasn't to find defects: it was to understand where the problems were and what their nature was.

What we found:

  • Non-uniform codes between categories and between suppliers — each part of the catalog had developed its own conventions
  • The SPEC field filled with GEN (generic) in 71% of cases — data that carries no useful information
  • Prices and stock not present in the catalog, managed separately in the management system
  • No explicit management of obsolete or replaced products — they lived in the catalog as active items
  • An "Accessories" category with 2,763 items — signal that the system stopped classifying and started accumulating
  • Classification knowledge existed only in people, not documented anywhere

The analysis produced a precise map of where the problems were and what their nature was. Some categories were well maintained; others nearly abandoned. Some suppliers had dozens of unconsolidated variants. The picture was clear.

FASE_02

Define

Redesign the architecture with those who know the system from the inside

The new architecture couldn't be designed from outside alone. Every structural decision required dialogue with the team — because knowledge of the technical domain of medical gases is specialized, and classification choices have real operational consequences.

Together with Sabrina Rosiglioni, COO of the company, we redesigned the catalog structure from within through structured work sessions. Every choice was stress-tested: does this category hold when the configurator needs to automatically select components? Is this code memorable for someone who's never seen it? Does this distinction make operational sense, or is it just historical?

  • New MACRO taxonomy in 12 categories based on the actual technical function of products in the system — not supplier origin
  • Shared and documented supplier abbreviation system — 24 main suppliers each assigned consistent 3-letter abbreviations
  • Explicit management of obsolete items with -OLD suffix — visible in the system but identified, not lost
  • Dedicated category for patient-bedside systems, built on language already in use by the team
  • PENDING sheet for items still to be classified — transparency on work status

Non-obvious decisions were documented explicitly — with the reasoning and rejected alternatives. A knowledge asset worth as much as the catalog itself: whoever enters the company two years from now will understand why the system is built that way.

FASE_03

Design

Build SKU coding: readable by anyone, without knowing internal conventions

The new SKU coding logic was designed around one precise principle: an item must be identifiable by someone who has never seen the old system. Each component of the code carries information — not just distinction.

The final system combines: functional category, supplier abbreviation, sequential number. The result is a code readable aloud, shareable by phone or email, memorable for sales staff. Not glamorous. Functional.

In parallel, the internal operational guide was built: a document that explains the classification logic, coding rules, obsolete management and the process for adding new items. Designed for someone who joins the company two years from now and has never seen the old system.

  • Coding logic with three-component structure (category + supplier + sequential)
  • Consistent naming rules for product families
  • Variant management with standardized suffixes
  • Operational guide for personnel onboarding and ongoing catalog maintenance
FASE_04

Deploy

From theoretical catalog to operational catalog: integration with management system data

A reorganized catalog without economic data is a half-tool. The Deploy phase involved integrating real management system data into the new structured catalog.

Each item in the new structure was enriched with: updated purchase price, current stock, unit of measure, relevant operational notes. The source is the company management system — data was not reworked, it was transferred into the correct structure.

In this phase, AI was also used in a targeted way to accelerate mechanical work while maintaining human judgment where necessary:

  • Inference of the correct SPEC from text descriptions for 104 items classified generically
  • Identification of substitution patterns in legacy codes and internal notes
  • Extraction of commercial category (component, spare part, kit, consumable) from descriptions where readable

Classification decisions, validation of economic data and handling of ambiguous cases remained human. In a field where a wrong item in a medical gas installation has real consequences, precision is non-negotiable.

FASE_05

Develop

The equipment configurator was the goal. The catalog was the prerequisite.

The project was born with a concrete objective in sight: Rosiglioni Impianti wants to build a digital configurator for designing medical gas equipment systems. A tool that allows sales staff — and in future customers — to select the correct components, generate coherent specifications, produce structured quotes.

That configurator couldn't have relied on the previous catalog. Every automatic selection would have been unreliable. Every generated quote would have required manual verification. The diagnosis and reorganization of the catalog were the prerequisite — not the accessory.

With the new data foundation ready, Rosiglioni now has the groundwork to build digital tools that actually work. The governed catalog is the zero point of the company's digital evolution.

Ongoing support continues: progressive enrichment of descriptions from PDF technical sheets from suppliers, expansion of data coverage, evolution of the operational guide with the team.

"Alessandro and his team are extraordinary. His ability to read the market and transform needs into opportunities is one of his greatest strengths. Thanks to Kredo and his leadership, we repositioned a historic company and gave a huge boost to online activities, expanding the network and acquiring international-level customers."
— Sabrina Rosiglioni, COO · Rosiglioni Impianti
Impact

What changed

Catalog reorganized into 12 functional categories with scalable logic — from supplier-based to function-based classification

New SKU coding readable by anyone, without needing to know the internal conventions accumulated over the years

Prices and stock integrated directly into the structured catalog — operational and product data in one system

Operational guide documented for staff onboarding and ongoing catalog maintenance

Data foundation ready to power the equipment configurator in development — the missing prerequisite for the digital leap

Team's tacit classification knowledge transformed into a documented system — knowledge asset that survives personnel changes

Transferable Lesson

What can be applied without KREDO

The Rosiglioni case is not isolated. It's a recurring pattern in almost every SME that has grown through accumulation. Operational knowledge lives in people, not systems. Catalogs and internal processes were built to respond to the urgency of the moment, not to last. Digitalization gets blocked not by lack of technology, but by lack of structure to build it on.

01
A catalog is a statement about who you are

A product catalog is not a database. It's how a company represents itself to itself — and to customers. When codes are chaotic and descriptions incomplete, it's not just an operational problem: it's a signal that a common language is missing about what the company sells and how it distinguishes one thing from another. Before communicating better externally, a company must be able to speak clearly internally.

02
Clean data is the prerequisite, not the accessory

Before building any digital tool — configurator, CRM, advanced ERP, automated quoting system — the base data must be clean, consistent, governed. Without that foundation, technology doesn't help: it amplifies chaos. Investment in data structure isn't glamorous. It's the work that makes everything else possible. Those who do it first gain months of advantage on digital transformation.

03
Documenting decisions is as valuable as making them

The non-obvious classification choices — why this category and not that, why this code and not another — have been documented with the reasoning and rejected alternatives. This knowledge asset is worth as much as the catalog itself. A company that knows why its system is built a certain way is far more resilient than one with a working system it can't explain. Documentation of reasoning is the true business continuity.

Topics: Product identity · B2B industrial brand · Operational identity

FAQ

What does 'product identity' mean for an industrial SME?

Product identity is how a company represents itself through its catalog: codes, descriptions, categories, classification logic. When these elements are inconsistent or incomplete, it's not just an operational problem — it's a signal that a shared language is missing about what the company sells and how it distinguishes one thing from another.

When does it make sense to reorganize a product catalog?

The critical moment is when you want to make the digital leap: configurators, advanced CRM, automated quoting systems. All these tools require clean, structured, governed base data. Without that foundation, technology amplifies chaos instead of reducing it.

How long does catalog reorganization take for an SME?

It depends on size and data quality. For a 5,000+ SKU catalog with distributed criticality patterns, a structured intervention typically requires 2-4 months of shared work with the internal team.

How does the catalog connect to brand work?

A well-structured catalog is the prerequisite for credible commercial communication. Before communicating better externally, a company must be able to speak clearly internally. The catalog is the starting point of that clarity.

Let's work together

Is your catalog a blocking problem?

Structured data work is often the invisible prerequisite for digitalization projects. If your product system has grown through accumulation and you're thinking about a digital leap, let's talk first.