Medusa’s real pitch is that the codebase is yours: new data models, API routes, admin widgets, payment providers, and storefront changes are all normal work in the project. That’s exactly the kind of work a vibe-code agent does well, with you reviewing the result. Here are ten customizations worth asking for.

1. Add a Brand model linked to products

Medusa ships products, variants, collections, and categories — brands are yours to define. The agent scaffolds a module with a Brand data model, links it to products, exposes store API routes to fetch products by brand, and adds a brand picker to the admin product form. Your storefront can then render brand pages and filters from real data instead of tag hacks.

Try: “Create a Brand module with name, logo URL, and description, link it to products, add a store route that lists products by brand, and add a brand selector to the product page in the admin.”

2. Put your own fields on products

Every product line has attributes the standard model doesn’t know: care instructions, country of origin, shelf life. The agent extends the product with custom fields, makes them editable in the admin form, includes them in the store API response, and renders them on the storefront product page. Structured fields beat stuffing text into descriptions that search and filters can’t use.

Try: “Add ‘care instructions’ and ‘country of origin’ fields to products, make them editable in the admin, include them in the store product API, and show them on the storefront in a Care tab.”

3. Build a low-stock widget into the admin

The admin dashboard is yours to extend too. An admin widget can list every variant under its low-stock threshold across all locations, estimate days of stock left from the last 30 days of orders, and link each row straight to the product. Your standing warehouse question — what needs reordering? — gets answered on the screen people already open every morning.

Try: “Add an admin dashboard widget listing variants under my low-stock threshold in any stock location, estimating days of stock left from the last 30 days of sales, with a link on each row to edit that product.”

4. Expose a bestsellers endpoint

The starter storefront queries standard routes; your merchandising ideas deserve their own. A custom store route can compute top sellers over the last 30 days, cache the result for an hour so it stays fast, and return exactly the fields your homepage needs. The agent also shows you the small storefront change that starts using it.

Try: “Add a /store/bestsellers endpoint returning the top 20 products by units sold in the last 30 days, cache it for an hour, and swap the storefront homepage section from ‘New arrivals’ to use it.”

5. Make the starter storefront look like your brand

The Next.js starter storefront is deliberately plain — it’s a starting point, not a finished shop. The announcement bar, hero section, footer links, fonts, and colors all live in files the agent can edit and rebuild. Describe the outcome in plain words, review the result in the browser, and skip the design handoff entirely.

Try: “Add an announcement bar saying ‘Free shipping over €50 in the EU’, replace the homepage hero with our headline and a button into the Summer Tees collection, and update the footer with our contact email and a link to the returns policy page.”

6. Accept bank transfer as a payment method

Not every customer pays by card, and some markets still run on bank transfer. A custom payment provider can show your bank details and a per-order reference at checkout, create the payment as pending, and wait for staff to mark it captured in the admin — at which point the normal fulfillment flow takes over. No code you can’t read, and no card fees on those orders.

Try: “Add a manual bank-transfer payment option for the EU region that shows our IBAN and a per-order reference at checkout, keeps orders pending until we confirm receipt in the admin, and emails the customer the transfer details after ordering.”

7. Set up wholesale pricing without a second store

B2B on Medusa doesn’t need a separate shop. Customer groups plus price lists give wholesale accounts their own fixed prices per variant, and signed-in customers automatically see their group’s prices in the storefront and at checkout. The agent builds the group, generates the price list from your retail prices, and adds an application form that routes approved businesses into the group.

Try: “Create a Wholesale customer group with a price list at 30% below retail for every variant, make sure only that group sees those prices, and add an application form page that puts approved businesses into the group automatically.”

8. Harden the server around the store

A store handles money and customer emails, so the boring hardening matters: CORS restricted to your real origins, admin keys rotated and scoped, Stripe keys confirmed live rather than test, Postgres dumped nightly with uploaded images copied off the box. The agent audits each point, fixes what’s loose, and leaves you a note about what it changed and why.

Try: “Audit the server around Medusa: lock CORS to our storefront and admin domains, confirm we’re on live Stripe keys, set up nightly Postgres backups keeping seven days, and flag anything else that looks exposed.”

9. Seed a believable demo catalog

An empty store is hard to theme and impossible to demo. A seed script creates products with images, variants with stock, several regions with shipping options, past orders, and a sample discount code — everything a realistic shop needs. Useful for a staging copy, a redesign sandbox, or screenshots, and it runs again whenever you want a clean slate.

Try: “Write a seed script that creates 25 realistic products across two collections with placeholder images, three regions with shipping options, a few customers and past orders, and a 10% demo discount code.”

10. Upgrade search to something instant

The default product search does a basic job; a dedicated engine does it fast and tolerant of typos. Medusa supports Meilisearch and Algolia as search providers, and the agent can add one, index your products with the fields that matter — title, description, categories — and rewire the storefront search box to query it with instant results. On a growing catalog, this is the difference between found and abandoned.

Try: “Wire Meilisearch in as Medusa’s search provider, index all products and variants with title, description, and categories, and swap the storefront search box to query it with instant, typo-tolerant results.”

Customizations like these are how a headless platform earns its keep: small, precise changes instead of plugins fighting each other. Describe the outcome, review the diff, keep what works. See Medusa on OpenSysLab.