Keep the position.
Explain the gaps.

A store position starts with a complete population.

A manager looking across a jewelry shop needs a stable answer to a simple question: which item records belonged to this store when the report was created? A live search cannot hold that answer still while staff receive a transfer, sell a piece or prepare a refining lot. An inventory position snapshot records the bounded population once and keeps that original readable.

The supported snapshot contains zero to five hundred current item records from the active store, across their recorded statuses. A larger population rejects the whole request. There is no hidden first-five-hundred report, filtered subset presented as complete or combination of live inventory pages. An empty store can have an empty snapshot with explicit zero counts.

An owner, admin or manager chooses a label and explanatory note, then explicitly creates the report. The saved result is separate from the next report form. Creating another position makes another independent record; it does not revise the first one, mark anything counted or change a piece’s state.

The ring, the chain, the pendant and the watch.

Imagine four hypothetical item records in one shop. A ring is available with a recorded USD asking amount of 625.00. A chain has been reserved for whole-item refining preparation and carries a recorded EUR asking amount of 420.00. A pendant has a legacy amount of 300.0000 with no currency. A watch has a recorded USD amount of 100.1250.

The status view keeps the ring’s available state separate from the chain’s reservation. It does not promote the reserved chain into available stock because the report includes it. If a piece is recorded in transit or on hold, that state also stays visible. The snapshot is an account of recorded position, not a new decision about eligibility.

The asking coverage tells a different story. The ring’s exact-cent USD amount and the chain’s exact-cent EUR amount belong in separate currency breakdowns. They never become a mixed total of 1,045.00. The pendant’s currency remains unknown. The watch’s extra fractional cents remain a quality exception rather than being silently rounded into an eligible asking sum.

All four recorded rows still matter. A manager can follow the original raw amount and recorded currency alongside the coverage result. The report does not fix the pendant or rewrite the watch. A deliberate asking-price revision is a separate controlled action on an eligible current item.

A small asking total can mean incomplete coverage.

Asking amounts answer what was recorded as an asking price. They do not establish what a customer will pay, what the shop owns, what it originally spent or what it will retain after fees, repairs or taxes. A snapshot does not pull a melt estimate, component study or resale worksheet into an inventory valuation.

Read the coverage counts before the subtotal. Unknown amounts, unknown currencies, unsupported currency codes, negative or otherwise unsupported values and non-cent precision need their own visible treatment. Unknown is not a zero-price item. An explicitly recorded zero is different from no amount, and a valid zero may contribute zero while still counting as covered.

USD and EUR exact-cent asking coverage is kept separate. There is no currency conversion, blended asset-value figure or implied margin calculation. A raw legacy amount remains available for review even when it does not qualify for those sums. That helps an operator identify what needs attention without changing historical evidence to improve the appearance of the report.

The age of a record is not the age of the stock.

The report groups created-record ages at its captured time. That can help a manager notice long-standing records or a recent intake of records, but the meaning needs care: the creation timestamp is when this item record was created. It is not a documented acquisition date, physical arrival date, shelf date or continuous period owned by the shop.

A migrated estate ring can have a new record for an old piece. A transferred chain can be physically new to the destination while retaining an older creation time. A repaired description does not make the inventory younger. Treat the age buckets as record-management context and read the frozen timestamp rather than calling them stock turnover or aging receivables.

The population and summaries are fixed to this one snapshot. Later transfer, reservation, asking-price change or title edit does not recalculate the saved report. To inspect the new position, explicitly create a new report with a note that explains why it was taken.

Read the original instead of refreshing it into a different report.

The workspace keeps the recent twenty report summaries separate from a selected complete saved snapshot. An older authorized report can be opened directly. Its rows and breakdowns remain the recorded version; a list refresh does not substitute current item data or select a new report automatically.

An interrupted creation response is handled as an unresolved original request. The page keeps that request while the operator edits the next label or opens another report. Checking the original confirms its metadata; opening its priced report is a separate authorized read. A demoted operator may recover their own original request metadata without receiving the report’s rows or asking amounts.

Recovery is available while the workspace remains mounted. It is not offline storage or hard-reload recovery. A missing confirmation does not prove the report was never created, and the interface does not automatically issue a replacement creation request.

Use a position report alongside the checks it does not replace.

Start an evaluation with a small representative store: a new unpriced record, an explicit zero, an unknown legacy currency, both supported currencies, a fractional-cent amount and a reserved or transferring piece. Check the captured rows, status counts, coverage exceptions and record-age labels together. Then change an eligible current record and confirm the old snapshot stays unchanged.

Use count evidence for available-at-start expected tags and observation exceptions. Use the transfer desk for a physical handoff record, and preparation lots to reserve intact pieces before outside refinery work. None of those records independently proves ownership or physical presence, and this report supplies no automatic stock correction.

The current slice is a single-store immutable inventory-position report with bounded completeness. Consolidated multi-store reporting, accounting valuation, cost and margin reporting, scheduled reports, physical verification and full operational acceptance remain unfinished. A selected frozen report now has its own bounded evidence export. Bring the awkward legacy row to a walkthrough; it is often more useful than a perfectly populated demonstration.