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

# Settings - Order view

> Set how much of a listing's stock an order shows at once, and what each stock item says about itself.

export const viewAccessDefinition = "The view operation: read a record without changing it.";

export const manageAccessDefinition = "The manage operation: update an existing record. Creating and deleting are separate operations.";

export const deleteAccessDefinition = "The delete operation: remove a record. Most areas archive instead of deleting.";

export const createAccessDefinition = "The create operation: add a new record. Updating an existing one is the manage operation.";

<Info>
  This view can look different dependent on your user role. <br />See [Visibility and permissions](#visibility-and-permissions) for details.
</Info>

## Primary purpose

Open **Settings → Orders → Order view** to set how an order reads on screen. Nothing here changes what an order does. It changes how much of it staff see at once, and how quickly they can tell a finished line from one still being handled.

Every setting is account-wide. Staff cannot override them per order.

<AccordionGroup>
  <Accordion title="Stock items shown per listing">
    How many stock items a listing shows before the rest collapse behind a chip staff can open. Accepts 1 to 50, and starts at 5.

    A line of twenty units is otherwise twenty rows of the card. Pick the number from how your staff book: someone taking orders of two wants a different answer from someone taking orders of ten.
  </Accordion>

  <Accordion title="What each stock item says">
    Three toggles, all on to begin with. Turn one off and every unit's row gets shorter.

    | Toggle | What it adds to a unit's row |
    | :- | :- |
    | **Show SKU name** | The SKU the unit belongs to, under the unit's own name |
    | **Show SKU code** | That SKU's code |
    | **Show fulfillment labels** | Captions on the state chip and the item code |

    Turn both SKU toggles off to leave a unit with its own name alone. Turn fulfillment labels off once staff read the chips by sight, which saves two lines of height per unit.
  </Accordion>

  <Accordion title="Finished and done tints">
    Two colours, so staff read past the lines they are finished with.

    | Setting | What it sits behind |
    | :- | :- |
    | **Finished item background** | An item that has reached the end of its road |
    | **Done item background** | An item whose handling is finished for now: a booked item handed over, until it comes back |

    Pick both, or set either to **No tint** where the row's own chips say enough. Which items count as finished or done is set per state under [Fulfillment lifecycle](/docs/settings/orders/item-fulfillment-states), not here.

    The finished tint is the deeper of the two out of the box, because it is the further along of the two readings.
  </Accordion>
</AccordionGroup>

## Related concepts

<AccordionGroup>
  <Accordion title="The tints read your item states, not a fixed list">
    An item is finished or done because the state it sits in is marked **Terminal state** or **Done** for that line's purchase type. Rename and recolour your states as much as you like: the two tints keep meaning the same thing.

    Read more: [Fulfillment lifecycle](/docs/settings/orders/item-fulfillment-states)
  </Accordion>

  <Accordion title="Collapsing is display only">
    A unit folded behind the chip is still on the order, still claims its stock, and still moves under your automations. The fold decides what is drawn, never what is counted.

    Read more: [Order Lifecycle](/docs/concepts/orders/order-lifecycle)
  </Accordion>
</AccordionGroup>

## Visibility and permissions

This page is gated by `account_settings:orders`, in the four operations <Tooltip tip={viewAccessDefinition}>view</Tooltip>, <Tooltip tip={createAccessDefinition}>create</Tooltip>, <Tooltip tip={manageAccessDefinition}>manage</Tooltip> and <Tooltip tip={deleteAccessDefinition}>delete</Tooltip>.

Owner and Admin hold every operation. Manager and Member do not hold it at all, so they read orders drawn to your settings without being able to change them.

For what each operation means and the full role matrix, see [Users & Roles](/docs/settings/users-roles).

## Related articles

<CardGroup cols={2} className="doc-rows-condensed">
  <Card title="Orders settings" href="/docs/settings/orders">
    The four sections under Settings → Orders.
  </Card>

  <Card title="Fulfillment lifecycle" href="/docs/settings/orders/item-fulfillment-states">
    The states your staff move order items through, and which of them finish a line.
  </Card>

  <Card title="Order lifecycle" href="/docs/settings/orders/order-lifecycle">
    The states an order moves through, and what is checked along the way.
  </Card>

  <Card title="Orders" href="/docs/orders/overview">
    The order view these settings draw.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.