Stock Transfer Batch Feasibility Evidence

Review a proposed inventory-transfer batch before rekeying it or importing it into another system. This Actor checks supplied arithmetic across exact SKU, location and unit keys, keeps reserve floors explicit, and records why a transfer cannot be resolved. It accepts authorized snapshot and transfer exports as JSON arrays or mapped CSV. It does not connect to an ERP, reserve stock, approve a shipment or move inventory.

The report is useful when several outlets draw from the same source, when one proposed transfer is intended to fund a later transfer, or when exported snapshots contain missing, duplicate or mismatched records. One report covers the complete supplied batch. A successful Actor run means the evidence report was produced; it does not mean every proposed transfer is feasible.

Choose the execution model

• simultaneous-outbound: All outgoing quantities for a source key are aggregated and compared with its starting available quantity minus reserve floor. Incoming stock cannot fund outgoing stock in this model. Two individually small transfers can both be flagged when their shared source is oversubscribed. Cycles cannot create starting stock.
• ordered-immediate: Transfers are evaluated in ascending, unique integer sequence. Each feasible leg immediately debits its source and credits its destination in the supplied model. An invalid, insufficient or unresolved leg makes both touched balances unknown. Later dependent legs remain unresolved; the Actor never assumes a failed movement was simply skipped. Unrelated stock keys can retain known evidence.

The model is your explicit assumption. Neither model establishes actual transaction timing, warehouse concurrency, reservations or physical availability.

Input

Set snapshotId, snapshotCoverage (complete or partial) and executionModel. Coverage is a caller declaration; a missing stock key remains unknown even when you declare complete coverage.

Inventory rows contain rowId, sku, locationId, unit, availableQuantity, reserveFloor and snapshotId. Proposed transfer rows contain rowId, sku, fromLocationId, toLocationId, unit, quantity and sequence. Both models require unique integer sequences; only the ordered model uses them to update balances. Keep identifiers as exact strings: 001 differs from 1, and units or case are never converted. Identifiers cannot have control characters or leading/trailing whitespace. Row IDs must be unique within each table. Duplicate current-snapshot stock keys are unresolved even when their quantities agree. Other-snapshot or other-unit records are retained as related evidence and never substituted.

Quantities are decimal strings with up to 18 integer digits and six decimal places, such as 0, 12 or 0.125. Use no commas, exponent notation, signs or leading zero padding. Transfer quantities must be positive. Invalid bounded quantity strings appear as findings; numeric JSON quantities and malformed row structures fail input validation. Arithmetic uses exact six-place decimal integers, without floating-point rounding. Values are never totaled across unlike SKUs or units.

For CSV, remove the corresponding array and supply nonempty inventoryCsv or transfersCsv. Canonical headers match the row fields above. Optional inventoryColumns and transferColumns map every field to a distinct header. BOMs and quoted cells are supported; missing, duplicate or extra headers and irregular rows are rejected. A header-only CSV is an explicit empty table. The total input limit is 4 MB and 2,000 combined inventory and transfer rows. Dense evidence can reach output limits sooner; split such batches.

Reading the output

The default dataset has one complete report with retained inputs, rows, balances, findings, scope and summary. Transfer rows are feasible, infeasible, unresolved or invalid. A feasible row describes that leg's supplied arithmetic, not approval of the whole batch; check reviewRequired and all ending balances. Simultaneous ending balances at failed or uncertain legs are unknown because no actual execution subset is established. Ordered row balances describe that sequence prefix; the final balance table reflects later taint as well. Empty transfer input produces no_transfers, never a clean-stock conclusion.

Download full JSON, transfer evidence CSV, exact-key balances CSV, findings CSV and standalone HTML. Source references such as inventory[0] and transfers[0] point to the retained original zero-based positions. JSON retains exact identifiers. CSV neutralizes spreadsheet formulas; HTML escapes supplied text, has no scripts or external resources, and should be downloaded using the attachment link.

Price, recovery and limits

The Store configuration is $0.25 per completed report, with platform usage included, charged once through report-completed. Invalid input, insufficient report budget or an oversized report produces no completed-report charge. Downloads are written before publication. Resurrecting a run verifies its saved report and input fingerprint, restores missing exports, and keeps one dataset item and one charge. A new run is a new billable report. Partial files left by an interrupted uncharged run can be overwritten on recovery; they are not a delivered report by themselves.

Use only authorized, opaque identifiers. Raw inputs and results are stored in Apify and can expose operational quantities; do not provide contact details or secrets. This tool makes no live-stock, demand-forecasting, optimization, unit-conversion, shipping, valuation, compliance or platform-import acceptance claim. It produces bounded supplied-data evidence for your review.