@mercurjs/docs 2.2.1 → 2.3.0-canary.1

package/content/references/api/admin/order-groups/list-order-groups.mdx

@@ -4,7 +4,7 @@ api: "GET /admin/order-groups"
 description: "Retrieve a paginated list of order groups."
 ---
 
-Returns order groups — the customer-facing wrappers around per-seller orders created from a multi-seller cart.
+Returns order groups, the customer-facing wrappers around per-seller orders created from a multi-seller cart.
 
 <Note>
   Filtering by `seller_id` narrows results to order groups that contain at

package/content/references/api/admin/product-attributes/create-attribute-value.mdx

@@ -4,7 +4,7 @@ api: "POST /admin/product-attributes/{id}/values"
 description: "Create or update values on a product attribute."
 ---
 
-Upserts the given values on the attribute — items with an `id` update an existing value, items without one create a new value.
+Upserts the given values on the attribute. Items with an `id` update an existing value, items without one create a new value.
 
 ## Path parameters
 
@@ -13,7 +13,7 @@ Upserts the given values on the attribute — items with an `id` update an exist
 ## Body parameters
 
 <ParamField body="values" type="object[]" required>
-  Values to create or update — one of two shapes per item.
+  Values to create or update, one of two shapes per item.
   <Expandable title="update existing value (by id)">
     <ParamField body="id" type="string" required>The value's ID.</ParamField>
     <ParamField body="name" type="string">Value name.</ParamField>

package/content/references/api/admin/product-attributes/create-product-attribute.mdx

@@ -7,7 +7,7 @@ description: "Create a catalog product attribute."
 Creates a shared attribute that products across the catalog can use.
 
 <Note>
-`is_variant_axis` is only valid for `multi_select` attributes — axis attributes provide the value sets that variants are generated from.
+`is_variant_axis` is only valid for `multi_select` attributes. Axis attributes provide the value sets that variants are generated from.
 </Note>
 
 ## Body parameters

package/content/references/api/admin/product-attributes/update-product-attribute.mdx

@@ -7,7 +7,7 @@ description: "Update a catalog product attribute."
 Updates the attribute's details; only the provided fields are changed.
 
 <Note>
-`type` is immutable — sending a `type` different from the attribute's current type returns an error.
+`type` is immutable. Sending a `type` different from the attribute's current type returns an error.
 </Note>
 
 ## Path parameters

package/content/references/api/admin/product-changes/confirm-product-change.mdx

@@ -18,7 +18,7 @@ Applies the pending change set to the product and marks the change as confirmed.
 
 <ResponseField name="id" type="string">The confirmed product change's ID.</ResponseField>
 <ResponseField name="object" type="string">Always `product_change`.</ResponseField>
-<ResponseField name="deleted" type="boolean">Always `true` — the change is no longer pending.</ResponseField>
+<ResponseField name="deleted" type="boolean">Always `true`. The change is no longer pending.</ResponseField>
 
 <RequestExample>
 ```bash cURL

package/content/references/api/admin/products/batch-product-attributes.mdx

@@ -13,7 +13,7 @@ Applies attribute changes to the product in the order `remove` → `add` → `up
 ## Body parameters
 
 <ParamField body="add" type="object[]">
-  Attributes to attach — one of two shapes per item.
+  Attributes to attach, one of two shapes per item.
   <Expandable title="existing attribute (by id)">
     <ParamField body="id" type="string" required>ID of an existing catalog attribute.</ParamField>
     <ParamField body="value_ids" type="string[]">IDs of attribute values to select.</ParamField>

package/content/references/api/admin/products/create-product.mdx

@@ -50,7 +50,7 @@ Pass `seller_ids` to set which sellers may sell the product. The `attributes` ar
   </Expandable>
 </ParamField>
 <ParamField body="attributes" type="object[]">
-  Unified attribute input — one of two shapes per item.
+  Unified attribute input, one of two shapes per item.
   <Expandable title="existing attribute (by id)">
     <ParamField body="id" type="string" required>ID of an existing catalog attribute.</ParamField>
     <ParamField body="value_ids" type="string[]">IDs of attribute values to select.</ParamField>

package/content/references/api/admin/products/preview-product.mdx

@@ -7,7 +7,7 @@ description: "Retrieve the pending change set for a product."
 Returns the product's pending change request with its individual change actions, or `null` if no change is pending.
 
 <Note>
-The response contains the pending `product_change` record and its `actions` — the raw edits awaiting review — not a merged product payload.
+The response contains the pending `product_change` record and its `actions` (the raw edits awaiting review), not a merged product payload.
 </Note>
 
 ## Path parameters

package/content/references/api/admin.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Admin API"
-description: "Operator routes under /admin/* — sellers, commissions, payouts, master catalog, and marketplace-wide orders."
+description: "Operator routes under /admin/* for sellers, commissions, payouts, master catalog, and marketplace-wide orders."
 ---
 
-The Admin API is the marketplace operator's surface. It extends Medusa's standard admin routes with the marketplace domains below; everything else (regions, currencies, users, API keys, …) comes from Medusa core unchanged.
+The Admin API is the marketplace operator's surface.
 
-Authentication and shared conventions are covered in [API conventions](/rc/references/api/conventions).
+It extends Medusa's standard admin routes with the marketplace domains below. Everything else, such as regions, currencies, users, or API keys, comes from Medusa core unchanged. Authentication and shared conventions are covered in [API conventions](/rc/references/api/conventions).
 
 ## Sellers
 
@@ -52,7 +52,7 @@ Authentication and shared conventions are covered in [API conventions](/rc/refer
 
 ## Products (master catalog)
 
-Products are shared catalog records — see the [master products model](/rc/references/modules/product-edit#the-master-products-model).
+Products are shared catalog records. See [master products](/platform/catalog/concepts/master-products).
 
 | Method | Path | Purpose |
 | --- | --- | --- |
@@ -130,5 +130,4 @@ Mercur extends the Medusa RMA routes so they respect seller boundaries:
 
 <CardGroup cols={2}>
   <Card title="Vendor API" href="/rc/references/api/vendor" />
-  <Card title="API Client" href="/rc/tools/api-client" />
 </CardGroup>

package/content/references/api/conventions.mdx

@@ -1,9 +1,11 @@
 ---
 title: "API conventions"
-description: "Authentication, seller scoping, pagination, field selection, and webhooks — shared by every Mercur API surface."
+description: "Authentication, seller scoping, pagination, field selection, and webhooks shared by every Mercur API surface."
 ---
 
-Mercur exposes three HTTP surfaces on the Medusa server. They share the same conventions for authentication, pagination, and field selection.
+Every Mercur API surface follows the same rules for authentication, pagination, and field selection.
+
+Mercur exposes three HTTP surfaces on the Medusa server. They share the conventions below, so once you learn one surface the others behave the same way.
 
 | Surface | Base path | Audience | Authentication |
 | --- | --- | --- | --- |
@@ -11,27 +13,27 @@ Mercur exposes three HTTP surfaces on the Medusa server. They share the same con
 | [Vendor API](/rc/references/api/vendor) | `/vendor/*` | Sellers | Member auth + seller scoping (below) |
 | [Store API](/rc/references/api/store) | `/store/*` | Storefront | Mostly public; customer auth where noted |
 
-All requests and responses are JSON. The recommended way to call these APIs is the typed [`@mercurjs/client`](/rc/tools/api-client) — every route below maps 1:1 to a client call.
+All requests and responses are JSON. Call these APIs with the typed `@mercurjs/client`. Every route below maps 1:1 to a client call.
 
 ## Authentication
 
 ### Admin
 
-Admin routes use standard Medusa admin authentication — log in via `/auth/user/emailpass`, then send the session cookie or a `Authorization: Bearer <token>` header.
+Admin routes use standard Medusa admin authentication. Log in via `/auth/user/emailpass`, then send the session cookie or an `Authorization: Bearer <token>` header.
 
 ### Vendor
 
 Vendor routes authenticate the **member** actor (`/auth/member/emailpass` to obtain a token) and are additionally scoped to a single seller:
 
-1. The request must carry an `x-seller-id` header (or a seller selected in the session via `POST /vendor/sellers/select`).
-2. Middleware verifies the authenticated member belongs to that seller and populates the request's seller context — every query and mutation on the surface is automatically filtered to that seller.
+1. The request must carry an `x-seller-id` header, or a seller selected in the session via `POST /vendor/sellers/select`.
+2. Middleware verifies the authenticated member belongs to that seller and populates the request's seller context. Every query and mutation on the surface is then filtered to that seller automatically.
 3. The member's RBAC roles are resolved for the selected seller.
 
 A handful of vendor routes are public by design: seller registration (`POST /vendor/sellers`), invite acceptance (`POST /vendor/members/invites/accept`), `GET /vendor/stores`, and `GET /vendor/feature-flags`.
 
 ### Store
 
-Store routes are public. Customer authentication (session or bearer) is **required** for `/store/order-groups` and **optional** for `/store/offers`, `/store/products`, and `/store/search` (it enriches the pricing context when present). Public seller routes only return sellers whose status is `open` and who are not inside a scheduled closure window.
+Store routes are public. Customer authentication (session or bearer) is **required** for `/store/order-groups` and **optional** for `/store/offers` and `/store/products`, where it enriches the pricing context when present. Public seller routes only return sellers whose status is `open` and who are not inside a scheduled closure window.
 
 ## Pagination
 

package/content/references/api/store/carts/add-line-item.mdx

@@ -4,7 +4,7 @@ api: "POST /store/carts/{id}/line-items"
 description: "Add a seller offer to the cart as a line item."
 ---
 
-Adds an item to the cart by offer — Mercur resolves the offer's variant and stamps the `offer_id` on the line item so the cart can later split into per-seller orders.
+Adds an item to the cart by offer. Mercur resolves the offer's variant and stamps the `offer_id` on the line item so the cart can later split into per-seller orders.
 
 <Note>
   Unlike vanilla Medusa, this route takes an `offer_id` instead of a `variant_id`; an unknown offer returns a `404`.

package/content/references/api/store/offers/list-offers.mdx

@@ -7,7 +7,7 @@ description: "Retrieve seller offers with per-offer calculated prices."
 Returns a paginated list of offers from visible sellers whose products are published.
 
 <Note>
-  Customer authentication is optional. When a customer token is provided, the customer's group memberships enter the pricing context used for `calculated_price`. Prices are computed per offer (each offer scopes the variant's price set by an `offer_id` rule) only when `calculated_price` is in `fields` and a pricing context (`region_id`, `country_code`, or `cart_id`) resolves. Requesting `inventory_quantity` or `in_stock` requires a single sales channel — either configured on the publishable key or passed as `sales_channel_id`.
+  Customer authentication is optional. When a customer token is provided, the customer's group memberships enter the pricing context used for `calculated_price`. Prices are computed per offer (each offer scopes the variant's price set by an `offer_id` rule) only when `calculated_price` is in `fields` and a pricing context (`region_id`, `country_code`, or `cart_id`) resolves. Requesting `inventory_quantity` or `in_stock` requires a single sales channel: either configured on the publishable key or passed as `sales_channel_id`.
 </Note>
 
 ## Query parameters

package/content/references/api/store/order-groups/list-order-groups.mdx

@@ -4,7 +4,7 @@ api: "GET /store/order-groups"
 description: "Retrieve the authenticated customer's order groups."
 ---
 
-Returns a paginated list of the logged-in customer's order groups — the multi-seller wrappers created when a cart is completed.
+Returns a paginated list of the logged-in customer's order groups, the multi-seller wrappers created when a cart is completed.
 
 <Note>
   Customer authentication is required (`Authorization: Bearer <customer_token>` or a session cookie); results are always scoped to the authenticated customer.

package/content/references/api/store.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Store API"
-description: "Storefront routes under /store/* — discovery, multi-vendor carts, checkout, and order groups."
+description: "Storefront routes under /store/* for discovery, multi-vendor carts, checkout, and order groups."
 ---
 
-The Store API is what a storefront talks to. It extends Medusa's store routes with marketplace discovery (sellers, offers, search) and replaces the cart completion flow with the multi-vendor order-group split.
+The Store API is what a storefront talks to.
 
-Most routes are public; customer authentication requirements are noted per group. See [API conventions](/rc/references/api/conventions) for pagination and field selection.
+It extends Medusa's store routes with marketplace discovery (sellers and offers) and replaces the cart completion flow with the multi-vendor order-group split. Most routes are public, and customer authentication requirements are noted per group. See [API conventions](/rc/references/api/conventions) for pagination and field selection.
 
 ## Products and discovery
 
@@ -16,14 +16,6 @@ Most routes are public; customer authentication requirements are noted per group
 | `GET` | `/store/product-categories[/:id]` | Category tree with media and icons |
 | `GET` | `/store/product-attributes[/:id]` | Filterable attributes for building facet UIs |
 
-## Search
-
-| Method | Path | Purpose |
-| --- | --- | --- |
-| `POST` | `/store/search` | Query the search index across products and offers |
-
-Request body: `q`, `limit` (default 12, max 100), `offset`, pricing context (`region_id`, `country_code`, `province`), and provider-owned `filters`. Response: `{ hits, count, limit, offset, facets }` with pre-labelled collection, category, and attribute facets. See the [Search module](/rc/references/modules/search) for document shapes and filter semantics.
-
 ## Sellers
 
 | Method | Path | Purpose |
@@ -48,7 +40,7 @@ Mercur overrides the cart routes so a single cart can span multiple sellers:
 | `POST` | `/store/carts/:id/shipping-methods` | Add per-seller shipping methods |
 | `GET` | `/store/shipping-options` | Shipping options available for the cart, grouped by seller |
 | `POST` | `/store/carts/:id/promotions` | Apply promotions |
-| `POST` | `/store/carts/:id/complete` | Complete the cart — splits it into per-seller orders under an order group |
+| `POST` | `/store/carts/:id/complete` | Complete the cart, splitting it into per-seller orders under an order group |
 
 ## Order groups
 
@@ -63,5 +55,4 @@ Customer authentication **required**.
 
 <CardGroup cols={2}>
   <Card title="Order groups" href="/rc/learn/order-groups" />
-  <Card title="Search module" href="/rc/references/modules/search" />
 </CardGroup>

package/content/references/api/vendor/members/accept-member-invite.mdx

@@ -7,7 +7,7 @@ description: "Accept a seller team invite using its token."
 Accepts a member invite and joins the inviting seller's team.
 
 <Note>
-  This is a public route — no `Authorization` or `x-seller-id` header is required. The invite is identified by the `invite_token` sent in the invitation email.
+  This is a public route: no `Authorization` or `x-seller-id` header is required. The invite is identified by the `invite_token` sent in the invitation email.
 </Note>
 
 ## Body parameters

package/content/references/api/vendor/offers/batch-create-offers.mdx

@@ -46,6 +46,8 @@ Creates multiple offers at once; the whole batch is validated and processed toge
     </ParamField>
     <ParamField body="ean" type="string">EAN barcode.</ParamField>
     <ParamField body="upc" type="string">UPC barcode.</ParamField>
+    <ParamField body="manage_inventory" type="boolean" default="true">Whether stock is tracked for the offer. Set to `false` to sell without inventory checks.</ParamField>
+    <ParamField body="allow_backorder" type="boolean" default="false">Whether the offer can be purchased when it is out of stock.</ParamField>
     <ParamField body="metadata" type="object">Custom key-value pairs.</ParamField>
   </Expandable>
 </ParamField>
@@ -57,6 +59,8 @@ Creates multiple offers at once; the whole batch is validated and processed toge
     <ResponseField name="id" type="string">The offer's ID.</ResponseField>
     <ResponseField name="variant_id" type="string">ID of the listed product variant.</ResponseField>
     <ResponseField name="sku" type="string">The seller's SKU for the listing.</ResponseField>
+    <ResponseField name="manage_inventory" type="boolean">Whether stock is tracked for the offer.</ResponseField>
+    <ResponseField name="allow_backorder" type="boolean">Whether the offer can be purchased when it is out of stock.</ResponseField>
     <ResponseField name="prices" type="object[]">The offer's prices.</ResponseField>
     <ResponseField name="inventory_items" type="object[]">Linked inventory items.</ResponseField>
   </Expandable>

package/content/references/api/vendor/offers/batch-offer-inventory-items.mdx

@@ -52,6 +52,8 @@ Manages the inventory items backing an offer in one request and returns the refr
   <Expandable title="properties">
     <ResponseField name="id" type="string">The offer's ID.</ResponseField>
     <ResponseField name="sku" type="string">The seller's SKU for the listing.</ResponseField>
+    <ResponseField name="manage_inventory" type="boolean">Whether stock is tracked for the offer.</ResponseField>
+    <ResponseField name="allow_backorder" type="boolean">Whether the offer can be purchased when it is out of stock.</ResponseField>
     <ResponseField name="inventory_items" type="object[]">The offer's inventory items after the batch, with `id`, `inventory_item_id`, `required_quantity`, and `sku`.</ResponseField>
   </Expandable>
 </ResponseField>

package/content/references/api/vendor/offers/create-offer.mdx

@@ -4,7 +4,7 @@ api: "POST /vendor/offers"
 description: "Create a listing for a product variant."
 ---
 
-Creates the seller's offer for a variant — the seller's SKU, shipping profile, prices, and backing inventory.
+Creates the seller's offer for a variant: the seller's SKU, shipping profile, prices, and backing inventory.
 
 <Note>
   A product can be listed by many sellers; the offer is what carries the seller's own price and stock for a variant.
@@ -64,6 +64,14 @@ Creates the seller's offer for a variant — the seller's SKU, shipping profile,
   UPC barcode.
 </ParamField>
 
+<ParamField body="manage_inventory" type="boolean" default="true">
+  Whether stock is tracked for the offer. Set to `false` to sell without inventory checks.
+</ParamField>
+
+<ParamField body="allow_backorder" type="boolean" default="false">
+  Whether the offer can be purchased when it is out of stock.
+</ParamField>
+
 <ParamField body="metadata" type="object">
   Custom key-value pairs.
 </ParamField>
@@ -78,6 +86,8 @@ Creates the seller's offer for a variant — the seller's SKU, shipping profile,
     <ResponseField name="product_id" type="string">ID of the parent product.</ResponseField>
     <ResponseField name="shipping_profile_id" type="string">ID of the shipping profile.</ResponseField>
     <ResponseField name="sku" type="string">The seller's SKU for this listing.</ResponseField>
+    <ResponseField name="manage_inventory" type="boolean">Whether stock is tracked for the offer.</ResponseField>
+    <ResponseField name="allow_backorder" type="boolean">Whether the offer can be purchased when it is out of stock.</ResponseField>
     <ResponseField name="prices" type="object[]">Offer prices with `id`, `amount`, `currency_code`, `min_quantity`, `max_quantity`, and `price_rules`.</ResponseField>
     <ResponseField name="inventory_items" type="object[]">Linked inventory items with `id`, `inventory_item_id`, `required_quantity`, and `sku`.</ResponseField>
   </Expandable>
@@ -129,6 +139,8 @@ const { offer } = await client.vendor.offers.mutate({
     "product_id": "prod_01HXYZ",
     "shipping_profile_id": "sp_01HXYZ",
     "sku": "ACME-SHIRT-M",
+    "manage_inventory": true,
+    "allow_backorder": false,
     "prices": [
       { "id": "price_01HXYZ", "amount": 2500, "currency_code": "usd" }
     ],

package/content/references/api/vendor/offers/list-offers.mdx

@@ -72,6 +72,8 @@ Returns the seller's offers with variant, shipping profile, prices, and linked i
     <ResponseField name="sku" type="string">The seller's SKU for this listing.</ResponseField>
     <ResponseField name="ean" type="string">EAN barcode.</ResponseField>
     <ResponseField name="upc" type="string">UPC barcode.</ResponseField>
+    <ResponseField name="manage_inventory" type="boolean">Whether stock is tracked for the offer.</ResponseField>
+    <ResponseField name="allow_backorder" type="boolean">Whether the offer can be purchased when it is out of stock.</ResponseField>
     <ResponseField name="seller" type="object">The seller with `id`, `name`, and `handle`.</ResponseField>
     <ResponseField name="product_variant" type="object">The variant with `id`, `title`, and `sku`.</ResponseField>
     <ResponseField name="shipping_profile" type="object">The shipping profile with `id` and `name`.</ResponseField>
@@ -109,6 +111,8 @@ const { offers, count } = await client.vendor.offers.query({
       "product_id": "prod_01HXYZ",
       "shipping_profile_id": "sp_01HXYZ",
       "sku": "ACME-SHIRT-M",
+      "manage_inventory": true,
+      "allow_backorder": false,
       "prices": [
         { "id": "price_01HXYZ", "amount": 2500, "currency_code": "usd" }
       ],

package/content/references/api/vendor/offers/retrieve-offer.mdx

@@ -30,6 +30,8 @@ Returns a single offer owned by the seller; requesting another seller's offer fa
     <ResponseField name="sku" type="string">The seller's SKU for this listing.</ResponseField>
     <ResponseField name="ean" type="string">EAN barcode.</ResponseField>
     <ResponseField name="upc" type="string">UPC barcode.</ResponseField>
+    <ResponseField name="manage_inventory" type="boolean">Whether stock is tracked for the offer.</ResponseField>
+    <ResponseField name="allow_backorder" type="boolean">Whether the offer can be purchased when it is out of stock.</ResponseField>
     <ResponseField name="seller" type="object">The seller with `id`, `name`, and `handle`.</ResponseField>
     <ResponseField name="product_variant" type="object">The variant with `id`, `title`, and `sku`.</ResponseField>
     <ResponseField name="shipping_profile" type="object">The shipping profile with `id` and `name`.</ResponseField>
@@ -62,6 +64,8 @@ const { offer } = await client.vendor.offers.$id.query({
     "variant_id": "variant_01HXYZ",
     "product_id": "prod_01HXYZ",
     "sku": "ACME-SHIRT-M",
+    "manage_inventory": true,
+    "allow_backorder": false,
     "prices": [
       { "id": "price_01HXYZ", "amount": 2500, "currency_code": "usd" }
     ],

package/content/references/api/vendor/offers/update-offer.mdx

@@ -22,6 +22,14 @@ Updates the offer directly (no change request) and returns the refreshed offer.
   ID of the shipping profile used to fulfill the offer.
 </ParamField>
 
+<ParamField body="manage_inventory" type="boolean">
+  Whether stock is tracked for the offer. Set to `false` to sell without inventory checks.
+</ParamField>
+
+<ParamField body="allow_backorder" type="boolean">
+  Whether the offer can be purchased when it is out of stock.
+</ParamField>
+
 <ParamField body="prices" type="object[]">
   Prices to upsert; include `id` to update an existing price, omit it to add one.
   <Expandable title="properties">
@@ -45,6 +53,8 @@ Updates the offer directly (no change request) and returns the refreshed offer.
     <ResponseField name="id" type="string">The offer's ID.</ResponseField>
     <ResponseField name="sku" type="string">The seller's SKU for this listing.</ResponseField>
     <ResponseField name="shipping_profile_id" type="string">ID of the shipping profile.</ResponseField>
+    <ResponseField name="manage_inventory" type="boolean">Whether stock is tracked for the offer.</ResponseField>
+    <ResponseField name="allow_backorder" type="boolean">Whether the offer can be purchased when it is out of stock.</ResponseField>
     <ResponseField name="prices" type="object[]">The offer's prices after the update.</ResponseField>
     <ResponseField name="inventory_items" type="object[]">Linked inventory items.</ResponseField>
   </Expandable>
@@ -73,6 +83,8 @@ const { offer } = await client.vendor.offers.$id.mutate({
   "offer": {
     "id": "offer_01HXYZ",
     "sku": "ACME-SHIRT-M",
+    "manage_inventory": true,
+    "allow_backorder": false,
     "prices": [
       { "id": "price_01HXYZ", "amount": 2300, "currency_code": "usd" }
     ]

package/content/references/api/vendor/payout-accounts/create-onboarding.mdx

@@ -4,7 +4,7 @@ api: "POST /vendor/payout-accounts/{id}/onboarding"
 description: "Start or refresh provider onboarding for a payout account."
 ---
 
-Creates an onboarding session with the payout provider — for Stripe Connect, the returned `data` contains the hosted onboarding link.
+Creates an onboarding session with the payout provider. For Stripe Connect, the returned `data` contains the hosted onboarding link.
 
 ## Path parameters
 

package/content/references/api/vendor/products/batch-product-attributes.mdx

@@ -44,7 +44,7 @@ Stages attribute operations as a pending change request instead of applying them
   <Expandable title="properties">
     <ParamField body="id" type="string" required>The attribute's ID.</ParamField>
     <ParamField body="title" type="string">New attribute title.</ParamField>
-    <ParamField body="add" type="(string | object)[]">Values to select — plain strings or `{ "value": "..." }` objects.</ParamField>
+    <ParamField body="add" type="(string | object)[]">Values to select, plain strings or `{ "value": "..." }` objects.</ParamField>
     <ParamField body="remove" type="string[]">Value IDs to deselect.</ParamField>
     <ParamField body="value" type="string | number | boolean">New scalar value for `text`, `unit`, or `toggle` attributes.</ParamField>
   </Expandable>

package/content/references/api/vendor/products/create-product-variant.mdx

@@ -7,7 +7,7 @@ description: "Stage the addition of a variant to a product."
 Stages a `VARIANT_ADD` operation as a pending change request instead of creating the variant directly.
 
 <Note>
-  The endpoint responds with `202 Accepted` and a `product_change` record; the variant appears on the product once the change is confirmed. The staged variant is always created with `manage_inventory: false` — stock is tracked on offers.
+  The endpoint responds with `202 Accepted` and a `product_change` record; the variant appears on the product once the change is confirmed. The staged variant is always created with `manage_inventory: false`. Stock is tracked on offers.
 </Note>
 
 ## Path parameters

package/content/references/api/vendor/products/create-product.mdx

@@ -7,7 +7,7 @@ description: "Create a new product owned by the seller."
 Creates a product; when no status is provided it is created with status `proposed`.
 
 <Note>
-  When the product request flow is enabled, `status` may only be `draft` or `proposed` — publishing requires operator approval.
+  When the product request flow is enabled, `status` may only be `draft` or `proposed`. Publishing requires operator approval.
 </Note>
 
 ## Query parameters

package/content/references/api/vendor/products/delete-product.mdx

@@ -4,7 +4,7 @@ api: "DELETE /vendor/products/{id}"
 description: "Stage a product deletion as a change request."
 ---
 
-Does not delete the product directly — it stages a pending `PRODUCT_DELETE` change request that an operator confirms or declines.
+Does not delete the product directly. It stages a pending `PRODUCT_DELETE` change request that an operator confirms or declines.
 
 <Note>
   The endpoint responds with `202 Accepted` and a `product_change` record; the product remains until the change is confirmed.

package/content/references/api/vendor/products/update-product.mdx

@@ -4,7 +4,7 @@ api: "POST /vendor/products/{id}"
 description: "Stage an update to a product as a change request."
 ---
 
-Does not modify the product directly — it stages a pending change request that an operator confirms or declines.
+Does not modify the product directly. It stages a pending change request that an operator confirms or declines.
 
 <Note>
   The endpoint responds with `202 Accepted` and a `product_change` record, not the updated product. Use [Preview Product Change](/rc/references/api/vendor/products/preview-product) to inspect the pending change and [Cancel Product Change](/rc/references/api/vendor/products/cancel-product-change) to withdraw it.

package/content/references/api/vendor/sellers/create-seller.mdx

@@ -7,7 +7,7 @@ description: "Register a new seller account with its first member."
 Creates a seller account, optionally with an initial address, professional details, and payment details.
 
 <Note>
-  This is a public route — no `Authorization` or `x-seller-id` header is required. When called without an authenticated member, `member_email` is required so the owner member can be created.
+  This is a public route: no `Authorization` or `x-seller-id` header is required. When called without an authenticated member, `member_email` is required so the owner member can be created.
 </Note>
 
 ## Body parameters
@@ -33,7 +33,7 @@ Creates a seller account, optionally with an initial address, professional detai
 </ParamField>
 
 <ParamField body="member_email" type="string">
-  Email for the owner member — required when there is no authenticated member.
+  Email for the owner member, required when there is no authenticated member.
 </ParamField>
 
 <ParamField body="first_name" type="string">

package/content/references/api/vendor/sellers/list-sellers.mdx

@@ -7,7 +7,7 @@ description: "List the seller accounts the authenticated member belongs to."
 Returns the member's seller memberships (excluding terminated sellers), each with the related seller and role.
 
 <Note>
-  This route requires only the `Authorization` header — no `x-seller-id` — since it is used before a seller is selected.
+  This route requires only the `Authorization` header (no `x-seller-id`) since it is used before a seller is selected.
 </Note>
 
 ## Query parameters

package/content/references/api/vendor.mdx

@@ -1,9 +1,11 @@
 ---
 title: "Vendor API"
-description: "Seller-scoped routes under /vendor/* — every request operates on the authenticated member's selected seller."
+description: "Seller-scoped routes under /vendor/* where every request operates on the authenticated member's selected seller."
 ---
 
-The Vendor API is the seller's surface. Every route is scoped to one seller through the member authentication and `x-seller-id` mechanism described in [API conventions](/rc/references/api/conventions#vendor) — a seller can never read or mutate another seller's data.
+The Vendor API is the seller's surface.
+
+Every route is scoped to one seller through the member authentication and `x-seller-id` mechanism described in [API conventions](/rc/references/api/conventions#vendor). A seller can never read or mutate another seller's data.
 
 ## Account and team
 
@@ -24,7 +26,7 @@ The Vendor API is the seller's surface. Every route is scoped to one seller thro
 
 ## Products and offers
 
-Products are shared master records: updates stage a [change request](/rc/references/modules/product-edit) rather than writing directly, and the list shows products the seller created plus published, unrestricted products.
+Products are shared master records. Updates stage a [change request](/platform/product-edit/overview) rather than writing directly, and the list shows products the seller created plus published, unrestricted products.
 
 | Method | Path | Purpose |
 | --- | --- | --- |
@@ -43,7 +45,7 @@ Products are shared master records: updates stage a [change request](/rc/referen
 
 ### Catalog taxonomy (read-only)
 
-`GET /vendor/product-categories[/:id]`, `/vendor/product-tags[/:id]`, `/vendor/product-types[/:id]`, `/vendor/product-attributes[/:id]`, `/vendor/collections[/:id]` — plus `POST /vendor/product-categories/:id/products` and `POST /vendor/collections/:id/products` to place own products.
+`GET /vendor/product-categories[/:id]`, `/vendor/product-tags[/:id]`, `/vendor/product-types[/:id]`, `/vendor/product-attributes[/:id]`, and `/vendor/collections[/:id]`. Use `POST /vendor/product-categories/:id/products` and `POST /vendor/collections/:id/products` to place own products.
 
 ## Orders and fulfillment
 
@@ -146,5 +148,4 @@ Full RMA suites exist per domain, following the same action pattern Medusa uses
 
 <CardGroup cols={2}>
   <Card title="Store API" href="/rc/references/api/store" />
-  <Card title="API Client" href="/rc/tools/api-client" />
 </CardGroup>