# How STIGA launched on seven marketplaces in four months > STIGA, Europe’s market leader in ride-on mowers, went live on seven marketplaces in five native languages in four months, with 500+ product pages generated, validated and published. The channels include Amazon in five countries, Allegro, Otto, Kaufland, ManoMano, Leroy Merlin and cDiscount. The sequential route, one country at a time, takes one to two years. Product data stayed in Akeneo, STIGA’s own PIM, with nothing replaced. ![A STIGA machine in a garden.](https://cdn.sanity.io/images/xd4hrbt2/production/f17c5962644bda093d12da9e166e2dfdcba8f217-1000x750.jpg) **Hero figure value:** 500+ **Hero figure label:** Product pages generated, validated and live **Industry:** Outdoor power equipment ## Key figures - 7 · marketplaces live - 500+ · PDPs generated, validated and live - 5 · native languages - 4 mo · to live, against one to two years ## Agents - Data Enrichment - Content Translation - Amazon Listing Optimizer - Leroy Merlin Listing Optimizer ## Overview For over ninety years STIGA has engineered powered garden equipment, and today it is Europe’s market leader in ride-on mowers, sold through specialist dealers, garden centres and mass retail. Garden equipment has always been an offline-first industry. Now the market is moving online: shoppers research long before they set foot in a store, and the marketplaces are opening the garden and outdoor category. STIGA saw the opening early and set an ambitious target, go live across every target marketplace, in every language, in parallel. ## The challenge The constraint was capacity, not ambition. Three things made the catalog genuinely hard. 1. **A deep catalog.** 500+ SKUs, each carrying technical specifications that had to be rendered accurately. 1. **A high average selling price.** The content could not just describe the products, it had to carry the value and justify the price. 1. **Proprietary technology.** Much of that value lived in engineering language, Vista, AGS, ePower, Multiclip, which says nothing to a marketplace shopper until someone rewrites it as a concrete benefit. On top of the catalog, time was binding. The traditional way to expand is sequential, one country and then the next, roughly six months each and one to two years in total. STIGA wanted the opposite. ### The setup before CommerceClarity Product data lived in Akeneo, a PIM designed to hold specifications and feed the trade channel, not to produce marketplace-ready content. Around it ran a manual, multi-vendor operation: source copy written in-house, translation tools for the other languages, a local marketing manager reviewing every product by hand, and spreadsheets holding the hand-offs together. The model worked. It did not scale. ## How we solved it, agents and engineers CommerceClarity replaced that chain with one agent platform, slotted into STIGA’s existing stack with no rip-and-replace of the PIM. The job: turn raw product data into channel-ready content, copy and structured attributes both, for Amazon in five countries, Allegro, Otto, Kaufland, ManoMano, Leroy Merlin and the direct eShop. ### The agents bring the scale Each product starts as a single canonical record, and a pipeline carries it from raw input to channel-ready content. 1. **Normalize** heterogeneous inputs into STIGA’s own taxonomy. 1. **Enrich** the missing attributes from STIGA’s internal sources. 1. **Apply the rules,** brand voice, channel constraints and compliance, so the output is correct by construction rather than corrected after. 1. **Translate and localize** natively, not word for word. 1. **Generate channel variants** in the exact shape each marketplace expects. 1. **Validate,** score the quality, run the automated checks, escalate what needs a human eye. STIGA started where the pain was sharpest, Channel Adaptation, then extended into Translation and Localization and Search Enrichment. ### The engineers co-build the outcome A CommerceClarity engineer works as an extension of STIGA’s team, the same person scoping, building and shipping. That flipped the operating model from decentralized and reactive to centralized and proactive. HQ owns the full content lifecycle and ships content already pre-validated and brand-ready. The agents bring the speed and the scale, the humans keep the governance over what actually goes live. ## Before and after Four months of work in a single view. - Time to launch · One to two years, country by country · Four months, in parallel - Marketplaces live · None · Seven - Product pages · Manual, per market · 500+ generated, validated, live - Languages · Generic translation tools, reviewed by hand · Five native localizations - Operating model · Internal team, tools, local managers, spreadsheets · One operator, centralized, end to end - Validation · Local managers, reactive · Automated checks, escalation only ## The people who own the rollout *In their words* - It feels like an extension of our team, like having their thinking embedded in an AI that works alongside us every day. · Asif Azam · Marketplace Manager, STIGA - Without CommerceClarity we would still be building the foundations. We are already building the next layer. · Gabriele Nofrini · Group E-Commerce Director, STIGA ## Proves area [Channels & Markets](/solutions/channels-markets) ## More customer stories - [Yeppon](/customers/yeppon) · How Yeppon got a 150,000 SKU catalog marketplace-ready, from its own store outward - [Cisalfa Sport](/customers/cisalfa-sport) · How Cisalfa cut the time to publish a product by eighty per cent ## 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 did STIGA achieve with CommerceClarity? Seven marketplaces live in five native languages in four months, with 500+ product pages generated, validated and published. Done the traditional way, country after country, the same expansion takes one to two years. ### Which marketplaces did STIGA launch on? Amazon in Italy, the United Kingdom, France, Germany and Poland, plus Allegro, Otto, Kaufland, ManoMano, Leroy Merlin and cDiscount, alongside STIGA’s own direct-to-consumer eShop. Each channel gets the product in the shape it requires, copy and structured attributes both. ### Did STIGA have to replace its PIM? No. Product data stayed in Akeneo, the PIM STIGA already ran for its dealer and retail business. The agents slot in around it: no rip-and-replace, and no second system for the team to keep in sync. ### Who did the work, agents or people? Both, and the split is the point. The agents carry the scale: normalize, enrich, apply the rules, translate, generate the channel variants, validate. A CommerceClarity engineer works as an extension of STIGA’s team, scoping and shipping inside the way STIGA already operates. People keep the governance over what goes live. ### Is the content translated or written for each market? Localized, not translated word for word. Five native localizations, with the proprietary technology names, Vista, AGS, ePower and Multiclip, rewritten as concrete benefits a marketplace shopper understands rather than left as engineering language. ### Are these figures approved by STIGA? Yes. Every figure and both quotes on this page are published with STIGA’s sign-off, and the two people quoted, Asif Azam and Gabriele Nofrini, are named with their consent. ## Entities - [STIGA](https://www.stiga.com) · Organization, about - [Channels & Markets](/solutions/channels-markets) · Thing, about - Asif Azam · Person, mentions - Gabriele Nofrini · Person, mentions - [Amazon](https://www.amazon.com) · Organization, mentions - [Leroy Merlin](https://www.leroymerlin.it) · Organization, mentions - [ManoMano](https://www.wikidata.org/wiki/Q48757787) · Organization, mentions - [Kaufland](https://en.wikipedia.org/wiki/Kaufland) · Organization, mentions - [Cdiscount](https://en.wikipedia.org/wiki/Cdiscount) · Organization, mentions - [Akeneo](https://www.akeneo.com) · Organization, mentions ## Sources - [Stiga Group](https://en.wikipedia.org/wiki/Stiga) · Wikipedia - [STIGA, garden machinery and outdoor power equipment](https://www.stiga.com) · STIGA Group - [Listing quality and product data requirements](https://sellercentral.amazon.com/help/hub/reference/GT4CDCFTFPWKMYNW) · Amazon Seller Central - [Akeneo, product information management](https://www.akeneo.com) · Akeneo --- Canonical: https://commerceclarity.com/customers/stiga Every page of this site is available as markdown: append `.md` to its path. Index: /llms.txt