One purchase order does not necessarily equal one manufacturing lot. An OEM may request several deliveries while material, inspection dates or approved revisions change between releases. If every carton receives the same undifferentiated report, the customer cannot reliably determine which evidence belongs to the parts received.
The objective is a clear chain from the delivery to the physical kit, its configuration and the relevant inspection records. For OEM sheet-metal assemblies and kitted parts, that chain should be agreed before split shipments begin, not reconstructed when a receiving discrepancy appears.
Separate order, release, manufacturing lot and shipment
These identifiers answer different questions. The purchase order describes the commercial purchase. A release identifies a requested delivery or production instruction. A manufacturing lot groups production under the agreed lot definition. A shipment identifies what was actually dispatched.
The relationships can be one-to-many or many-to-one. A shipment may contain multiple lots; one lot may be divided between deliveries. Keep those relationships visible instead of forcing every identifier to share the same number.
| Record | Question it answers | Required connection |
|---|---|---|
| Order and release | What configuration and quantity were requested? | Part number, revision and delivery instruction |
| Production lot | Which manufactured items are grouped together? | Agreed lot definition and process records |
| Inspection report | What was checked and with what outcome? | Lot, sample identity, method and actual scope |
| Packout and shipment | Which accepted items were sent? | Container identity and contributing lots |
Freeze the configuration for each release
List the assembly BOM and relevant component revisions. A kit may contain several part numbers with different revision histories; writing only the top-level revision can hide a component substitution.
Before production, resolve mismatches among the order, drawing package and accepted quotation. When a change occurs, define its effectivity: which releases or lots use the old configuration and which use the new one.
Do not change the header on an old report and reuse its measurements for a later revision. Retaining earlier baseline evidence may be appropriate, but the new report must distinguish that reference from inspection actually performed on the current lot.
Make the inspection coverage explicit
A report should identify which characteristics were checked, the sample or item identities and the inspection stage. State whether the record covers a first article, a sampled lot check, an agreed full inspection or a particular assembly verification.
An inspected sample is not proof that every shipped item was individually measured. Conversely, a full-presence hardware check does not necessarily mean every dimension received full inspection. Use precise descriptions of the agreed scope.
For a mixed-lot delivery, provide a report index that lists the contributing lots and applicable documents. This can be more useful than merging unrelated results into one spreadsheet.
Link deviations to their authorized limits
If an exception is approved, identify the affected characteristic, configuration and permitted scope. Connect the approval to the relevant lot or release, including any quantity or validity boundary specified by the customer.
A supplier should not carry an exception from a pilot kit into future production by default. If the next release still requires it, obtain the appropriate decision before relying on the earlier approval.
Design receiving records for the buyer’s workflow
Agree whether the customer wants one document package per shipment, release or production lot, and how container identification should be presented. Specify file naming, delivery timing and the method for corrected records.
A corrected report should retain a reason and identifiable revision. The buyer needs to know whether a typographical error was corrected, a missing record was supplied or physical parts were reinspected. Those are different events.
The SAP scheduling-agreement overview illustrates delivery schedules containing individual quantities and dates. An inspection package needs similarly explicit connections, even when the buyer uses a simpler ordering system.
Test the chain with one simulated receiving question
Before the first split shipment, select one planned container and ask: which revision is inside, which lot produced it, what was inspected, and where is any approved exception? Then work backwards from one report to the physical items it covers.
Our split-delivery customer project describes a specific kit and record-control application. Its results belong to that project; the structure for your program should follow your own configuration, sampling and receiving requirements.
The goal is not a larger document pack. It is evidence that remains understandable after an order has been divided, revised and delivered over time.
Need a Custom Sheet Metal Quote?
Send us your CAD drawings — DRAmetal's initial response target is within 24 working hours. Quotation, DFM and lead-time timing depend on file completeness and engineering scope.
GET A FREE QUOTE →
