# Cell history Every rate, inventory number, and restriction lives at the intersection of a property, a room, a rate plan, and a date. **Cell history** shows how one calendar cell changed over time. ## Why this exists Pricing and inventory cells get touched a lot. In a busy month, a single rate cell may see dozens of changes: a base-rate update, a promotion activation, a partner update, an Adragent bulk operation, or a manual fix. When a number looks wrong, cell history helps you see the sequence behind it. Use it from the rate calendar when a date needs explanation before you change it again. ## What you see For each change to a cell, the panel shows: * **What** — the field that changed (rate value, inventory count, stop-sale flag, restriction). * **Before / after** — the previous value and the new value, side by side. * **When** — the timestamp. * **Who** — the operator, or the partner if the change was inbound, or the Adragent run if the agent applied it. * **Where** — the source of the change (console, Adragent chat, connected partner). * **Why** — for some changes, the reason: a promotion activation, a contract update, an explicit override. * **Support reference** — for platform support when deeper help is needed. A typical cell history view shows all of this as a timeline, newest first, with the option to expand any entry for full detail. ## What it looks like for an operator Open any cell in the rate calendar; the cell-history panel opens alongside it. A typical history might read: * *April 3, 09:14 — Rate set to EUR 180 by Operator A from the console.* * *April 5, 11:02 — Spring Saver promotion activated; derived rate now EUR 153.* * *April 8, 23:47 — Inbound from Channel C set inventory to 4 (was 5); reason: 1 booked.* * *April 10, 07:30 — Adragent run #1247: bulk weekend pricing applied; new base EUR 220 (Saturdays only).* * *April 12, 15:09 — Operator B paused Spring Saver promotion; derived rate back to EUR 220.* Five changes, five different sources, one timeline. The cell value at any point is reconstructable from the chain. ## How finance and operations use it Beyond "*why is this number what it is*", cell history supports a few common workflows: * **Reconciliation** — for any booked rate, trace back to the cell version active at the time of booking. * **Dispute resolution** — a partner claims they saw a different rate; the history shows what the cell was at the moment they polled. * **Bulk-operation review** — after Adragent applies a wide change, the affected cells each carry the run reference; you can verify the operation behaved as expected. ## Source attribution — every change knows where it came from A cell change always carries provenance: | Source | Attribution | | --------------------------- | --------------------------------------------------------------------------------------------- | | Operator action via console | The user, the screen, the timestamp. | | Adragent operation | The user who initiated, the run ID, the chat or panel context, the preview that was approved. | | Connected system | The caller's identity and support reference. | | Partner inbound | The connector, the partner identifier, the partner message reference. | | Engine derivation | The contract version, the promotion ID, the markup rule that fired. | Mixed sources on the same cell are normal. The history shows them in order; the current state is the result of all of them together. ## Per-channel inbound — keeping partner writes honest When a partner pushes an update — a new rate, a new inventory count, a stop-sale — the cell history shows: * The partner identifier (which channel sent it). * The partner message reference for cross-checking with the partner's records. * The mapping that resolved the partner's identifiers to your catalog item. * The before / after values. This is what makes "the partner sent us a wrong rate" actionable rather than mysterious — you have the message they sent, the time they sent it, and the state both before and after. ## Adragent and cell history Adragent operations on a cell show the related run: * The request that started the run. * The preview that was approved. * The result that touched the cell. ## Where to next * **The rate plans these cells live on** → [Rate plans](/console/pricing-and-availability/rate-plans.md) * **The inventory side of the same cells** → [Inventory](/console/pricing-and-availability/inventory.md) * **The engine that derived the displayed rate** → [Pricing engine](/console/pricing-and-availability/pricing-engine.md) * **Adragent operations** → [Adragent](/console/adragent/overview.md) --- # 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://adrasis.gitbook.io/console/pricing-and-availability/cell-history.md?ask= ``` 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.