Pluck glossary
Plain-language definitions for common Pluck terms used across inventory, orders, labels, and support.
Help updated for v0.10.21 · 2026-07-13
Inventory terms
Asset ID The operational code Pluck uses to identify one serialized item.
Assigned to The active holder or commitment for an item, such as an order, employee, kit, or maintenance job.
Barcode A scannable one-dimensional code, often used for Asset IDs or Type IDs.
Bulk inventory Quantity-based stock where the exact physical unit usually does not matter.
Category The broad family a type belongs to.
Consumable Stock that is used up, sold, or depleted rather than returned as the same unit.
Current warehouse Where Pluck currently believes an item or quantity lives.
Department The internal team, department, or operational group responsible for the record.
Expendable A consumable-style item that may be issued or billed but is not expected back as rented inventory.
Generic Asset ID A printed or reserved ID that may not belong to an existing item yet.
Home warehouse The usual or default warehouse for a type, item, or stock record.
Inventory type The reusable definition of something the company rents, sells, tracks, quotes, or stocks.
Keyword Search language added to help users find a type when they do not remember the exact name.
Known asset A serialized item that already exists as a physical record in Pluck.
Manufacturer The brand, maker, or supplier associated with a type.
QR code A square two-dimensional code that can carry longer values or app payloads.
Serial number A manufacturer or physical serial value, when the item has one.
Serialized item One physical unit under an inventory type, usually identified by an Asset ID.
Status The operational state of an item, such as available, reserved, out, maintenance, or assigned.
Type asset tag A type-level code used for type labels, bulk/type scanning, and generic type ID workflows.
Type ID The operational code Pluck uses to identify an inventory type.
Warehouse A location Pluck uses for planning, picking, transfers, returns, and availability.
Inventory setup terms
Acquisition report A report that answers what was bought in a period and how much was spent.
Assigned kit A physical tracked kit built from a kit blueprint with specific component assets attached.
Batch add A workflow for creating several serialized items of one type at once.
Bundled item A suggested companion line added when a type is added to an order.
Category-backed option A bundle or estimate choice that starts as a category before a specific type is chosen.
Cost A type-level expected, replacement, or planning value; not always the same as price paid.
Generate quantity A batch-add mode where the user enters a count and Pluck creates that many rows.
Generated Asset ID An Asset ID Pluck fills from company numbering rules when the field is blank.
Kit blueprint A reusable component pattern for assembling a tracked kit.
Number padding The number of digits Pluck uses when formatting generated numeric IDs.
Optional bundle group A group of choices the user can pick from while adding a bundled type.
Per-unit price The acquisition cost for one unit.
Open kit A planned kit mode where expected contents are known from a blueprint, but the exact assets are resolved during picking.
Prebuild A reusable order preset that inserts normal order lines for common estimates and orders.
Prefix source The company setting that decides whether generated IDs use a shared company prefix, custom prefix, company slug, category slug, or no prefix.
Price paid The actual amount spent for an item, batch, or stock acquisition.
Purchase date The date an item or quantity was acquired.
Quantity to add The amount of bulk stock or generated records being added in one workflow.
Required bundle companion A companion line that normally comes with the primary type.
Scan batch A batch-add mode where the user scans physical items into the list before saving.
Total price The whole acquisition amount before Pluck splits it across units.
Order terms
Availability Pluck’s calculation of whether inventory can satisfy the order for the relevant dates.
Category allowance An estimate-only line that prices a category before a specific type is chosen.
Closed order An order that is complete and should generally be read-only except for controlled follow-up work.
Dispatch The stage where the order has physically left company control.
Estimate An early order stage for planning and customer pricing.
Expected back The date the team expects returned inventory to be reconciled.
Fulfillment The actual source chosen for a line, such as owned assets, bulk stock, kits, transfers, or cross rentals.
Line discount A discount applied to one line.
Line item One row on an estimate or order.
Locked rental duration A setting that moves the end date when the start date moves, preserving the same length.
Locked time Operational time considered unavailable even when it is not billed as customer rental time.
Order discount A discount applied to the order total or eligible subtotal.
Pick The stage where actual assets, kits, containers, or quantities are selected for the order.
Pick day The day the warehouse should physically pick the order.
Prep day Time before the rental start used to stage, test, clean, charge, or prepare inventory.
Rate override A user-entered rate that intentionally replaces the default type rate.
Rate term The pricing period, such as daily, weekly, monthly, weekend, or a company-defined term.
Recalculate Rebuild totals from the current dates, rates, discounts, and availability assumptions.
Rental duration The customer rental window used for availability and pricing.
Rental end The last customer rental date.
Rental start The first customer rental date.
Reservation A committed order stage where inventory should be protected for selected dates.
Return The stage where the company reconciles what came back.
Picking and packing terms
Container A case, cart, bin, tote, rack, or physical holder used to pack order items.
Container asset A container that is itself tracked as inventory.
Container mode New scans are packed into the selected container.
Continuous scanning Repeated scanner input keeps moving through the intended pick context without a mouse click after each scan.
Finish packing Stop directing new scans into the current container.
Inventory scan A scan-first operations page for lookup, warehouse moves, status changes, and item actions.
Move to container Change which container a packed item belongs to.
Multiscan A workflow designed for scanning many values quickly in sequence.
Packed item A line, asset, or quantity assigned to a container.
Packing record The record of what container exists, what it contains, which section it belongs to, and whether packing is finished.
Pick list The working list of what needs to leave for an order.
Picked Inventory has been selected for the order but may not have left the building yet.
Quick container A container record created during packing so the team can keep moving.
Scan Enter a barcode, QR code, Asset ID, Type ID, serial number, or supported app payload through scanner input or camera.
Section A grouping inside an order, often used for departments, rooms, systems, or show areas.
Successful scan Pluck understood the value and completed the intended action.
Unsuccessful scan Pluck could not find or use the value and should leave the user in the same workflow.
Print and support terms
Browser print dialog The print panel the browser can open through `window.print()`.
Calibration A guide print with outlines, position numbers, dimensions, or pitch marks.
Custom font A company-uploaded or selected font available to label templates when the subscription allows it.
Gutter marker A small reference printed in a safe area outside label cells.
Human-readable text Printed letters or numbers beside a barcode or QR code.
Label-cell marker A sheet reference that intentionally consumes a label position.
Label template The design for what appears inside one label cell.
Partial sheet Label stock where some cells have already been used.
Print dialog The Pluck dialog where the user chooses scope, template, sheet, and print behavior.
Print preview The app-owned page that renders final printable output before browser printing.
Quiet space The blank area a scanner needs around a barcode or QR code.
Report printout A document-style print view with safe paper margins.
Reprint Reopen the original planned print output so a failed physical print can be tried again.
Sheet definition The physical paper definition: page size, label size, rows, columns, margins, pitch, safe area, and orientation.
Starting position The first label cell Pluck should use on a sheet.
System print dialog The operating-system print panel a browser may offer as an extra option.
Template element One text, barcode, QR, image, or shape object inside a label template.
Tracked sheet A saved physical sheet reference with known used positions.
Maintenance and usage terms
Cadence The rule for when maintenance should be suggested.
Completed maintenance The job was closed and the item can usually return to normal workflow.
Maintenance Work that removes an item from normal availability until it is repaired, inspected, cleaned, tested, or returned to service.
Maintenance cost category A bucket for labor, parts, outside service, or other maintenance costs.
Maintenance history The record of previous jobs, notes, labor, parts, and costs.
Maintenance job The active record explaining why an item is unavailable and what needs to happen.
Maintenance order number The readable number used to identify a maintenance job.
Maintenance state The current condition of an item from an operations point of view.
Open maintenance Active maintenance work still needs to be resolved.
Send to maintenance Start a maintenance job from an item, scan workflow, return workflow, or maintenance screen.
Time-based cadence A maintenance rule triggered after a calendar interval.
Usage hours A meter-like value for equipment where operating time matters.
Usage-hour prompt A request for the user to record operating hours during pick, return, or maintenance.
Use-based cadence A maintenance rule triggered after a count of rentals, dispatches, returns, or other use events.
Support and history terms
Addressed issue A known issue that the changelog says was fixed or intentionally handled.
Archived Hidden from normal work without being immediately purged.
Audit log A structured record of an operational change.
Bug report The support workflow that captures what the user tried, expected, and saw.
Build number The version and commit information shown so support can identify exactly what code is running.
Debug context A safe diagnostic snapshot attached to a bug report.
Deleted Permanently removed only when the product explicitly says data will be purged.
Disabled A company, user, template, or feature is intentionally turned off.
History The record-level story of what happened to a specific item, order, customer, type, or maintenance job.
Internal error An unexpected app or backend failure that should guide the user toward a bug report.
Known issue A reported problem that has not yet been fully addressed.
Permission Individual user role access that allows an action.
Release notes User-facing notes about what changed in a shipped version.
Restore Bring disabled or archived data back into active use.