> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mercurjs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use cases

> Two ways to run Mercur: as the whole marketplace, with its own storefront, admin and vendor panels, or as the marketplace layer inside a store you already run, selling seller offers next to your own products.

Mercur fits two kinds of business. Pick the one that matches yours; the modules underneath are the same.

**Marketplace platform**

You are building a marketplace from scratch, or replacing one. Mercur runs everything: the storefront, the operator admin, the vendor panel sellers log into, and the backend that splits every checkout into one order per seller, computes commissions and pays sellers out.

![Three Mercur surfaces stacked back to front: the admin Sellers list, the vendor panel's Offers table for ACME, and the storefront product page for the Linen shirt listing the offers a shopper can buy.](https://mintcdn.com/mercur/MTLsNFocqKlAvczN/images/figures/use-case-platform-light.svg?fit=max\&auto=format\&n=MTLsNFocqKlAvczN\&q=85\&s=90eab7e2774ac8c66e656385e179d7ba)

**Pick this when**

* You don't have a store yet, or you want the marketplace to be the product
* Sellers should get their own panel: offers, orders, fulfillment, payouts
* You want one shared catalog that every seller lists against

**What you get**

| Surface | Who uses it | Package |
| - | - | - |
| Storefront | Shoppers | Any framework on the Store API, or the starter storefront |
| Admin panel | Operators | `@mercurjs/admin` |
| Vendor panel | Sellers | `@mercurjs/vendor` |
| Backend | Everyone | `@mercurjs/core` on Medusa |

> **[Install Mercur](/learn/introduction)**
>
> Create a marketplace project and run it locally.

> **[Architecture](/learn/architecture)**
>
> How the panels, the API and the modules fit together.

**Marketplace inside your store**

You already sell your own products on a platform like Magento. You want third-party sellers next to them, in the same product page and the same checkout, without moving your catalog or your payments. Your store stays the storefront; Mercur becomes the marketplace layer behind it.

![A product page in your own store lists your warehouse next to two seller offers from ACME and GLOBEX. A wire leads from the seller rows to a Mercur order group with one order per seller; your own line never leaves your store.](https://mintcdn.com/mercur/MTLsNFocqKlAvczN/images/figures/use-case-hybrid-light.svg?fit=max\&auto=format\&n=MTLsNFocqKlAvczN\&q=85\&s=8438a6f3faa34d31d4829ef3417f07e3)

**Pick this when**

* Your store, checkout and payment provider are already live and should stay
* You sell first-party stock and want sellers to compete on the same SKUs
* Sellers need a panel, but shoppers should never notice a second system

**Who runs what**

| Concern | Your store | Mercur |
| - | - | - |
| Catalog, prices, stock of your own products | ✔ | |
| Storefront, cart, checkout, payment capture | ✔ | |
| Sellers, their offers, their panel | | ✔ |
| One order per seller, commissions, payouts | | ✔ |

> **[Magento 2 integration](/resources/integrations/magento2)**
>
> Install the connector and run a mixed first-party and seller order.

> **[Order Group module](/platform/order-group/overview)**
>
> How one checkout becomes one order per seller.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.