# Pricing & Availability

A catalog doesn't set prices or manage stock — that data lives in NetSuite. What you control on the catalog is **which pricing and availability fields are pulled into the output** at build time. Five toggles in the catalog's **Settings** section drive this.

## When you'd use this

* Configuring a B2B catalog that needs price levels and quantity breaks.
* Configuring a B2C catalog that should only show base price.
* Reducing build time on a large catalog by trimming unnecessary fields.
* Diagnosing why a portal isn't showing the pricing detail you expected.

## The five toggles

All on the Edit Catalog page → **Settings** card.

<table data-view="cards"><thead><tr><th>Toggle</th><th>What it pulls in</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Price Levels</strong></td><td>Every price level configured on each item (Base, Wholesale, VIP, etc.).</td><td><a href="#price-levels">#price-levels</a></td></tr><tr><td><strong>Quantity Breaks</strong></td><td>Volume-tiered pricing schedules per item.</td><td><a href="#quantity-breaks">#quantity-breaks</a></td></tr><tr><td><strong>Item Vendor</strong></td><td>Vendor information from each item's preferred-vendor sublist.</td><td><a href="#item-vendor">#item-vendor</a></td></tr><tr><td><strong>Locations</strong></td><td>Per-location inventory data per item.</td><td><a href="#locations">#locations</a></td></tr><tr><td><strong>Add Pricing Fields</strong></td><td>Supplemental pricing fields and metadata (additional rates, etc.).</td><td><a href="#add-pricing-fields">#add-pricing-fields</a></td></tr></tbody></table>

### Price Levels

NetSuite supports multiple price levels per item — base price, wholesale, VIP, and so on. With **Price Levels** on, every configured level for each item ships in the catalog output. The portal can then show customer-specific pricing based on the price level on the customer's NetSuite record.

Off → only the base price ships.

### Quantity Breaks

Quantity breaks are volume-tiered prices configured on the item record (e.g. *$10 each for 1–9 units, $8.50 each for 10–49*). With this on, the full schedule per item ships with the catalog. Common for B2B and wholesale.

### Item Vendor

Pulls the preferred-vendor information from the item record's vendor sublist into the catalog. Useful for procurement-facing portals.

### Locations

Per-location inventory data per item. With this on, the catalog output carries stock quantities broken down by every location the item is stocked at. Portals can use this to show *Available at Store X* / *In stock at warehouse Y*.

See [Inventory](/client-admin-guide/creating-catalogs/inventory-management.md) for the full picture.

### Quantity Adjusts Rate

When this is on, changing the quantity on an order line recalculates the unit price using the item's configured pricing tiers (volume breaks, quantity schedules, etc.). Turn it off if you want the rate to stay fixed regardless of quantity changes.

This setting is most useful for B2B catalogs where pricing scales with volume — the portal automatically shows the right tier price as the buyer adjusts quantities.

### Add Pricing Fields

Adds supplemental pricing fields beyond the standard price levels — additional rate fields and pricing metadata that some NetSuite item configurations rely on. Leave it off unless you know your portals need these extra fields.

## Where the source data lives

Every pricing and availability field originates in NetSuite. The catalog is a snapshot built on top.

| Data                      | NetSuite source                             |
| ------------------------- | ------------------------------------------- |
| Base price                | Item record — Sales/Pricing tab             |
| Price levels              | Item record — multiple price-level fields   |
| Quantity breaks           | Item record — quantity pricing schedule     |
| Customer's price level    | Customer/Contact record — Price Level field |
| Stock on hand / available | Inventory detail records per location       |
| Preferred vendor          | Item record — vendor sublist                |

Toggling a Settings checkbox doesn't change anything in NetSuite. It only changes what gets included next time the catalog is built.

## After you change a toggle

Click **Save & Update** to rebuild the catalog and have the change reach the portal immediately. Just **Save** stores the configuration but the portal won't reflect the new fields until the next rebuild — that might be a scheduled refresh or another manual reprocess.

{% hint style="warning" %}
On large catalogs, toggling more pricing fields on increases build time and output size. If a portal doesn't actually use Price Levels or Quantity Breaks, leave them off.
{% endhint %}

## Common issues

* **Portal shows "no price"** — if Price Levels is off and the customer's NetSuite record references a non-base price level, the customer-facing portal has no price to display. Turn Price Levels on.
* **Quantity breaks render flat** — confirm Quantity Breaks is on **and** the item record actually has a quantity schedule. The catalog can only surface what NetSuite holds.
* **Stock disagrees between catalog and NetSuite** — the catalog is a snapshot. Trigger **Reprocess** on the catalog to pick up the latest inventory.
* **Vendor field is empty** — the source is the preferred-vendor sublist on each item. Items without a preferred vendor won't carry vendor data.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Creating a Catalog</strong></td><td>Where these toggles live, plus every other section of the Edit Catalog page.</td><td><a href="/pages/sqKV6Gm0WqBRQeT9aFbs">/pages/sqKV6Gm0WqBRQeT9aFbs</a></td></tr><tr><td><strong>Inventory</strong></td><td>How the Locations toggle includes per-location stock data.</td><td><a href="/pages/bTe9OOdZKbLt2hnXRIRb">/pages/bTe9OOdZKbLt2hnXRIRb</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/client-admin-guide/creating-catalogs/pricing-and-availability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.