# Service Details Overview
> Source: https://development.fuze-store.com/docs/store/pos/service-context/overview

# Service Details Overview

**Service Details** let you capture a small set of structured, per-visit fields on every order -- a license plate, a claim tag, a device serial number, a unit number. It is built for walk-in service shops (car wash, laundry, repair, water refill), but it is completely generic: **you choose the field labels**, so the same tool fits any business.

![The register order summary showing a Service details section with a plate number and vehicle type](/docs/store/pos/service-context/register-service-details.png)

## What Are Service Details?

A **service detail** is a labeled field you fill in while ringing up a sale -- for example a **Plate number** on a car-wash order or a **Claim tag #** on a laundry order. The values are saved with the order, so you can later match the order back to the physical item you serviced.

You decide which fields exist and what they are called. A car wash might use *Plate number*, *Vehicle type*, and *Color*; a repair shop might use *Device*, *Serial / IMEI*, and *Reported issue*. Nothing is hard-coded to any industry.

## Why Use Service Details?

- **Match orders to the item you serviced** -- find the right car, garment bag, or device at pickup.
- **Structured, not free text** -- consistent fields your whole team fills the same way, instead of cramming everything into the order note.
- **Prints where it matters** -- values can appear on the receipt, the kitchen/queue ticket, and the customer display.
- **Searchable** -- mark one field (such as the plate or claim tag) as the primary identifier.
- **Zero setup for common trades** -- pick a store template and the right fields are filled in for you (see [Store Templates & Examples](/docs/store/pos/service-context/store-templates-and-examples)).

## The Four Field Types

When you create a field you pick one of four types:

| Type | Use it for | Example |
| --- | --- | --- |
| **Text** | Free text, optionally auto-uppercased | Plate number, claim tag, serial |
| **Number** | Whole numbers | Bag count, gallon count |
| **Dropdown** | A fixed list of choices you define | Vehicle type: Sedan / SUV / Van |
| **Yes / No** | A simple on/off flag | VIP, express service |

## Where Service Details Appear

Once a field is set up and filled in, its value can show up in several places:

- **POS register** -- a **Service details** section in the order summary, and a **Service details** button in the register action **Menu**.
- **Order details** -- listed on the order after it is created.
- **Waiting list** -- captured when you add a customer to the queue.
- **Receipt & queue ticket** -- printed on the documents (for fields you mark to show there).
- **Customer display** -- the primary identifier can appear on the customer-facing screen.

## Field Limits

A few simple rules keep the capture screen fast:

- Up to **10 fields** per store.
- Each field needs a unique **key** (letters, numbers, and underscores; must start with a letter).
- **One** field can be marked **Searchable** as the primary identifier.
- **Dropdown** fields need at least one option.

  Service Details is available on any paid plan (Starter and up) and during your free trial. On the free Basic plan the capture screens and the editor are hidden -- but any details already saved on past orders stay visible, and everything switches back on the moment you upgrade.

- [Setting Up Your Fields](/docs/store/pos/service-context/setting-up-fields)
- [Capturing Details at Checkout](/docs/store/pos/service-context/capturing-at-checkout)
- [Store Templates & Examples](/docs/store/pos/service-context/store-templates-and-examples)
- [Using the POS Register](/docs/store/pos/using-pos-register)