Orders and support

Which completed orders received a particular supplier lot?

Answer only from a crosswalk built out of actual receipt and dispatch records, never from order dates alone. Start with the named lot exactly as the supplier's records print it, link it to the goods-receipt records showing when and where it entered your stock, then follow each dispatch record that drew on that receipt to the order lines it fulfilled. Orders connected by that documented chain can be named as recipients; orders that merely fall in the same period cannot. Mark every missing link as untraceable rather than filling it by assumption, and let the authorized operations owner decide what the business states in response to the inquiry.

For: Authorized operations staff of a research-only merchant who must answer which completed orders were fulfilled from a named supplier lot.

Updated 2026-10-01

Anchor the map on the lot's receipt records

Begin with the lot identifier exactly as it appears on the supplier's documents and on your receiving records, preserving both if they differ. Record the receipt events: the date the lot entered your stock, the location that received it, the quantity received and the party it came from. The GS1 Global Traceability Standard describes receipt and dispatch traceability events as connecting identifiers, parties, locations and dates, and it describes lot and batch identification — the same structure your crosswalk needs, whether or not your records were built to that standard.

A design standard is not evidence about your lot. The standard explains how records can connect; it does not prove that your particular lot arrived when you think it did, that it was pure, or that your business complied with anything. And a supplier invoice by itself, however genuine, shows what you bought — not which orders later drew on it. The receipt anchor is the start of the chain, not the answer.

Follow dispatch records to real order lines

From the receipt, work forward through the records that consumed the stock: pick lists, packing records and dispatch events that identify the lot per parcel or per order line. Where your operation records lot at dispatch, each of those events names an order. Where lots were split across locations or combined into cases, the aggregation relationships matter — the GS1 standard describes recording them precisely because a lot's path is not always one-to-one. Preserve the original identifiers and event times at every step rather than rewriting them into a summary.

Expect the chain to break somewhere. If the warehouse recorded only the SKU at pick time and not the lot, the link from that period's dispatches to any lot is missing, and the correct entry is the location of the break — not an inference. An order placed while the lot was in stock is consistent with having received the lot, but consistency is not a connection, and this page does not let order date stand in for a dispatch record.

Mark the three outcomes honestly

Every completed order in the questioned period ends in one of three states. Linked: a documented chain runs from the named lot through receipt and dispatch to that order line. Excluded: the records show the order's dispatch predated the lot's receipt or drew on a different recorded lot. Untraceable: a link is missing and the order cannot be placed on either side. Each state names the records behind it, and the untraceable set is reported as untraceable — never quietly folded into the recipient set to make the answer look complete.

A finished worksheet does not prove complete traceability, product quality or recall readiness, and it cannot establish that unrecorded orders received the lot. Those are the unsupported conclusions this process is built to avoid. What it produces is a bounded, evidence-tied answer: this set is linked, this set is excluded, and this set cannot be resolved from the records that exist.

Decide what the business may state, and who decides

When the inquiry is a document-correction or traceability question from a supplier, partner or provider, the response should present the three sets with their reasons and name the missing records that keep the untraceable set open. The authorized operations owner decides what is sent; if the question carries recall, regulatory or legal weight, the obligations attached to it go to qualified review, because this worksheet establishes record linkage and nothing more. Do not let the desire to give a clean answer upgrade an untraceable order into a linked one.

If the underlying concern extends to what the public store says about lots, batches or product documents, that website question fits a Prism storefront review within an agreed scope. Confirm responsibilities, fees and terms before work; the review examines public representations, not your laboratory results.

Lot-to-order crosswalk

Use one crosswalk per named lot. Fill rows from genuine receiving, stock and dispatch records, using internal order references rather than customer details. Any row without a record is a marked gap, not a prompt to infer.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

Lot-to-order crosswalk. The last column is for temporary notes.
Record or checkWhat it settlesYour finding
Named lot and its identifiersThe exact lot or batch as supplier and receiving records print it, with any internal alias preserved.
Receipt events for the lotDate, location, quantity and supplying party establish when the lot could first be dispatched.
Stock period and locationsBounds which dispatches could have drawn on this lot and where it was held.
Dispatch events naming the lotPick, pack or shipment records that connect the lot to specific parcels or order lines.
Aggregation and split recordsWhere the lot was divided or combined, these keep the chain continuous instead of assumed.
Orders linked by the chainThe recipient set the records actually support — the defensible core of the answer.
Orders excluded by the recordsDispatches predating receipt or drawing on another lot clear these orders without guessing.
Orders with a broken linkThe untraceable set, each with the missing record named and an owner assigned to resolve or accept it.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.

Limits

  • The GS1 standard is a traceability design standard; it does not prove a particular lot history, product purity, certification or legal compliance.
  • A completed crosswalk does not establish recall authority, complete traceability, or that unrecorded orders received the lot. Refer recall and legal obligations to qualified review.
  • Never infer a lot from an order date or fill a missing link by assumption; an untraceable order stays untraceable until a record connects it.
  • Keep customer identities and full order records out of shared worksheets; use internal references.

Sources

  • GS1 Global Traceability Standard v2.0 — checked 2026-10-01. Receipt and dispatch traceability events connect identifiers, parties/locations, and dates. The standard describes lot/batch identification and recording aggregation relationships.
  • Prism solutions — checked 2026-09-21. Published support is a storefront review, processing preparation, and help with a provider's website questions. Scope, fees, and terms are discussed before work.

Get help with store operations

Need help with the order, email or fulfillment step itself?