Accepting a product-level trace creates a trace record — a batch with its own lot code, listed in Batches/Orders and marked Auto in the Type column. Each trace is kept, so what a product claimed on an earlier date stays available.
A record's page lists every product covered, with items nested under their style, and names its origin as either the assessment it came from or an integration sync, linked both ways. The lot resolves publicly, and digital ID links can be generated for a record exactly as for a purchase order.
On a product, the batch selector lists past records by date and source with the newest marked Current, so switching between them shows what each trace recorded. In the products list, a product under an open trace shows its trace number, so products in the same trace are identifiable as a group.
An integration sync that re-sends identical data creates nothing. A sync that changes one product's traceability creates one record containing only that product.
Records begin at deploy — products traced before then have no history. Purchase-order-backed traces are unchanged, as they already had a batch, and traceability edited directly on a product does not create a record. Records stay editable by an admin: nothing automatic overwrites them, but they are not locked.
