Some shop work isn’t a one-off task — it repeats every night, on every order, or every Tuesday. Your vibe-code agent can turn these into scripts, cron jobs, and Shopware flows that run without you. Here are ten workflows worth handing over, with the phrases to start each one.

1. Nightly Supplier Price and Stock Sync

Most shops still get a supplier file, and typing it in by hand is a job that should not exist. The agent can write a script that downloads the file on schedule, matches product numbers, updates purchase prices and stock, and reports what changed. A dry-run mode and a log file turn “did it run?” into a non-question. Try: “Every night at 3am, fetch supplier.csv from the URL in my .env file, update stock and purchase price on matching product numbers, and email me a summary of everything that changed, including rows it couldn’t match.”

2. Paid Order to Shipment, Hands-Free

The gap between “customer paid” and “parcel shipped” is where goodwill leaks. The agent can hook the paid-transaction event or poll on a schedule, then create the shipment with your provider, write the tracking number back onto the order, and send your shipping-confirmation email template. Keeping the tracking code in an order custom field makes it visible to staff and customers alike. Try: “When an order’s transaction turns to paid, create the shipment with my DHL contract, save the tracking number in a custom field on the order, and send the customer my shipping-confirmation email.”

3. Low-Stock Early Warning

Running out of a bestseller costs more than any discount would have. A scheduled script can total the sellable stock per product — summing across variants where needed — and alert you below per-product thresholds before the zero hits. Grouping the report by supplier makes the reorder call obvious. Try: “Every morning, check stock for all active products and email me anything with fewer than 5 sellable units across its variants, grouped by supplier, so I can reorder before lunch.”

4. Auto-Cancel Orders That Never Pay

Unpaid orders hold stock and pollute your order list, and after 48 hours most will never convert. The agent can set this up as a scheduled job or a Flow Builder flow: find open, unpaid orders past the deadline, cancel them cleanly so the stock releases, and send a short, polite email. It should keep a list of everything it touched for your records. Try: “Cancel any order still unpaid after 48 hours: set the state to cancelled, confirm the stock was released, and send the customer a short note saying their reservation timed out.”

5. A Morning Sales Digest You Actually Read

You don’t need a dashboard open all day to know how yesterday went. A script can pull orders from the database — revenue, count, top products by quantity, refunds — and push a compact digest to email, Slack, or Telegram. Comparing against the same weekday last week keeps the numbers honest. Try: “Every day at 8am, send me yesterday’s numbers on Telegram: revenue, order count, top five products by quantity, and any refunds, compared with the same weekday last week.”

6. Newsletter Segment Export on Schedule

Your customer list is an asset, and exporting it manually is how it goes stale. The agent can build an export that runs on schedule: customers who opted in and ordered within the last year, deduplicated, dropped where your mail tool expects it, with hard bounces excluded. Try: “Every Sunday night, export customers with newsletter opt-in and at least one completed order in the past 12 months to a CSV on my SFTP, deduplicated, and exclude the addresses that bounced last time.”

7. Import New Products from a Supplier Feed

Supplier feeds bring new items faster than any human can type. The agent can parse the feed, create products through the Admin API with images uploaded into the media library, assign the right categories, and — the important part — leave everything inactive for your review. Twice a week is usually enough for a new-arrivals flow. Try: “Twice a week, import new products from my supplier’s feed: create them with images, put them in the right category, keep them inactive, and send me the list with anything that failed and why.”

8. Backups That Prove Themselves

A backup you’ve never restored is a hypothesis. The agent can schedule a proper one — database dump, media folder, your active theme and .env, encrypted and pushed to object storage — and then, monthly, restore the dump into a scratch database to prove it works. That restore test is the step everyone skips; automate it so it can’t be. Try: “Nightly at 2am, dump the database, tar the media folder and my active theme, encrypt the archive, push it to my S3 bucket keeping 14 days, and on the first of each month restore the latest dump into a scratch database and tell me it worked.”

9. Abandoned-Cart Follow-Up

Logged-in customers who leave a cart are warm leads, and Shopware can reach them without a marketing platform. The agent can combine a Flow Builder trigger with an email template so a reminder goes out a few hours after abandonment, excluding anyone who completed the order in the meantime. Keep the tone helpful, not needy. Try: “Three hours after a logged-in customer abandons a cart, send them my abandoned-cart email — and skip anyone who ordered in the meantime.”

10. A Nightly Invoice Run

Generating invoices one by one is fine at five orders a week and miserable at fifty. A scheduled job can find orders that reached paid status during the day, generate the invoice documents, email them to customers, and archive a copy in a dated folder. Your accountant will ask fewer questions. Try: “Every evening, find orders that reached paid today, generate their invoices, email each PDF to the customer, and store copies in /var/backups/invoices sorted by month.”

Each workflow starts as a chat message and ends as a scheduled job you can stop thinking about. Start yours with Shopware on OpenSysLab.