One-off jobs are useful, but the real payoff is work that happens while you’re doing something else. Medusa has the hooks built in: events like order.placed, scheduled jobs, and a notification module for sending email. Here are ten automations worth wiring up, each small enough to review in a single sitting.

1. Ping the team the moment an order lands

Medusa fires an order.placed event for every completed checkout, and a subscriber can react within seconds. The agent writes one that posts to your Slack or Discord channel — order number, total, country, items — so whoever handles fulfillment knows before the customer refreshes their inbox. Add a confirmation email through the notification module and the “did my order work?” worry disappears on both sides.

Try: “When an order is placed, post to our #sales Slack channel with the order number, total, customer country, and items, and email the customer a confirmation listing what they bought and our 3-day delivery window.”

2. Get yesterday’s sales in your inbox every morning

A scheduled job can query the database on a timer and email you the numbers before you sit down: orders, revenue, average order value, top products, failed payments. Compared against the same weekday last week, you get the trend and the absolute numbers in one glance. Building this by hand means a script, a mailer, and a cron entry — an afternoon of work for the agent, a permanent habit for you.

Try: “Every morning at 7, email me yesterday’s order count, revenue, average order value, the five top products by revenue, and any failed payment attempts, each compared with the same weekday last week.”

3. Promote repeat customers to VIP automatically

Customer groups power price lists and promotions, but moving people between groups by hand doesn’t scale. A workflow on order.placed can total each registered customer’s lifetime spend and, past your threshold, add them to the VIP group — the same group your VIP price list already targets. The customer gets a thank-you email; you get a loyalty program without signing up with a loyalty vendor.

Try: “Each time an order is placed, if the customer’s lifetime spend crosses $1,000, add them to the VIP customer group and email a thank-you with their early-access code. Skip guest checkouts.”

4. Never run out of stock quietly

Stockouts cost sales you never see, because the product page just quietly says sold out. A daily scheduled job can compare every variant’s level in your main stock location against the thresholds you set, then email a restock list sorted by urgency. Include recent sales velocity and the same list doubles as a purchasing priority order.

Try: “Every morning, check all variants in the Main stock location against these reorder thresholds and email me a restock list sorted by how fast each item sold over the last 30 days.”

5. Tell shoppers the moment something is back

A shopper who wanted the sold-out item is the easiest sale you will ever get — if you reach them. The agent adds a notify-me form to out-of-stock product pages that stores the shopper’s email against the variant, plus a subscriber that watches inventory and emails the list the moment levels come back above zero. One message per person, with a direct link to buy.

Try: “Add a ‘notify me when available’ box to out-of-stock product pages, store each email against the variant, and when inventory goes above zero, email everyone on that variant’s list once with a link to the product.”

6. Recover abandoned carts before they go cold

Every store has carts that stall at the payment step. Medusa keeps carts around, so a scheduled job can find ones idle for more than 24 hours, with an email attached and a value above your threshold, then send a single reminder with a time-boxed discount code. The agent wires the job, the email template, and the code creation — and caps it at one email per cart so you never nag.

Try: “Every hour, find carts idle over 24 hours that have an email and over $50 of items, and send one reminder email with a 10% code that expires in 48 hours. Maximum one email per cart.”

7. Bridge Medusa to the rest of your stack

Finance lives in a spreadsheet, marketing lives in n8n, and nobody wants another admin tab. A subscriber can forward order events to any webhook — n8n, Make, Zapier — or append straight into a Google Sheet, mapping order fields to columns once. From then on, every order lands where your team actually looks, with no manual exports and nothing copied twice.

Try: “Forward every placed order to our n8n webhook with order number, email, country, and line items, and also append one row per order to the finance team’s ‘Orders 2026’ Google Sheet. Retry on failure so nothing is dropped.”

8. Ask for reviews when the package actually arrives

Review requests sent at fulfillment feel random; sent at arrival they feel timely. A subscriber on order.fulfilled records the date, and a daily job emails customers seven days later, naming the products they bought with links to those product pages. One reminder three days after that, then silence. Polite, specific, and it runs while you sleep.

Try: “Seven days after an order is marked fulfilled, email the customer asking for a review, name the products they bought with links to each product page, and send one reminder three days later, then stop.”

9. Auto-fulfill orders that need no warehouse

Digital goods and gift cards don’t need picking, packing, or a courier. A workflow can detect orders containing only items from your digital collection, capture the payment if it hasn’t been, create the fulfillment immediately, and email the customer their download links or codes. Mixed orders stay manual; fully digital ones clear themselves off your plate.

Try: “For orders containing only items from the Digital collection, capture the payment, create the fulfillment automatically, and email the customer a download link for each item. Leave mixed orders for manual fulfillment.”

10. Put a watchdog on returns

Returns are where customer trust is won or lost, and a return request sitting unrefunded for a week is a support ticket and a bad review in waiting. A daily job can list open returns past your SLA — say 48 hours — with the order number, items, and age, and email the list to your support inbox every morning. Nothing falls through a crack you can’t see.

Try: “Every morning, email support@ourstore.com a list of return requests older than 48 hours that aren’t refunded or resolved, with order number, items, and how long each has waited. Skip the ones waiting on the customer.”

Each of these is a small, reviewable change: a subscriber file, a scheduled job, an email template. The agent builds them, shows you what it wrote, and you decide what keeps running. See Medusa on OpenSysLab.