Out of the box, Shopware looks like everyone else’s Shopware. The agent can change that — themes, plugins, custom fields, and the admin plumbing most owners never touch. Here are ten customizations worth asking for, roughly in order of ambition.

1. A Child Theme with Real Overrides

Changing the storefront properly means a theme that inherits from Shopware’s default and overrides only what you need — colors, fonts, layout moves — so updates don’t wipe your work. The agent can scaffold the theme plugin, write the SCSS overrides, adjust the Twig blocks for your header and buy button, compile the storefront assets, and activate it on your sales channel. The first compile takes a few minutes; after that, tweaks are quick to test. Try: “Create a child theme of the default storefront with my brand colors, a larger add-to-cart button, and my logo in the header — compile it and make it active on my storefront.”

2. A Custom Shopping Experiences Element

The layout editor ships with standard blocks, but marketing always wants one more: a trust-badge row, a delivery-estimate banner, a USP strip. A small plugin can register a new element with its own config fields, so your team drops it into any Shopping Experiences layout without calling you. The agent writes the element, the storefront renderer, and the admin configuration in one go. Try: “Build a plugin that adds a ‘trust badges’ element to the Shopping Experiences editor with editable text fields for three badges, and show me how to place it on a landing page.”

3. Custom Fields That People Actually See

A custom field nobody can see is just database decoration. The agent can add fields to orders or products and then surface them everywhere they matter: on the customer’s order-detail page in the storefront, as an editable column in the admin list, or inside emails through the template variables. Delivery date is the classic win for shops with scheduled shipments. Try: “Add a delivery-date field to orders, show it on the customer’s order page and as an editable column in the admin order list, and include it in my shipping email.”

4. Hide Prices from Guests

B2B and trade shops often want the catalog public but the prices private until login — good for SEO, useless to scrapers. The agent can set customer-group and rule-based visibility, then adjust the template so guests see a “log in to see prices” block instead of the buy box. Trade customers get their real prices through their assigned customer group. Try: “Hide prices and the buy button from guests and the default customer group, show a ‘log in to see trade prices’ notice instead, and keep category pages crawlable.”

5. Custom Sorting and Filters in Listings

Default sorting is name and price, but shoppers think in “newest” and “fits my machine.” A plugin can add sort options — newest first, bestselling — and filters that read your custom fields, so the spare-parts category filters by model fitment instead of color. Try: “Add a ‘newest first’ sort to category pages and a filter on my fits_models custom field for the spare-parts category only.”

6. Email Templates With a Sender That Passes Checks

Transactional mail is your highest-open-rate channel, and Shopware’s default templates read like placeholders. The agent can rewrite your order-confirmation and shipping emails in your voice for each language, wire up proper SMTP, and then check SPF, DKIM, and DMARC for your sending domain so the messages actually land in inboxes. Mail that lands in spam might as well not exist, so the DNS check comes before any template polishing. Try: “Rewrite my order-confirmation and shipping emails in plain, friendly German, send via the SMTP account in my .env, and verify SPF, DKIM, and DMARC all pass before my Friday campaign.”

7. Background Jobs That Survive a Reboot

Shopware leans on background workers — the message-queue consumer and the scheduled-task runner — for everything from flows to sitemaps. If they live in a fragile web cron, they silently stop. The agent can move both into systemd services with restart-on-failure, then verify that your Flow Builder jobs and the nightly sitemap actually ran. Try: “Move the queue consumer and scheduled-task runner into systemd services that start on boot, and confirm tonight that my flow and the sitemap job both ran.”

8. A Staging Clone You Can Break

Testing theme changes on production is how shops go down on a Friday. The agent can clone the database and media to staging.yourdomain with its own .env and APP_URL, lock it behind basic auth, and set noindex so search engines stay out. Break it freely, then promote what works. Try: “Clone my shop to staging.mydomain.tld with its own .env, protect it with basic auth, and make sure search engines can’t index it — that’s where I’ll test theme changes.”

9. A Second Language and Currency, Done Right

Going from German-only to German-plus-English is more than flipping a toggle: languages, currencies, country assignments, and payment methods all interact per sales channel. The agent can create the /en channel, install the English language content, assign UK shipping methods and GBP, and copy your category tree over — then check the storefront switcher actually works. You can keep prices in EUR until you’re ready to maintain a second price list. Try: “Set up an English storefront at /en with GBP, UK shipping methods, and payment methods that work there — copy my categories over and check the language switcher.”

10. A Performance Pass With Receipts

“It feels slow” deserves numbers. The agent can audit the stack — whether the HTTP cache is on, whether sessions sit in Redis, OPcache settings, oversized media, slow queries — apply the safe wins, and measure before and after on the homepage and a category page. Anything it changes, it should show you the difference. Try: “Audit my Shopware setup for speed: enable the HTTP cache if it’s off, move sessions to Redis, check OPcache, compress oversized product images, and give me before-and-after load times for the homepage and one category page.”

Start with one change, check the result, then ask for the next. And if you don’t have a server yet, Shopware on OpenSysLab ships with the agent already inside.