Skip to content

Shopware 6 - Product Feedback & Ideas

Interested in a direct exchange?Are you interested in a direct exchange about your business case? We would be happy to learn more about your daily business and its requirements. For this purpose, we offer you the opportunity to discuss this directly with our product management team. Book your appointment right here:Book an appointmentDo you have a specific request that you would like to tell us about? Then the following feedback portal is the right place for you.

This is the space where you can share your ideas and feedback about Shopware 6.

How it works
  • Connect your Shopware Account or register with your email
  • Use the search or choose a category for your idea to check if it has been submitted already
  • Upvote existing ideas, as opposed to creating multiple similar requests. Comment an idea to share extra details.
  • If you create a new idea: Be clear with your idea; provide examples or even screenshots
  • The more activity and votes an idea has, the higher the chance it will be implemented
Notes

Shopware 6 - Product Feedback & Ideas

Categories

What idea would you like to share with us?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

3 results found

  1. Custom fields from apps cannot be repositioned.

    Custom fields from apps cannot be repositioned. This means that, for example, such fields end up in product locations that are potentially completely unsuitable and irrelevant.

    According to the software vendor, this is due to the Shopware core. This should be adjusted.

    Feedback from the manufacturer:
    "If you create custom fields within an app, these cannot be edited in the Shopware admin panel. This is a limitation of Shopware, and unfortunately, we cannot change it. Within an app, custom fields are only 'defined' in an XML file. No programming is done here to determine how and where the field is…

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Checkout gateway mechanism for calculating delivery charges

    Die vorhandenen Commands des Checkout Gateways (https://developer.shopware.com/docs/guides/plugins/apps/gateways/checkout/command-reference.html) lassen es nicht zu, die Versandkosten des Warenkorbs zu berechnen oder zu setzen.
    Dies wäre aber wünschenswert, um z.B. kompliziertere Versandkostenberechnungen vom ERP erledigen zu lassen.

    –

    The existing commands in the Checkout Gateway (https://developer.shopware.com/docs/guides/plugins/apps/gateways/checkout/command-reference.html) do not allow the shipping costs for the shopping basket to be calculated or set.
    However, this would be desirable, for example, to allow the ERP system to handle more complex shipping cost calculations.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback


    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.


    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

  3. Standardize shortName for Categories to ensure App and Headless stability

    Shopware provides a shortName for SalesChannels to enable environment-agnostic identification, yet this primitive is missing for Categories. This inconsistency forces App developers and Headless integrators to rely on volatile SEO URLs or environment-specific UUIDs to identify "Page Types" (e.g., Home, Support, Landing Page).

    By extending shortName to the Category entity, Shopware would provide a stable, indexed, and semantic developer contract. This eliminates the need for redundant repository searches or brittle Custom Field lookups, which currently penalize performance and complicate CI/CD pipelines. Standardizing this across core entities ensures that external systems can resolve both "Shop Context" and "Location Context" using the…

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback


    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.


    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

  • Don't see your idea?