--- title: 'Store Listing, Translations, and Presentation | Shopware Community Hub' description: >- Learn how to create a clear Store listing with descriptions, translations, images, setup information, and partner profile signals. canonical_url: >- https://hub.shopware.com/learn/unit/store-listing-translations-and-presentation --- - Create a Store listing that clearly communicates functionality and value. - Align descriptions, screenshots, and translations consistently. - Present setup and configuration information in an understandable way. - Design the listing as a professional entry point for merchants. # Store Listing, Translations, and Presentation The Store listing is often the first place where merchants evaluate an extension. Before they install it, they need to understand what the extension does, which problem it solves, how it is configured, and whether the partner behind it looks reliable. This makes the listing more than a marketing text. It is part of the product experience. A clear listing helps merchants make a good decision and helps Store Review understand whether the extension is presented accurately. In this unit, you will learn how to structure descriptions, translations, images, and partner information so that the Store listing becomes a trustworthy entry point for merchants. ## The Store Listing Sets Expectations The content and translations documentation describes several requirements for Store listings. The core idea is simple: the listing should accurately and clearly describe the extension and its use cases. A merchant should be able to answer these questions after reading the listing: - What does the extension do? - Which use case does it solve? - What does it change in the shop? - What must be configured before it works? - Are external services, fees, or special requirements involved? - Is the partner behind the extension trustworthy? The important mental model is this: > A Store listing should help merchants understand the product before they install it. If the listing is unclear, merchants may install the wrong extension, misunderstand the setup, or contact support for questions that should have been answered in the listing. ## Write Descriptions That Explain Value and Functionality Store descriptions should be concrete. They should not only say that the extension is "easy", "powerful", or "flexible". They should explain what the extension actually does and why that matters to the merchant. The short description is used as a teaser in overviews and can also appear as meta description. The long description gives more space to explain functionality, use cases, setup, and limitations. A useful description usually covers: - the merchant problem the extension solves - the main functionality - where the extension appears in the shop or administration - required setup or configuration - external services or accounts, if relevant - important limitations or scope boundaries This helps merchants compare extensions and reduces false expectations. ## Keep Translations Consistent If an extension is available in both the international Store and the German Store, descriptions should be consistent across languages. The documentation describes a 1:1 relationship between English and German content where both are used. This does not mean every sentence needs to sound mechanically translated. It means the meaning should match. The same features, limitations, setup steps, and claims should be present in each language. Consistency matters because merchants may switch languages, teams may compare listings, and Store Review needs to understand whether the extension is represented correctly. Before submission, partners should check: - Are all relevant languages complete? - Does each translation describe the same functionality? - Are setup steps and limitations present in each language? - Are screenshots language-specific where required? - Is English available as a fallback for settings and error messages? ## Use Images to Show the Extension in Context Images and screenshots should help merchants understand how the extension works. They should show the extension in use, not only decorate the listing. The content guidelines mention that screenshots should represent the extension's function and should not advertise unrelated services or other extensions. At least one storefront and one administration screenshot should show main features where relevant. Good screenshots can show: - the main storefront result - the administration configuration - setup or how-to details - mobile and desktop behavior - the feature in the context where merchants will use it Images should match the language of the Store listing. For example, English listing screenshots should use English-only UI content. How To - Add images and icons to extensions ## Explain Setup and Configuration Clearly A merchant should not need to guess how to activate or configure the extension after installation. The Store listing should explain what is needed before the extension works. This can include: - required credentials - required external accounts - sales-channel configuration - theme assignment - cache or build steps - setup limitations - known dependencies This is especially important for extensions that integrate external services or affect checkout, storefront behavior, or operational workflows. Clear setup information reduces support requests and makes the extension feel more professional. ## Connect the Listing With the Partner Profile The Store listing presents the extension. The partner profile presents the partner behind it. The Extension Partner profile documentation explains that the profile can show reviews, certifications, the number of extensions, and the partner badge. This gives merchants a transparent overview of the partner's services and extensions. For partners, this means the listing and profile should support each other. The listing should explain the extension. The profile should help merchants understand who provides and maintains it. Both should feel consistent: - same positioning - same quality level - same target audience - clear communication style - no misleading claims This consistency helps merchants trust the extension before they install it. ## Extension Details in the Account The Extension Partner Account documentation explains that extension details include master data, descriptions, images, categorization, sales options, marketing options, versions, and demo shops. For a Store listing, this means partners need more than a description. They also need to maintain the surrounding product information carefully. Important account fields can include: - display name - technical extension name - default language - availability for international or German Store - license - descriptions and images - categories - sales options - extension versions - demo shop information These fields shape how the extension appears and how merchants understand it. ## Example: Preparing a Listing for a Shipping Extension Imagine a partner prepares a Store listing for a shipping integration. A weak listing might say: > This extension connects your shop to our shipping platform. It is fast and easy to use. A stronger listing explains more clearly: - which shipping workflow the extension supports - which external shipping account is required - where merchants enter credentials - whether settings apply per sales channel - what the storefront or checkout experience looks like - which screenshots show setup and usage - whether additional fees or external contracts are involved The stronger listing helps merchants understand both value and requirements. It also helps avoid support requests caused by missing setup information. ## Common Pitfalls ### Writing Marketing Text Without Product Detail General claims do not help merchants decide whether the extension fits their use case. Describe functionality, setup, and scope clearly. ### Letting Translations Drift Apart If English and German descriptions describe different features or limitations, merchants and reviewers can receive conflicting information. ### Using Screenshots as Decoration Screenshots should show the extension in use. They should help merchants understand configuration, storefront behavior, or administration workflows. ### Hiding Setup Requirements External accounts, credentials, sales-channel settings, or additional services should be visible before installation. ### Treating the Partner Profile Separately The partner profile is part of the trust picture. A strong listing can still feel weak if the profile behind it is incomplete or unclear. ## Summary - A Store listing should clearly explain what the extension does, who it helps, and what setup is required. - Descriptions, screenshots, and translations should communicate the same functionality and value. - Images should show the extension in realistic Storefront and administration contexts. - Setup and configuration information should be understandable before installation. - The partner profile supports the listing by showing the partner behind the extension. Next, you will look at installation, uninstallation, and data cleanup so the extension lifecycle remains clear after the listing has convinced a merchant to install it.