Medusa is a headless commerce platform: products, carts, orders, discounts, and regions, all served by APIs with an admin dashboard on top. On your server it runs as a Node.js app next to Postgres and Redis, and in the Open WebUI chat beside it sits your vibe-code agent. It can read Medusa’s files, run commands, query the database, and restart services — so here are ten everyday store jobs you can hand over instead of clicking through the admin.

1. Load a season of products from a spreadsheet

Typing forty products with sizes, colors, and prices into the admin is an afternoon you don’t have. The agent reads your CSV and creates the products with their variants, options, and prices in each currency you sell in. It also catches the mistakes that cost you sales later: duplicate SKUs, a variant missing a price, an option value that only exists on half the variants. You get a summary and a short problem list instead of a data-entry headache.

Try: “Here’s summer-products.csv with 36 products, each with size and color variants. Create them all with EUR prices for the EU region, put the shirts into a Summer Tees collection, skip and report any duplicate SKUs, and summarize what you created.”

2. Spin up a discount code that expires on its own

Discount codes look simple until you’re setting rules by hand: which region, which collection, one use per customer, an end date. Medusa’s discount conditions handle all of that, and the agent can set them precisely from one sentence — then read the rules back so there’s no surprise at checkout. Turning the code off later is another sentence, not a hunt through the admin.

Try: “Create code SUNNY20 for 20% off everything in the Summer Tees collection, EU region only, one use per customer, valid until June 30. Read back the exact rules before you save it.”

3. Find out why a product won’t show in the storefront

In a headless setup a product can exist and still be invisible. The usual suspects: it isn’t assigned to the sales channel the storefront queries, it has no price in the active region’s currency, its inventory is zero, or its category never made it into the navigation. Checking that by hand is five screens per product. The agent inspects all suspects in one pass, fixes the culprit, and tells you exactly what was wrong.

Try: “The ‘Sunset Hoodie’ shows fine in the admin but 404s in the store. Find out why — sales channel, prices, stock, categories — fix it, and tell me what the problem was.”

4. Reconcile inventory after a stocktake

Physical counts never match the system exactly. After a stocktake you need every discrepancy entered, and the big ones double-checked before anyone assumes shrinkage. The agent applies your counted levels per stock location, then hands you a delta report ordered by size so the odd ones stand out. What used to be an evening of clicking becomes a review of one table.

Try: “We just counted the warehouse — update these 18 SKUs to the counted levels in the Main stock location, and give me every adjustment bigger than 5 units so I can verify those first.”

5. Refund one line on an order

Refunds touch money, stock, and the order record, and the order of operations matters: refund through the payment provider, return the item to stock, then confirm the order totals. The agent finds the order by its number, walks that sequence, and shows you the amounts before the irreversible step. You approve the number, it does the clicking.

Try: “Order #1042 wants to return one item, the blue one in size M. Refund just that line through Stripe, return the unit to Main stock, and show me the new order total before you finish.”

6. Ask the store questions in plain English

“How did last week go?” is a SQL query against Medusa’s Postgres database: orders placed, revenue, average order value, top products by units and by money. The agent writes the query, runs it, and explains the result — no report builder, no CSV exports, no waiting for someone to pull the numbers.

Try: “How many orders did we get last week, what were the total revenue and average order value, and which five products earned the most? Break it down by region too.”

7. Open the store to a new country

A new region is more than a flag on a map. Medusa regions carry a currency, tax behavior, payment and fulfillment options, and their own shipping prices. The agent creates the region, converts your existing shipping prices at today’s rate, wires the payment provider, and enables it on the web sales channel — then proves the whole path with a test order.

Try: “Add Norway as its own region with NOK, tax-exclusive like the EU region, copy Standard and Express shipping over with prices converted from EUR at today’s rate, and enable it for the web sales channel.”

8. Raise prices across the catalog in one pass

When a supplier raises costs 8%, updating variant prices one by one is the kind of task that gets postponed until the margin disappears. The agent can apply a percentage or fixed increase across a collection or the whole catalog, per currency, with your rounding rule applied. It shows a before-and-after table for your most expensive products first, so you sanity-check the pattern before it commits.

Try: “Raise all prices in the Footwear collection by 6% and round up to the nearest .90, for EUR and GBP, then show me old and new prices for the ten most expensive products before applying it everywhere.”

9. Clean up a catalog that grew organically

Catalogs rot quietly: duplicate SKUs from old imports, products in no collection, variants with no inventory anywhere, tags used once and abandoned. Left alone, this pollutes search, reporting, and your own navigation. The agent audits the entire catalog and hands you a cleanup list grouped by problem type — and only touches data after you’ve seen it.

Try: “Audit the catalog: find duplicate or missing SKUs, variants with no inventory levels, products not in any collection, and tags used fewer than twice. Give me the cleanup list grouped by problem — don’t change anything yet.”

10. Health-check the money plumbing

Payments and tax depend on configuration most owners never look at: the Stripe keys and webhook secret in the environment file, the tax provider setting per region. When this rots, orders still arrive but money handling quietly degrades. The agent verifies the keys match what’s live in the Stripe dashboard, confirms a sample cart gets tax calculated for your main region, and restarts the backend if the config changed.

Try: “Run a payments health check: confirm the Stripe keys and webhook secret in .env match our live Stripe account, verify a test cart gets EU tax calculated, and restart the backend if you changed anything.”

None of these need a developer on retainer — they need one clear sentence and a few minutes of review. Hand the agent one job today and see how much admin time it hands back. See Medusa on OpenSysLab.