You have Saleor running on your own server: a GraphQL commerce engine, a React dashboard, a storefront, and PostgreSQL underneath. Next to it in Open WebUI sits your vibe-code agent — it can read Saleor’s files, run mutations against the GraphQL API, query the database directly, and restart services. Here are ten everyday shop jobs you can hand over instead of clicking through the dashboard.

1. Load a whole catalog from a spreadsheet

Adding one product through the dashboard is fine. Adding forty with variants, attributes, and stock is an afternoon of repetitive form-filling. The agent can read your CSV, map the columns to product types and attributes, write a script that posts the right mutations — products, variants, channel listings, stock — and run it against your API. It checks each response and reports what was created and what failed, instead of you discovering a half-finished import two days later.

Try: “Import this products.csv: each row is a coffee bag with SKU, name, a roast level attribute, a USD price for the default channel, and 50 units of stock in the main warehouse. Create anything that doesn’t exist and give me a summary.”

2. Launch a voucher for the weekend

Saleor vouchers can discount the whole checkout, a category, or specific products, with start and end dates and a usage limit. That’s five fields to get right, and a mistake is real money. Describe the promotion in plain language and the agent creates the voucher with the correct value type, sets the cap, sets the end date, and hands you the code. It can also schedule a small job that disables the voucher Monday morning so it never outlives the sale.

Try: “Create a code SUMMER15 for 15% off everything in the Apparel category, starting now, ending Sunday at midnight, usable at most 200 times. Show me the code when it’s live.”

3. Reprice a channel without a spreadsheet marathon

Prices in Saleor live on each variant’s channel listing, so a seasonal repricing touches hundreds of records. The agent writes a script that walks your categories, applies the rule you asked for, and updates the listings through the API. Have it print a before-and-after sample first — that one step catches a fat-fingered 10x price before your customers do.

Try: “Raise prices in the Outlet channel by 10%, rounded to the nearest .99, leave anything under $5 alone, and show me the ten biggest changes before you apply them.”

4. See stock across warehouses and rebalance

Once you run two warehouses, “do we have it?” stops being one number. The agent queries stock per variant and warehouse, flags anything under your threshold, and proposes moves — from the warehouse with surplus to the one with orders waiting. You approve the transfers; it does not move stock on its own unless you explicitly tell it to.

Try: “Show me every variant with fewer than 10 units across all warehouses, broken down by warehouse, and propose transfers from the main warehouse to the backup for anything the backup is missing.”

5. Clear the day’s order queue

Unfulfilled orders pile up during a busy week, and each one is a page of clicking. The agent lists orders by status, joins in their lines and shipping addresses, and produces a pick list per warehouse. When you confirm, it creates the fulfillments with the tracking numbers you give it. You still eyeball every order — you just stop retyping addresses.

Try: “List all unfulfilled orders from the last 48 hours grouped by warehouse, with SKUs and quantities for each pick list, and hold anything over $500 for my review.”

6. Answer “where is my order?”

Status emails are quick to answer if someone can look the order up. That someone is the agent. Give it a customer email or an order number and it walks the order’s events — placed, paid, fulfilled, shipped — pulls the tracking code, and drafts a reply. If the order was never paid, it says that instead of guessing.

Try: “Customer kara@example.com asked where her order is. Find her latest order, tell me its status, payment state, and tracking code, and draft a two-line reply I can send.”

7. Audit the catalog for drift

Catalogs rot quietly: draft products nobody published, SKUs duplicated by a bad import, items listed in no channel, empty categories. The agent runs the audit on demand and returns a fix list with links, so cleanup takes minutes instead of a weekend. Run it monthly and the storefront stays trustworthy.

Try: “Audit the catalog: products with no channel listing, duplicate SKUs, empty categories, and draft products older than 90 days. Give me the list grouped by problem type.”

8. Wire up a new shipping zone

A shipping zone ties countries to warehouses and shipping methods — three objects that must agree, which is exactly what goes wrong when you click through it tired. Tell the agent the countries, the serving warehouse, and the rate table, and it creates the zone, attaches the warehouse, adds the methods, then proves it works with a test checkout query.

Try: “Add a zone for Norway, Sweden, and Denmark served by our EU warehouse: flat €9 under 5 kg, €15 above, then verify a Danish test checkout can actually select it.”

9. Publish pages and fix the menus

Static pages — returns policy, about, contact — live in Saleor’s page manager, and menus decide where they appear. The agent can draft a page from a file you point it at, create it, and slot it into the navigation or footer menu in the right position. Next storefront visit, the link is there.

Try: “Create a Returns & Refunds page from /home/shop/policies/returns.md, publish it, and add it to the bottom of the footer menu on both channels.”

10. Open an outlet channel

Channels are Saleor’s way to sell the same catalog with different prices, currency, or availability — most shops eventually want an outlet. The agent creates the channel with its default country and currency, copies listings from your main channel at the discount you name, and reports what ended up live where. Excluding specific collections is one sentence.

Try: “Create a channel called Outlet in EUR for Germany, copy every product from the default channel at 30% off, skip the Limited collection, and show me the final count per collection.”

None of this needs a plugin or a fork — just the GraphQL API and an agent that knows where things live. Hand over one job, watch it work, then hand over the next. If you don’t have Saleor yet, start here: Saleor on OpenSysLab.