> ## Documentation Index > Fetch the complete documentation index at: https://docs.alforse.com/llms.txt > Use this file to discover all available pages before exploring further. # Kanban > Scan-based pull replenishment. A kanban card ties an item to a bin, and a signal fires a purchase order, a job, or a stock transfer. A kanban is a physical pull signal represented by a printed card, QR code, or URL. It links an item, location, storage unit, and reorder quantity. Scanning the signal creates the purchase order, job, or stock transfer needed to refill the bin. A [reordering policy](/docs/reference/reordering.md) calculates suggestions from on-hand quantity, demand, and reorder points. Kanban replenishment is direct: a signal creates a real document immediately. Use policies for planning-driven replenishment and kanban for shop-floor pull. Alforse screenshot**Kanbans list with the order, start, and complete QR codes and the Reorder Qty., Replenishment, Supplier, and Storage Unit columns** ## What a kanban holds Each kanban is a small record: an item, where it lives, how much to reorder, and how to reorder it. On a `Transfer` kanban, the form adds a From Storage Unit beside the To Storage Unit. FieldType
**Item**required The part, material, tool, or consumable this card replenishes.
**Quantity**required How much to reorder on each signal (at least 1). On a `Transfer` kanban, this is the quantity moved from the From storage unit.
**Replenishment system**required How the signal replenishes: `Buy` (raise a purchase order), `Make` (create a job), or `Transfer` (create a stock transfer between two storage units in the location). See replenishment system.
**Location**required The location whose stock this card refills.
**Storage unit** The bin the reordered stock lands in. Defaults from the item's pick method for that location if left blank. (`Buy` and `Make`.)
**From storage unit**required The storage unit the stock moves out of. It must be in the kanban's location. (`Transfer` only.)
**To storage unit**required The storage unit this card refills. It must be in the kanban's location and must be different from the From storage unit. (`Transfer` only.)
**Supplier** Who to buy from. **Required for `Buy` kanbans.**
**Purchase unit of measure / Conversion factor** The unit you buy in and how many stock units that equals. Alforse applies both to the PO line. (`Buy` only.)
**Auto Release** On a `Make` scan, release the created job to the floor (status `Ready`) instead of leaving it in draft. (`Make` only.)
**Auto Start Job** On a `Make` scan, drop the operator straight into the first operation in MES. Requires Auto Release. (`Make` only.)
**Completion Barcode** The code operators scan to mark the job complete; auto-generated when left blank. (`Make` only.)
## The scan flow Each kanban has scan targets for `order`, `start`, and `complete`. A scan opens a URL, runs the action, and redirects to the resulting document. QR codes are black for order, emerald for start, and blue for complete. The **order** scan (the create signal) branches on the replenishment system:
**Buy** The scan finds an open (`Draft` or `Planned`) purchase order for that supplier and adds a line for the kanban's quantity. If none exists, it creates a new draft PO. It applies the kanban's conversion factor, purchase unit, and storage unit to the line, then drops you on the purchase order.
**Make** The scan creates a job for the item at the kanban's quantity, copies the item's method onto it, and links the job back to the card. With **Auto Release** on, it releases the job: it recalculates its requirements, plans it, schedules the location, and marks it `Ready`. With **Auto Start Job** on, the operator goes straight into the first operation in MES.
**Transfer** The scan creates a `Released` stock transfer for the kanban's quantity, from the From storage unit to the To storage unit, then drops you on the transfer. Each scan creates a transfer.
HEADS UP **Auto Release needs the method copied** If the item's method could not be copied onto the job, the job stays `Draft` and linked to the card, and the scan opens the job page. Get the method on the job, then release it from there. **Start** and **complete** scans only apply to `Make` kanbans. They resolve the linked job's active operation and hand off to the MES operation start / complete screens, so an operator can drive the whole build from the same card that created the job. HEADS UP A `Make` kanban links to the job it created (`jobId`). If you scan **order** again while that job is still open, Alforse doesn't create a duplicate. It routes you to a collision screen that shows the existing job and offers to remove the link so a fresh scan can start over. Once the job is completed or cancelled, the link clears automatically and the card is free to fire again. ## Output format How a card is rendered is a per-company setting, **Kanban Output** (under **Settings → Inventory**), with three modes: | Mode | What a card is | | - | - | | QR Code | A scannable QR code, color-coded per action. | | Label | A printed PDF label with the QR, item thumbnail, name, storage unit, quantity, and supplier. | | URL | A copyable link that hits the same scan endpoint directly. | For `Make` kanbans, the list view also surfaces the **start** and **complete** affordances. `Buy` and `Transfer` kanbans show only the order signal, since there's no job to start. ## Kanban vs. reordering policy Both replenish stock, but they're different tools: NOTE **A kanban is a signal, not a plan** A [reordering policy](/docs/reference/reordering.md) is evaluated by the planning engine, which computes suggested orders from on-hand, demand, and reorder points. A kanban skips all of that: a scan creates a real purchase order, job, or stock transfer on the spot. Reach for a kanban when the shop floor pulls material by hand and you want the refill to be one scan away. ## Related **Inventory & locations** Where stock lives, the storage units a kanban refills, and how on-hand is tracked. [Open](/docs/reference/inventory.md) **Reordering policy** The planning-driven alternative: when and how much each part replenishes automatically. [Open](/docs/reference/reordering.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.