# Order Details block

> Order Details

Order details sheet: a right-anchored fulfillment review surface that reuses the solution-inventory-7 sheet shell. Header carries an Order Details title row, the order id + Shipped badge, a Created / Customer meta line, and a vertically-centered Delete / Order Tracking / View Shipping Label action cluster. The scrollable two-column body pairs an Order Data Frame (Items, Total Price, Shipping Priority, Delivery Method), a Products Frame with Item-based rows (image + name + SKU/color, inline weight input on the right), and a title-less Shipping Frame combining a vertical route Timeline, a UPS Global carrier chip, a Separator, and a four-step Picking / Packed / Shipping / Delivered status stepper. The right rail is a Summary Frame with shipping-to address, price details (Subtotal / Shipping / Tax / Total), and a separated total row. All frames use `dense spacing="sm"` for an operator-density default. The footer mirrors the header action cluster with a Read Shipping Terms & Conditions link on the left.

- Type: Pro block
- Category: [Inventory](https://web.dev.reui.io/blocks/solutions/inventory.md)
- Page: https://web.dev.reui.io/blocks/solutions/inventory/solution-inventory-11
- MCP: `get_block("solution-inventory-11")`
- Built with: Badge, Button, Frame, Input Group, Item, Label, Scroll Area, Separator, Sheet, Timeline
- Installs with a ReUI Pro or Ultimate license; setup: https://web.dev.reui.io/docs/license-setup

## Best for

An order review pairing shipping priority, delivery method and per item weight inputs with a route, a 4 step stepper and a price summary

## Agent notes

- `SUMMARY.finalTotal` is 22.99 but `SUMMARY.price.total` is 350, so the two total rows disagree; feed both from one order total
- `HeaderActions` serves header and footer: Delete is a placeholder anchor, while Order Tracking and View Shipping Label have no handler
- The weight `InputGroupInput` uses a `defaultValue` from `item.weight` and has no change handler, so edited weights are never stored

## When not to use

- A form that buys a shipping label from package size, weight and carrier fields: use [Shipping Label](https://web.dev.reui.io/blocks/solutions/inventory/solution-inventory-10.md) (`get_block("solution-inventory-10")`)
- A buyer facing confirmation of a purchase with line items, totals and tracking details: use the [Receipt blocks](https://web.dev.reui.io/blocks/ecommerce/receipt.md)

## Install

```bash
npx shadcn@latest add @reui/solution-inventory-11
```

## About Inventory blocks

### When to use

- Stock overview and ledger pages: KPI tiles, a stock health bar and a filterable SKU table
- A low stock reorder queue, or a purchase order received line by line from its supplier
- Product and order overlays: stock rules, variants and photos, order review, tracking or a shipping label

### When not to use

- A team overview of KPI tiles and charts where nothing tracks stock or SKUs: use the [Dashboard blocks](https://web.dev.reui.io/blocks/application/dashboard.md)
- A side panel for a record other than a product, order or shipment: use the [Sheet blocks](https://web.dev.reui.io/blocks/application/sheet.md)
- An activity or event history on its own, with no stock or shipment around it: use the [Timeline blocks](https://web.dev.reui.io/blocks/application/timeline.md)

### Agent notes

- Every block sets a `min-h-svh` wrapper with its own padding in page.tsx or its root component; drop it when the block mounts inside your app layout
- No block fetches or saves anything: actions set local state, fire a sonner `toast`, link to a page anchor or have no handler, so wire each to your API

Every ReUI item has a twin like this one; the index is https://web.dev.reui.io/llms.txt. Agents with the ReUI MCP (https://web.dev.reui.io/docs/mcp) get the same guidance from the getters named above.