A location is part of the record.
Staff begin with an authorized organization and store. A membership in one organization does not widen access in another. The active location is checked on the server; a store ID in a request does not grant permission.
Current item custody matters for private image access. When a controlled same-organization transfer changes the item’s location, the old store loses its item-photo access and the authorized destination follows the retained evidence. The capture location remains part of its provenance.
Historical estimates stay with the location that saved them. Their frozen photo references do not create a new path around current binary access. Viewing an old record and accessing a current private original are separate authorization decisions.
Keep an original instead of an editable memory.
Each saved estimate records its calculation operands and results, quote basis, inspection and photo manifest. A later estimate revision appends a record rather than editing an earlier original. An independent scenario starts a new family.
Legacy records remain explicit about missing history or evidence. The app does not infer families from dates, names or similar amounts. A newer photo is not silently attached to an old estimate, and unknown historical currency is not replaced by the active store currency.
History is read in location-scoped pages of up to fifty explicitly linked records. Older and Newer controls change the history page while keeping the viewed original, working inputs and chosen parent in place. A refresh starts from the latest records; it does not adopt a new parent. Full family export remains future work.
Preserve the operands behind the amount.
The gold calculation uses decimal arithmetic, canonical measurement precision and the quote’s supported decimal price. Payable cash behavior is tested separately with integer-cent reconciliation. A polished amount display alone would not establish those controls.
Source review keeps changes visible. The current UI binds a new save to the reviewed deduction, gold facts, inspection and photo manifest. If that basis changes while the save waits, it returns for review without replacing typed inputs.
Quote, source and head checks have different jobs. A new version must use the reviewed current basis. An already accepted keyed retry instead returns its original record before looking at newer sources, so a lost response does not create another estimate.
Keep photos useful and private.
Private JPEG/PNG originals retain their file hashes. The app renders a separate normalized preview and serves the original through an authorized attachment route. The operator-reported capture time remains distinct from server recording time.
Up to six photos per item are supported, with four-MiB and twelve-million-pixel input limits. The server decodes files within bounded processing limits. PDF upload, governed removal and retention administration are not supplied by this photo slice.
None of this verifies authenticity or certificate facts. A photograph is evidence that was recorded, not an automatic conclusion about the object.
Take one saved estimate with its context.
The evidence export gives authorized managers a ZIP for one selected saved estimate. The record-only option contains frozen data, lineage, a manifest, a readme and checksums. Original photographs are an explicit option and require current authorized custody and an exact match to the saved photo references.
If an original cannot be included safely, the full-photo request fails rather than silently returning a partial archive. A separate record-only download can still preserve the historical facts. It does not fetch the newest customer contact information or substitute a later photograph.
The packet is a neutral estimate record. It is not a signed agreement, an appraisal, a compliance filing or a full store migration. Keep its private notes and attribution with the appropriate record.
Controls still need operational acceptance.
Unsupported regulated production buying and pawn execution remain disabled. Recorded setup checkboxes do not turn them on. Ticket, payout, reporting and hold behavior must be supported for the actual operator and jurisdiction before a pilot can rely on that path.
Runtime AI is also inactive. The prepared listing-assistance foundation does not autonomously authenticate an item, set a price or change ownership. Availability is listed separately so you can evaluate the product against the work your shop needs today.
Source, offline interaction and isolated HTTP/database checks provide engineering evidence. Rendered-browser acceptance and comparative operator benchmarks remain outstanding. Bring your permissions, exceptions and reconciliation questions to the walkthrough.