Batch add and Asset IDs
How to add multiple serialized items, choose scan modes, and let Pluck generate Asset IDs safely.
Help updated for v0.10.21 · 2026-07-13
Choosing a batch add mode
Batch add is for adding several serialized items of the same type without opening the single-item form over and over. It should feel like the picking scanner: choose the type, choose the mode that matches the physical workflow, scan or generate rows, review the rows, and then create the records.
Use scan Asset IDs when every physical item already has its operational label and the serial number can be filled in later. Use scan serials with automatic Asset IDs when the manufacturer serial is the first thing you can scan and the company wants Pluck to assign the operational code. Use scan serial, then Asset ID when the user needs to capture both values in pairs. Use generate quantity when the user already knows the number of items and wants Pluck to prepare the rows without scanning each unit first.
Asset ID generation
Asset IDs are the operational codes people scan, print, and search. If a row is left blank and company Asset ID generation is enabled, Pluck can fill the next available number using the company’s configured prefix source, padding, and sequence rules. That is safer than making a user invent codes by hand, but the generated values still need to be checked before printing labels or saving a large batch.
Generation should never knowingly create a duplicate. When printing generic labels or creating new assets, Pluck should look for existing identifiers and move to the next available numeric value. If the company uses a slug-based prefix, the generated labels and batch-add rows should use that same prefix. If the company has no prefix mode, the generated value should not silently fall back to a generic Pluck prefix.
Purchase details and review
Batch add can also capture acquisition details. Use shared purchase date when the items came from the same purchase. Use total price paid when the invoice amount is for the whole group, or per-unit price when each item has the same cost and the total should be calculated. Those values support purchase-spend reports later, so they are worth entering while the paperwork is fresh.
Before creating the records, review the type, warehouse, status, generated Asset IDs, serials, purchase date, and price paid. If the batch also offers to print labels, treat that as a follow-up action rather than a required save step. The inventory records should be correct first; printing can happen after the rows exist and the user knows which labels need to be produced.