# How Cisalfa cut the time to publish a product by eighty per cent > Cisalfa Sport, the largest sports retail chain in Italy with 240+ stores and 250+ third-party brands, cut the time to publish a new product by eighty per cent, from weeks to hours. The bottleneck was supplier data: attributes, descriptions and images missing, every supplier in a different format, and the team chasing the gaps by email before anything could go live. The agents normalize whatever arrives and fill the gaps, inside the process Cisalfa already ran. ![A Cisalfa Sport store.](https://cdn.sanity.io/images/xd4hrbt2/production/0c616d65d16e53545599d30c95b7c6a987a3a86b-1600x1067.jpg) **Hero figure value:** 80% **Hero figure label:** Less time to publish a new product **Industry:** Sports retail ## Key figures - 80% · less time to publish a new product - Hours · from supplier file to live, not weeks - 240+ · stores, and the online business on the same data ## Agents - Data Enrichment ## Overview Cisalfa Sport is the largest sports retail chain in Italy, 240+ stores across eighteen regions and an online business that has to carry the same assortment. Its catalog is 250+ third-party brands, and it turns over with every season. As the ecommerce operation grew, the constraint stopped being the assortment and became the speed of getting it live. Cisalfa came to us to take the manual exchange with suppliers out of that process. ## The challenge Product onboarding ran on what suppliers sent, and what they sent was uneven: attributes missing, descriptions missing, images missing, formats different for every one of them. - Chasing the missing details by hand held publication up, supplier by supplier. - The team reviewed, corrected and enriched every record before it could go out. - New arrivals landed too late to catch the demand peak they were bought for. ## How we solved it The agents took the supplier file as it arrived and turned it into a publishable product, inside the process Cisalfa already ran. 1. **Normalize.** Whatever the supplier sends, spreadsheet, code list or images, becomes structured product data on Cisalfa’s own taxonomy. 1. **Enrich.** The missing attributes, specifications and descriptions get filled, so the record arrives publication-ready rather than half-written. 1. **Fit the existing workflow.** No new system for the team to learn and no integration project to run first. ## What changed Publication went from weeks to hours, an eighty per cent cut, and the team stopped writing product data. It reviews what the agents produce and decides what ships, which is the part of the job that needed people in the first place. ## Before and after The same catalog, the same suppliers, a different operation. - Time to publish · Weeks, waiting on supplier replies · Hours, eighty per cent faster - Supplier data · Whatever format arrived, chased by email · Normalized on arrival, whatever the format - The team’s job · Writing and correcting every record · Reviewing output and deciding what ships - New arrivals · Live after the demand peak · Live in time for it ## The team that stopped typing *In their words* - The team validates output now. They have stopped writing. · Alberto Colnaghi · Cisalfa Sport - Now we find out whether your output answers for the German market too, at the quality level we reached in Italy. · Francesco Gasca · Cisalfa Sport ## Proves area [Catalog Foundation](/solutions/catalog-foundation) ## More customer stories - [STIGA](/customers/stiga) · How STIGA launched on seven marketplaces in four months - [Yeppon](/customers/yeppon) · How Yeppon got a 150,000 SKU catalog marketplace-ready, from its own store outward ## See what the agents do with your catalog Bring one messy feed, or the backlog of products you never got to. We will show you the rest. [Book a demo](/book-a-demo) ## Questions ### What changed for Cisalfa Sport? The time to publish a new product fell by eighty per cent, from weeks to hours, and the team stopped writing product data. It reviews what the agents produce and decides what ships. ### What was actually slowing publication down? Supplier data. Attributes, descriptions and images were missing or inconsistent, and every supplier sent a different format. Getting the gaps filled meant chasing suppliers by email, so new arrivals often went live after the demand peak they had been bought for. ### How does the automation handle files that all look different? It normalizes first. Whatever the supplier sends, a spreadsheet, a code list or a folder of images, becomes structured product data on Cisalfa’s own taxonomy. Then the missing attributes, specifications and descriptions are filled, so the record arrives publication-ready instead of half written. ### Did Cisalfa have to change its systems? No. The automation fits the process Cisalfa already ran, with no new system for the team to learn and no integration project to finish first. ### How big is the catalog behind this? Cisalfa Sport runs 240+ stores across eighteen regions with around 5,700 employees, and sells 250+ third-party brands online and in store. The assortment turns over every season, which is why publication speed is the constraint rather than assortment size. ## Entities - [Cisalfa Sport](https://www.cisalfasport.it) · Organization, about - [Catalog Foundation](/solutions/catalog-foundation) · Thing, about - Alberto Colnaghi · Person, mentions - Francesco Gasca · Person, mentions - [SportScheck](https://www.sportscheck.com) · Organization, mentions ## Sources - [Cisalfa Sport](https://www.cisalfasport.it) · Cisalfa Sport - [Product data specification](https://support.google.com/merchants/answer/7052112) · Google Merchant Center - [Product](https://schema.org/Product) · schema.org - [Product structured data markup](https://developers.google.com/search/docs/appearance/structured-data/product) · Google Search Central --- Canonical: https://commerceclarity.com/customers/cisalfa-sport Every page of this site is available as markdown: append `.md` to its path. Index: /llms.txt