> ## 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.
# Day one in the warehouse
> Part of step 9. One shift in one page: answer an availability question, explain a no, find a unit from the label on it, take one out of circulation, and grade stock as it arrives.
Print this page and keep it in the warehouse. It covers one shift and nothing beyond it, so hand it to someone on their first day and let the area guides wait until their second week.
Select the locations you work from in the location picker before anything else. **Free Stock**, **Committed Stock** and **Has conflicts** count the selected locations only, so a unit sitting in a location nobody selected reads as no stock at all.
## Before the shift starts
| Check | Why it matters |
| --------------------------------------------------- | --------------------------------------------------------------------------- |
| Your locations are selected | Every stock count on the table is scoped to that selection |
| The toolbar date is the moment you were asked about | The picker holds one moment rather than a span, so the answer moves with it |
| You can reach **Settings → Archived assets** | A unit missing from the table is usually archived rather than lost |
## Answer the availability question
Open **Inventory → Stock items**, set the toolbar date to the moment in question, then read the row:
| Column | What it tells you |
| ------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Availability** | **Available** or **Not Available** at that moment |
| **Free Stock** | Units free across your selected locations |
| **Committed Stock** | Units held by orders and reservations |
| **Commitments** | What holds the unit. Open the cell to reach the order, or the item's **Events** tab when several things hold it |
| **Has conflicts** | **Yes** when an order expects this unit with nothing holding it. Open the cell to land on **Events** |
Answer in one line, then name what is holding it. "Not free on Friday" ends the call, and "not free on Friday, an order holds it until Saturday noon" ends the argument.
## Explain a no
Work down this table in order. The first row that matches is the answer.
| What you see | Where to look | What it means |
| ----------------------------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------ |
| **Not Available**, with a commitment on the row | **Commitments** | An order or a reservation holds those dates |
| The dates look clear either side of an order | **Buffer time** on **Events** | Turnaround padding blocks the hours around the neighbouring order |
| A hold with no order behind it | **Events** | Someone reserved the unit for maintenance or internal use |
| **Has conflicts** reads **Yes** | **Events** | An order has the unit assigned with nothing holding it, and a manager resolves that on the order |
| **Status** reads **Inactive** | **General** | The unit takes no new orders, and the orders already behind it stay |
| The unit is absent from the table | **Settings → Archived assets** | The unit left service and contributes no capacity |
Hand anything past this list to whoever owns the catalog. A unit can be free and still unsellable, because the listing decides which stock it draws from and the location decides what it sells. Read [Check availability](/docs/guides/inventory/check-availability) for that half of the question.
## Find the unit from the label on it
Use the scanner anywhere in the admin. One scan resolves to one record:
| Scanned code | Where you land |
| ---------------------------- | --------------- |
| A stock item code | That stock item |
| A listing barcode | That listing |
| An order reference or number | That order |
The match is exact once spaces are trimmed, so a half-read label gives a red "No match found for scanned code" message rather than the wrong unit. Order pages run their own scanner, so the global scan stays out of the way while you are on one. Print labels from [Stock codes and barcodes](/docs/guides/inventory/stock-codes-and-barcodes).
## Take a unit out of circulation
Reserve the unit instead of leaving a note on the shelf. Open the unit, go to **Events**, then **Add → Reservation**:
| Field | What to put in it |
| -------------- | ---------------------------------------------------------------------- |
| **Title** | What the unit is doing: a service, a repair, an internal loan |
| **Location** | Where it sits while it is out |
| **Start date** | When it leaves circulation |
| **End date** | When you expect it back, or tick **No end date** while that is unknown |
A reservation over dates that something already holds takes the stock away from whatever holds them.
**Existing orders and reservations will be affected** is the confirmation that then appears. Read the list it shows, because it names every order and reservation that loses its stock, and confirm only once you know who to tell.
A released hold does not come back. The affected order keeps the unit assigned with nothing holding it, which is what **Has conflicts** reads afterwards.
Archiving a unit releases its future holds the same way, and taking it back out of the archive restores none of them. Reserve a unit you expect to return to service, and archive one that has left for good.
## Grade stock as it arrives
Record the grade the day the unit lands, while it is in your hands. **Condition** on the unit's **General** tab is free text, so it carries a note for a person and nothing further.
Put the grade in an attribute when it decides what can be sold. A listing draws stock by attributes, item code, SKU code, item name and SKU name, never by **Condition**, so a grade kept only in that field cannot be sold from. Follow [Intake and grading](/docs/guides/inventory/intake-and-grading) to set that up once.
## Done when
* A new employee has answered an availability question from **Inventory → Stock items** unaided, and named what was holding the unit.
* They have scanned a label and landed on the right record without asking where it went.
* They have reserved a unit for maintenance and read back which orders it affected.
* They have found an archived unit under **Settings → Archived assets** after failing to find it in the table.
* They can say why a grade written in **Condition** does not make a unit sellable.
## Related articles
The launch step this guide belongs to.
The counter half of the same shift.
The full diagnosis, including why a free unit is not always sellable.
Giving each unit a label worth scanning.
Holds for maintenance and internal use in detail.
Grading used stock so listings can draw from it.
Turnaround padding, and where a picker finds the unit.