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

# Your stock, where your team already works

> Live unit inventory synced from your DMS feed, so anyone answering a call can say what is actually on the lot and deals get written against a real unit.

Inventory is your live unit stock, synced in from your DMS or inventory feed on a schedule. It answers the question that comes up on almost every inbound call: do you actually have it?

<Note>
  Inventory is an optional workspace surface, off by default. An admin turns it on under **Settings → General → Workspace surfaces**. Until then, the page explains what it does rather than disappearing from the nav.
</Note>

## What it gives you

* **Your team can answer "is it in stock?" on the call**, instead of promising to check and calling back.
* **Your coworkers can answer it too.** A voice coworker looks the unit up mid-call rather than taking a message.
* **Deals get written against a real unit.** A deal on [the Desk](/concepts/desk) can point at an actual VIN, so nobody works numbers on something that sold yesterday.

## The catalogue

One row per unit, with the header showing the total count and how long ago the feed last synced.

Search by VIN, make, model, or stock number, and filter by:

| Filter         | Values                                                    |
| -------------- | --------------------------------------------------------- |
| **Location**   | Any rooftop in the feed                                   |
| **Body style** | Whatever your feed carries, for example SUV, sedan, truck |
| **Condition**  | New, used, or certified pre-owned                         |

Each unit carries the fields you would expect to quote from: year, make, model, trim, price, MSRP, mileage, exterior colour, body style, location, and photos. Recreational-vehicle feeds additionally carry class, sleeping capacity, length, and slide-outs.

## How the feed works

You connect a feed once and it keeps itself current. Two shapes are supported:

| Transport | How it runs                                                                                                   |
| --------- | ------------------------------------------------------------------------------------------------------------- |
| **Pull**  | RevDesk fetches your feed on a schedule.                                                                      |
| **Push**  | Your DMS posts to a RevDesk endpoint whenever stock changes, authenticated with a token issued for that feed. |

Feeds rarely agree on column names, so each one carries a mapping from your feed's columns onto the fields RevDesk understands. Common column names are recognised automatically, and anything unusual is mapped once at setup.

Units are keyed on VIN, so the same unit arriving in two syncs updates in place rather than duplicating. A unit that stops appearing in the feed is marked sold or removed rather than silently vanishing, so a deal already written against it still resolves.

Sync failures surface on the feed rather than failing quietly, along with the count of units in the last successful run.

<CardGroup cols={2}>
  <Card title="The Desk" icon="table" href="/concepts/desk">
    Work every lead as a deal, against a real unit.
  </Card>

  <Card title="Coworkers" icon="users" href="/concepts/coworkers">
    Who answers the call that asks what is on the lot.
  </Card>
</CardGroup>