Use Batch, Expiry, IMEI, and Serial Tracking in SalePro

Enable the appropriate product identity before receipt. Record batch/expiry or IMEI/serial data on the purchase, then select the same identity when stock leaves.

Enable batch/expiry or IMEI/serial tracking on the product before the first tracked receipt.

For an IMEI/serial line, the submitted identifier count must match the unit quantity expected by the workflow. Identifiers are treated as opaque values after whitespace/delimiter normalization; do not reuse an identifier already sold, returned, or allocated in an incompatible state. A batch selection must belong to the same product/variant and authorized warehouse and have enough remaining quantity.

Effects#

• Batch quantity belongs to a product and warehouse context.
• Sale deletion or an eligible return restores the exact recorded identity. A return cannot use a foreign sale line, product, variant, batch, or serial, exceed unreturned quantity, or return the same serial twice.
• Imported FIFO layers also retain product, variant, batch, and IMEI identity where the consuming workflow supports it.

Limits#

Batch/expiry fields do not guarantee automatic FEFO picking or a universal hard block on expired stock. Legacy IMEI storage is text-based and does not provide per-identifier specific costing or multiple normalized identifier types. Damage, Production, Repair, and combined Exchange reject imported/tracked identities they cannot preserve. Deleting a return can also be blocked if its restored serial has already been resold or historical duplicate identity makes reversal ambiguous. A rejected operation does not change stock or accounting.

See Returns and exchanges, Import and landed cost, and Inventory operations.