---
alias: "fc.reports.ipuipc"
aliases:
  - fc.reports.ipuipc
category: content
module: Analytics
---
# fc.reports.ipuipc

IPU (Inventory Position Update) and IPC (Inventory Position Change) reporting component with line chart visualization, configurable filters for report type, date range, and granularity.

## When to Use
- Inventory analytics dashboards
- Monitoring inventory update volumes over time
- Capacity planning and IPU/IPC usage tracking

## Key Props
| Prop | Type | Required | What it controls |
|------|------|----------|------------------|
| `width` | CardWidth | No | Card width on 12-column grid. Named widths: `"quarter"`, `"third"`, `"half"`, `"two-thirds"`, `"full"`, or number `1-12`. Default: `"full"`. Mobile auto-adjusts to 12. |

## Data Binding
The component self-manages its data fetching based on three user-configurable filters:

- **Display**: Report type -- "Inventory Position Update" (default) or "Inventory Position Change"
- **Date/time range**: Visualization period, default last 31 days. Based on UTC time.
- **Granularity**: Detail level -- "Minute", "Hour", or "Day" (default)

The line chart displays data points across the selected date range. X-axis shows the date range (UTC), Y-axis shows quantity of inventory updates. A "Total Updates" summary shows the cumulative sum of all usages within the selected range.

## Descendants
No.

## Gotchas
- Data older than 185 days cannot be displayed. Exceeding this limit shows: "The maximum time frame is 185 days."
- Granularity constrains the date range: Minute granularity max 12 hours, Hour granularity max 31 days. Day granularity has no additional constraint beyond 185 days.
- Mismatched granularity/range shows: "The time frame for your chosen granularity is too long."
- Both chart start and end points use UTC timestamps.

## Manifest Example
```json
{
  "component": "fc.reports.ipuipc",
  "props": {
    "width": "full"
  }
}
```

## AI Parse Notes
- **Primary intent:** Declarative Mystique component definition for manifests.
- **Selection signals:** Match by `alias`, category, and required `Key Props`.
- **Assembly hints:** Combine with compatible parent/child components listed in `Composition Patterns`.
- **Safety checks:** Validate required props and data bindings before manifest generation.
