Linked warehouse record examples
Fictional scenario for 2026-10-01 to 2026-10-06

Purpose and source
These four filled CSV files demonstrate how the existing blank planning templates can describe one connected warehouse workflow. All quantities, dates, SKUs, prices, tracking references, photos, approvals and other evidence references are invented. They are not customer records, actual warehouse results, carrier evidence or Amazon, Walmart or Shopify platform data. No EX- approval, release or evidence reference is a real permission or a document supplied for use with your goods.

Files
- receiving-example.csv uses the full receiving-record.csv header, in the same order.
- dispatch-example.csv uses the full dispatch-record.csv header, in the same order.
- stock-example.csv uses the full stock-balance-record.csv header, in the same order.
- order-parcel-example.csv uses the full order-parcel-record.csv header, in the same order.
Use the separate blank templates for your own records. Replace the fictional identifiers and evidence references through your agreed reporting workflow. These files are not marketplace or carrier upload formats.

Import without losing identifiers
The files use UTF-8 with a BOM, comma-separated fields and CRLF line endings. Import through a CSV/text import dialog, rather than relying on automatic conversion when double-clicking a CSV. Select Text for SKU, carton number, order line, batch, tracking and every reference or version column. Preserve SKUs 000101 and 000102 and cartons 0001 and 0002 exactly. Import date and event-time fields as Text to retain ISO dates and the +08:00 timezone; convert them deliberately only if your reporting system requires it. Counts, measurements and amounts can be imported as numbers. CSV has no stored cell types or formulas, so quotation marks alone do not prevent spreadsheet software from removing leading zeros.

Receipt reconciliation
Location: EX-LOC-01. Batch for the stock balance: EX-BATCH-01. Purchase order: EX-PO-01. Opening physical stock is 0.
- EX-RECEIPT-01 on 2026-10-02: SKU 000101 expected 50, received 50. SKU 000102 expected 30, received 30.
- EX-RECEIPT-02 on 2026-10-04: SKU 000101 expected 20, received 20.
Expected quantities describe the agreed delivery on that row, not the total purchase order repeated on every row. The two receipts total 100 units: 70 of SKU 000101 and 30 of SKU 000102. A recount would revise the same receipt, rather than create an additional receipt. The receiving template has no batch column; this scenario assigns both receipts to EX-BATCH-01 in the stock balance.

Two cartons, one completed dispatch
EX-SHIP-01 records the actual carrier handoff on 2026-10-06.
- Carton 0001: SKU 000101 30 units and SKU 000102 20 units. The finished carton is 40 x 30 x 20 cm and 12 kg. Measurements appear on the first SKU row only.
- Carton 0002: SKU 000101 10 units. The finished carton is 20 x 20 x 20 cm and 3 kg.
The shipment contains 60 units in 2 cartons. Packed gross weight is 12 + 3 = 15 kg. Packed volume is (40 x 30 x 20 + 20 x 20 x 20) / 1,000,000 = 0.032 CBM. Count unique shipment/carton keys before counting cartons, weight or volume. Product-label files and their versions are separate from marketplace receiving labels. This fictional shipment is a direct customer shipment, so the platform identifier, marketplace receiving-label and shipment-plan fields are NA.

Two parcels for the same order
Order EX-ORDER-01 has two parcels, both actually handed over and physically scanned on 2026-10-06.
- EX-PARCEL-01 maps to EX-SHIP-01 carton 0001 through EX-TRACK-01. It contains line EX-LINE-01, SKU 000101 30 units, and line EX-LINE-02, SKU 000102 20 units. Delivery is recorded at 2026-10-06T16:00:00+08:00.
- EX-PARCEL-02 maps to EX-SHIP-01 carton 0002 through EX-TRACK-02. It contains a further 10 units of the same EX-LINE-01, SKU 000101. delivered_at is unknown and parcel_status is in_transit.
EX-LINE-01 therefore totals 40 units across the two parcels; EX-LINE-02 totals 20. Every row records total_parcels_in_order = 2. The parcel template has no shipment/carton column, so retain this explicit mapping when using the example. A delivered first parcel does not make the whole split order delivered. The second parcel still has no confirmed delivery event.
Dimensions, gross weight and shipping amounts appear once per unique parcel, on its first SKU row. The other SKU row in EX-PARCEL-01 intentionally leaves these cells blank. The shipping quote totals 12 + 5 = 17 USD. Billed shipping totals 13 + 5.5 = 18.5 USD, a difference of 1.5 USD. These are invented parcel-level shipping amounts, not prep charges or a current carrier price. Repeated order lines do not add another parcel or another fee.

Stock balance after the same physical handoff
- SKU 000101: 0 opening + 70 received - 40 dispatched - 0 completed removal + 0 signed adjustment = 30 physical units. Held 5 + reserved 4 + available for release 21 = 30.
- SKU 000102: 0 opening + 30 received - 20 dispatched - 0 completed removal + 0 signed adjustment = 10 physical units. Held 2 + reserved 3 + available for release 5 = 10.
Closing physical stock totals 40 units: 30 + 10. Held, reserved and available are mutually exclusive subsets of that same physical stock, not extra quantities. Incoming not received is a separately recorded confirmed 0 for both SKUs. The EX-STOCK-REVIEW-01 reference is fictional and illustrates the review of these balances and buckets.
source_record_references links the actual-receipt rows in this scenario and the completed EX-SHIP-01 handoff. Dispatch and parcel rows describe the same physical departure. Do not deduct or total their quantities twice, and do not add their matching 15 kg / 0.032 CBM transport measurements as two separate shipments. Labels, preparation or release approval alone would not reduce physical stock.

NA, unknown, blank and zero
- NA means confirmed not applicable within this fictional scenario: there was no extra receiving rework quote or product change, no stock adjustment, no parcel exception, and no marketplace receiving label or shipment plan. It does not mean pending approval.
- unknown means a required fact has not been confirmed. EX-PARCEL-02 has no confirmed delivery time. It must not be interpreted as delivered or as zero delay.
- A blank is intentional only for repeated carton/parcel measurements and parcel shipping amounts on the second SKU row of the same physical carton or parcel. Refer to the first row for that unique key.
- 0 is a known zero: opening, affected units, completed removals, signed adjustments and incoming not received in this scenario. It does not substitute for an unknown quantity.

Use your actual approved scope, current versions, measured packed dimensions, completed events and traceable evidence when completing your own records. Do not copy the fictional approval or evidence references as proof.