{"id":3361,"date":"2026-08-10T12:25:57","date_gmt":"2026-08-10T10:25:57","guid":{"rendered":"https:\/\/premsoft.de\/?p=3361"},"modified":"2026-08-11T11:54:23","modified_gmt":"2026-08-11T09:54:23","slug":"shopware-6-forms-what-the-standard-covers-and-where-it-runs-out","status":"publish","type":"post","link":"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/","title":{"rendered":"Shopware 6 Forms: What the Standard Covers \u2013 and Where It Runs Out"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A contact form is the first thing built in a new shop \u2013 and the last thing anyone thinks about. It sits in the Shopping Experiences, it works, it sends mail to&nbsp;<code>info@<\/code>. Two months later the picture looks different: sales receives complaints, support receives pricing requests, nobody knows whether last week&#8217;s inquiry was ever answered, and the job application with the attached CV never arrived at all, because the form does not accept files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is not a misconfiguration. That is the point where a standard form reaches its limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This article covers what Shopware 6 provides out of the box, where the friction shows up in daily operations \u2013 and how the typical cases can be solved.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_76 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#What_the_standard_Shopware_form_does_well\" >What the standard Shopware form does well<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#Point_1_everything_lands_in_one_inbox\" >Point 1: everything lands in one inbox<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#Point_2_the_mail_ends_up_in_spam_%E2%80%93_or_you_cannot_reply_to_it\" >Point 2: the mail ends up in spam \u2013 or you cannot reply to it<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#Point_3_no_record_no_history\" >Point 3: no record, no history<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#Forms_people_actually_complete\" >Forms people actually complete<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#The_case_that_pays_off_fastest_the_product_inquiry\" >The case that pays off fastest: the product inquiry<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#And_afterwards_the_form_as_a_trigger\" >And afterwards: the form as a trigger<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#A_note_on_data_protection\" >A note on data protection<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#Quick_checklist_for_your_form\" >Quick checklist for your form<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/premsoft.de\/en\/shopware-6-forms-what-the-standard-covers-and-where-it-runs-out\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_the_standard_Shopware_form_does_well\"><\/span>What the standard Shopware form does well<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s start fair: for the basic case, Shopware is well equipped. The&nbsp;<strong>Form<\/strong>&nbsp;CMS element lets you create a contact or newsletter form in the Shopping Experiences, drop it into a layout and define a recipient address \u2013 done. The mail template is translatable, captcha protection comes from the basic settings, and the output follows your theme.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For &#8220;get in touch&#8221; that is entirely sufficient. If you need nothing more, you need no plugin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The friction starts at three points \u2013 and it does so in almost every shop that handles inquiries seriously.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Point_1_everything_lands_in_one_inbox\"><\/span>Point 1: everything lands in one inbox<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One recipient per form means, in practice, one shared mailbox where service, sales and accounting all run together. A human does the sorting \u2013 every morning, by hand, by forwarding.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The usual workaround is to build several forms: one for service, one for sales, one for complaints. That only moves the work to the customer, who now has to guess which of the three forms fits their request. And guessing means guessing wrong.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The clean solution is one form with rules behind it.<\/strong>&nbsp;That is exactly what the&nbsp;<strong>mail routes<\/strong>&nbsp;in our form toolkit are for. A route is a recipient plus a condition:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Route &#8220;Service&#8221; \u2192&nbsp;<code>support@your-shop.com<\/code>, condition: select field&nbsp;<em>Subject<\/em>&nbsp;=&nbsp;<code>Service<\/code><\/li>\n\n\n\n<li>Route &#8220;Sales&#8221; \u2192&nbsp;<code>sales@your-shop.com<\/code>, condition: select field&nbsp;<em>Subject<\/em>&nbsp;=&nbsp;<code>Quote<\/code><\/li>\n\n\n\n<li>Route &#8220;Everything else&#8221; \u2192&nbsp;<code>info@your-shop.com<\/code>, no condition<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Every submission is evaluated against the routes; each matching route sends its mail. The available operators are&nbsp;<em>equals<\/em>,&nbsp;<em>not equals<\/em>,&nbsp;<em>contains<\/em>,&nbsp;<em>does not contain<\/em>,&nbsp;<em>empty<\/em>&nbsp;and&nbsp;<em>not empty<\/em>&nbsp;\u2013 combinable across several fields. Each route can carry CC and BCC recipients as well, for example to loop in a team lead on complaints.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The customer still fills in&nbsp;<em>one<\/em>&nbsp;form. The sorting happens before the inbox, not inside it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Point_2_the_mail_ends_up_in_spam_%E2%80%93_or_you_cannot_reply_to_it\"><\/span>Point 2: the mail ends up in spam \u2013 or you cannot reply to it<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A classic that costs a lot of time and is rarely understood.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To let staff simply hit &#8220;Reply&#8221; on a form notification, many solutions put the address the customer entered into the&nbsp;<strong>From<\/strong>&nbsp;header. Technically that means your server sends a mail claiming to come from&nbsp;<code>customer@gmail.com<\/code>. This is precisely the pattern SPF, DKIM and DMARC check for \u2013 and they classify it as spoofing. The result: the mail lands in the spam folder or is silently dropped. The inquiry is gone, and nobody notices.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The accepted standard for contact forms is different: the sender stays your shop address, and the customer&#8217;s address goes into the&nbsp;<strong>Reply-To<\/strong>&nbsp;header. Delivery is properly authenticated, and hitting &#8220;Reply&#8221; still addresses the customer directly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In our plugin you simply pick, per mail route, the form field that supplies the customer address. If it holds no valid address at submission time, the mail goes out without a Reply-To header instead of putting delivery at risk.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A detail nobody notices in day-to-day business \u2013 until you work out how many inquiries never arrived because of it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Point_3_no_record_no_history\"><\/span>Point 3: no record, no history<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As long as an inquiry exists only as an email, it is exactly as reliable as the mailbox holding it. It can land in spam, be deleted by accident, or sit untouched while a colleague is on holiday. And the question &#8220;how many product inquiries did we get last quarter?&#8221; simply cannot be answered.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is why, with our toolkit, every submission is stored in the Shopware database&nbsp;<strong>in addition to the mail<\/strong>&nbsp;and is visible in the Administration \u2013 with all submitted fields, language, sales channel and timestamp. Each submission carries a status (<em>new<\/em>,&nbsp;<em>read<\/em>,&nbsp;<em>answered<\/em>), so a team visibly works through the same list. For reporting or handover to a CRM there is a CSV export.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The mail stays the fast channel. The database is the memory.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Forms_people_actually_complete\"><\/span>Forms people actually complete<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">So far this has been about what happens after submission. What matters just as much is that people submit at all.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The most effective measure is not removing fields, but&nbsp;<strong>showing them only once they become relevant<\/strong>. Ticking &#8220;please call me back&#8221; reveals the phone field \u2013 until then it is out of everyone&#8217;s way. You configure this conditional field logic per field in the form editor, without a line of JavaScript.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For longer forms \u2013 applications, configuration requests, complaints \u2013 the&nbsp;<strong>multi-step view<\/strong>&nbsp;helps on top: the form is split into steps with a progress indicator. Instead of an intimidating wall of 20 fields, the visitor sees three manageable sections.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"530\" src=\"https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/multi-step-form-1-1024x530.png\" alt=\"\" class=\"wp-image-3380\" srcset=\"https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/multi-step-form-1-1024x530.png 1024w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/multi-step-form-1-300x155.png 300w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/multi-step-form-1-768x397.png 768w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/multi-step-form-1-1536x794.png 1536w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/multi-step-form-1.png 1843w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Then there are the building blocks that make a form readable: 14 input types (text, multiline, number, number range, dropdown, checkbox group, radio buttons, toggle, date picker, salutation, email, phone, file upload, privacy consent) and 9 structural elements (headings, dividers, spacers, rich text, explanations, plus notice boxes in four levels). Fields can be placed side by side in rows and bundled into groups \u2013 which makes a form look like part of the page rather than a foreign object.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The specialised field types pay off on mobile in particular: an email or phone field opens the matching keyboard on a smartphone \u2013 and is validated server-side, not just in the browser.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>File uploads<\/strong>&nbsp;work exactly as you would expect: CV, damage photo, print file. Which extensions are allowed is defined centrally in the plugin settings \u2013 the hint shown in the storefront and the server-side check come from the same source. Uploaded files are retrievable from the Administration only, never through a public URL.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"556\" src=\"https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-file-upload-1-1024x556.png\" alt=\"\" class=\"wp-image-3378\" srcset=\"https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-file-upload-1-1024x556.png 1024w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-file-upload-1-300x163.png 300w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-file-upload-1-768x417.png 768w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-file-upload-1-1536x834.png 1536w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-file-upload-1.png 1795w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Spam protection, by the way, stays yours: the form includes whichever captcha methods you have enabled in the Shopware basic settings. No second system, no additional third-party integration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_case_that_pays_off_fastest_the_product_inquiry\"><\/span>The case that pays off fastest: the product inquiry<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not every product can go into a cart. Products that need explanation, custom builds, tiered B2B pricing, &#8220;price on request&#8221; \u2013 in all of these the inquiry&nbsp;<em>is<\/em>&nbsp;the conversion point.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is what the&nbsp;<strong>product inquiry<\/strong>&nbsp;form type is for: a form that appears on the product page automatically, without you touching every layout in the Shopping Experiences. Where it appears is controlled by conditions \u2013 by&nbsp;<strong>customer group<\/strong>&nbsp;(B2B customers only), by&nbsp;<strong>sales channel<\/strong>, for individual&nbsp;<strong>products<\/strong>, or for an entire&nbsp;<strong>product stream<\/strong>, e.g. &#8220;every article in the custom-build category&#8221;.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"550\" src=\"https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-product-request-1-1024x550.png\" alt=\"\" class=\"wp-image-3375\" srcset=\"https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-product-request-1-1024x550.png 1024w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-product-request-1-300x161.png 300w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-product-request-1-768x412.png 768w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-product-request-1-1536x824.png 1536w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-product-request-1-2048x1099.png 2048w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The product context travels with the submission automatically: your sales team sees which article the inquiry is about instead of having to ask.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"And_afterwards_the_form_as_a_trigger\"><\/span>And afterwards: the form as a trigger<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A submission does not have to end with an email. On submit, the&nbsp;<strong>&#8220;Form submitted&#8221;<\/strong>&nbsp;event is dispatched in the Flow Builder \u2013 from there the process is yours:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>confirmation mail to the customer, in the language of their storefront (we ship the matching action, and a default flow is set up during installation)<\/li>\n\n\n\n<li>a notification into your team chat<\/li>\n\n\n\n<li>setting a customer tag to address prospects later in a targeted way<\/li>\n\n\n\n<li>handover to a CRM or ticket system via webhook<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Mail templates get access not only to the complete list of submitted fields, but also to individual fields directly \u2013 useful for a meaningful subject line: &#8220;New inquiry from Anna Sample about item XY&#8221; instead of &#8220;New form submission&#8221;.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"A_note_on_data_protection\"><\/span>A note on data protection<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Many shops solve more demanding forms with external services \u2013 Google Forms, Typeform and the like. That is quick to set up and, at the same time, means your customer data leaves the shop: you need a data processing agreement, a legal basis for the transfer and a paragraph in your privacy policy. For a contact form that is a remarkable amount of overhead.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With a solution inside Shopware, the data stays where your order and customer data already live. There is a dedicated field type for consent, linking to your privacy policy, and submissions are visible in the Administration \u2013 and therefore deletable in a targeted way when someone exercises their right to access or erasure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Quick_checklist_for_your_form\"><\/span>Quick checklist for your form<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>One form instead of three<\/strong>&nbsp;\u2013 let rules do the sorting, not the visitor.<\/li>\n\n\n\n<li><strong>Reply-To instead of a forged sender<\/strong>&nbsp;\u2013 otherwise inquiries end up in spam.<\/li>\n\n\n\n<li><strong>Reveal fields conditionally<\/strong>&nbsp;rather than dropping them.<\/li>\n\n\n\n<li><strong>Split long forms into steps.<\/strong><\/li>\n\n\n\n<li><strong>Store every submission<\/strong>, don&#8217;t just mail it.<\/li>\n\n\n\n<li><strong>Send a confirmation to the customer<\/strong>&nbsp;\u2013 it prevents the &#8220;did you get this?&#8221; follow-up.<\/li>\n\n\n\n<li><strong>Test on mobile<\/strong>, not just on desktop.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Shopware&#8217;s standard form is a solid starting point. But as soon as inquiries turn into a process \u2013 with responsibilities, records, attachments and reporting \u2013 it lacks the tools, and the difference is paid for in working hours every single day.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Our&nbsp;<strong>Form Toolkit for Shopware 6<\/strong>&nbsp;closes exactly that gap: 23 field and structural elements, conditional field logic, multi-step forms, mail routes with conditions, product inquiries on product pages, a submission inbox with status tracking and CSV export, plus full Flow Builder integration. Built for Shopware 6.7 and headless-ready, because all logic lives in dedicated routes.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"493\" src=\"https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-editor-1-1024x493.png\" alt=\"\" class=\"wp-image-3373\" srcset=\"https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-editor-1-1024x493.png 1024w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-editor-1-300x145.png 300w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-editor-1-768x370.png 768w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-editor-1-1536x740.png 1536w, https:\/\/premsoft.de\/wp-content\/uploads\/2026\/08\/form-editor-1-2048x987.png 2048w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/store.shopware.com\/en\/prems98244746964f\/form-toolkit.html\" data-type=\"link\" data-id=\"https:\/\/store.shopware.com\/en\/prems98244746964f\/form-toolkit.html\">View extension in the store<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A contact form is the first thing built in a new shop \u2013 and the last thing anyone thinks about. It sits in the Shopping Experiences, it works, it sends mail to&nbsp;info@. Two months later the picture looks different: sales receives complaints, support receives pricing requests, nobody knows whether last week&#8217;s inquiry was ever answered, [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[79],"tags":[],"class_list":["post-3361","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/posts\/3361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/comments?post=3361"}],"version-history":[{"count":2,"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/posts\/3361\/revisions"}],"predecessor-version":[{"id":3382,"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/posts\/3361\/revisions\/3382"}],"wp:attachment":[{"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/media?parent=3361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/categories?post=3361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/premsoft.de\/en\/wp-json\/wp\/v2\/tags?post=3361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}