Take the snapshot.
Keep its meaning.

A download begins with a deliberately selected report.

A manager comparing the shop’s recorded position needs the report they reviewed, not whatever inventory happens to look like when a colleague opens a file. Troctolite’s inventory export starts beside one selected saved snapshot. Opening the workspace does not choose the first report, create another snapshot or start a download.

An owner, admin or manager first reads the complete saved position, then explicitly requests its ZIP. The selected identity and reviewed report must match throughout preparation and download. Reading a different report pauses the earlier export control. If that new read fails, the last report may remain visible as a reference; explicitly re-read that original before exporting it again.

The new-report label and note remain a separate working draft. Export neither saves those fields nor resolves an uncertain creation request. Keep an interrupted creation’s workspace open and check its original metadata receipt; downloading another saved report does not prove whether that creation completed.

Four pieces should not become one misleading total.

Consider a hypothetical saved position with four jewelry records. A ring has a USD asking amount of 625.0000. A chain has a EUR asking amount of 420.0000. A pendant has 300.0000 with no currency. A watch has USD 100.1250. These are illustrative recorded asking amounts, not current prices or a recommended valuation.

The exact source keeps all four raw amounts and their recorded currencies. The ring contributes USD 625.00 to supported exact-cent asking coverage; the chain contributes EUR 420.00 separately. The pendant’s currency stays unknown. The watch remains a fractional-cent exception instead of being rounded into the eligible USD sum. There is no blended 1,045.00 total, conversion or assumption that the uncovered rows are worth zero.

An explicitly recorded USD 0.0000 is different from a missing amount. It can count as a priced row while contributing 0.00. A missing amount remains missing, and no supported priced rows means that currency’s asking sum is unknown rather than an invented zero. Read coverage counts alongside every sum.

Later title edits, asking-price revisions, transfers and refining reservations do not alter the archive’s captured rows or status groups. “Available” remains a recorded state, not verified ownership or proof that a piece was physically in the showcase. A later download of the same unchanged saved report retains that same original position.

Use JSON for exact evidence and CSV for a readable view.

The ZIP contains exactly five files: report.json, items.csv, README.txt, manifest.json and SHA256SUMS. The JSON carries the complete validated frozen report and its original creation receipt. It is the authoritative source when a spreadsheet application changes a number’s appearance or interprets text.

The CSV presents every captured item row in a readable form, including raw recorded amount and currency, classification and record-age context. It is not a filtered list of only well-populated or available pieces. The readme explains the scope and interpretation; the manifest and checksums describe and check the included file bytes.

A supported snapshot has zero to five hundred captured item records. A zero-row report still has its complete five-file package and a header-only item CSV. A larger store cannot be silently cut down to the first five hundred during snapshot creation, and export does not fill missing rows from current inventory. Unsupported, changed or unreadable evidence fails as a whole.

A SKU that resembles a formula is still recorded text.

Jewelry identifiers and descriptions can resemble spreadsheet formulas, dates or numbers. An identifier such as =RING-104 or a zero-prefixed code should not become a calculated value merely because someone opens a row view. Every CSV data cell therefore receives one protective apostrophe prefix, including numbers, flags and empty values. Fields are quoted, with explicit null flags to distinguish unknown from empty recorded text.

That protection makes this a text-oriented review file. A spreadsheet may display the apostrophe, import numbers as text or require explicit import choices. Do not treat the CSV as a ready-made financial workbook, silently strip the prefixes and then assume the original protections remain. Import settings, copying and manual edits can change appearance or interpretation; there is no promise that every spreadsheet behaves identically.

For an exact comparison, return to report.json and the saved report’s breakdowns. Never infer a legacy currency from the current store setting, promote an unsupported raw amount into a priced row or combine the separate currency coverage to make a more convenient total.

Review the private contents before handing them over.

The archive includes recorded asking amounts, saved explanatory notes and recorded operator attribution. It is not redacted or encrypted. Consider the actual contents and intended recipient before sharing it, including anything a staff member placed in a title or note. Download authorization does not make the resulting file safe for public posting.

Access is checked for an owner, admin or manager in the report’s recording store. The selected report remains historical when current items move, but another store does not gain its priced archive merely by receiving one of those pieces. A demoted operator’s own creation-metadata recovery is narrower than a full report read or export.

The client checks selected identities, the expected report, complete length, ZIP response and archive checksum before requesting the browser download. Failed or canceled preparation produces no partial download and does not retry automatically. Preparation is audited; that audit does not establish that a browser received, saved or opened the file. Checksums support byte consistency, not a digital signature, authenticity finding or external certification.

Take a recorded position, not an accounting conclusion.

Evaluate with an empty report and a representative jewelry roster containing unknown amounts, explicit zero, both supported currencies, a fractional-cent exception and reserved or transferring items. Change a current title or price afterward, then read the saved source again. Check that row counts, original raw values and separate currency coverage remain fixed.

Created-record age measures elapsed time from item-record creation at the report’s captured time. It does not establish acquisition date, shelf age or turnover. Asking coverage is not asset value, expected proceeds, cost, profit or margin. The archive contains no photographs, other reports, current customer details or live item enrichment, and opening it performs no stock or money action.

This is a single selected inventory-position evidence export. It is separate from selected estimate and resale-worksheet exports, count and transfer records, accounting integrations and a complete migration packet. Bring a difficult legacy row to a walkthrough and decide what the saved evidence can actually answer.