For a PR-kit project going to multiple addresses, prepare one controlled delivery list that connects each allocation ID to an approved kit version, quantity, destination, shipment-unit reference and release status. Confirm the required address format and shipment information with the party arranging delivery before creating labels. Keep the approved pack specification separate from recipient details, but join the records through stable IDs.
Image note: the featured image is an AI-generated Pliapack concept of a PR kit with an outer carton. It is not a customer campaign, actual shipment or evidence of transport performance.
Use a delivery allocation ID as the joining point
A recipient name is a poor record key: one contact may receive several kits, a company may use several locations, and the destination may change. Give each allocation its own ID and retain that ID when its details are corrected. The PR kit variant-control guide defines which kit version belongs to an allocation. The delivery record carries that decision forward to the outgoing shipment.
Separate the number of kits from the number of parcels. One allocation may need several shipment units, or several kits may share one outer carton. Define that relationship after reviewing the actual packed configuration. Do not assume that one spreadsheet row, one kit and one carrier label always mean the same thing.
Agree the fields before collecting the list
| Record group | Suggested information to agree | Check before release |
|---|---|---|
| Allocation | Stable ID, kit version and number of kits. | The version exists and the quantity reconciles with the packing plan. |
| Destination | Recipient or organization, address lines, locality, region, postal code and country as applicable. | Required fields match the chosen destination and delivery provider. |
| Delivery contact | Only the contact details required for the agreed delivery work. | The responsible team has confirmed the details and intended use. |
| Shipment units | Parcel or carton reference, relationship to allocation and contents quantity. | Every released kit is accounted for in the shipment-unit record. |
| Label and dispatch | Label reference, release status and dispatch or tracking reference when available. | Labels point to the current destination and the correct physical unit. |
| Exceptions | Hold reason, decision owner and record revision. | Held work cannot be mistaken for an approved dispatch. |
These are planning fields, not a universal carrier template. Ask the delivery provider which fields, formats and product information it needs for the proposed countries and route. Where cross-border documentation is required, assign its preparation and approval explicitly. The address list alone does not establish that the shipment is ready for acceptance.
Check completeness without inventing missing information
Preserve postal codes, telephone prefixes and identifiers as text when moving data between files. Check the exported file as well as the working sheet so formatting changes are caught before label generation. Keep address lines separate in the format requested by the delivery provider.
Flag blank required fields, inconsistent country names and apparent duplicates for the list owner. Two rows with the same address may be intentional; two similar names may refer to different recipients. Ask for a decision instead of merging records or guessing a missing unit number. Share recipient details only with the parties that need them for the agreed work, through the agreed transfer method.
Reconcile allocations, packed kits and shipment units
Compare totals by kit version first. Distinguish allocations ready for release from those on hold, then compare released quantities with the available packed sets. Keep retained samples and other non-delivery allocations visible. A single overall total can conceal a shortage of one kit version and a surplus of another.
Illustrative example: allocation D014 requests two kits. The agreed outer-packing arrangement uses one kit per parcel, so it creates shipment units D014-01 and D014-02. Both point to the same approved destination record. The handoff record needs to account for both parcels, even if their tracking references become available at different times. This is a data example, not a shipping commitment or prescribed packing method.
The physical packing sequence belongs in the pack-out instruction. The delivery record should identify its output without copying assembly directions into every recipient row. Review the agreed handoff condition as part of the kitting and pack-out scope.
Control address changes after labels are prepared
Name a list owner and identify the revision approved for label creation. Agree a change process with the party arranging delivery, including how it will confirm whether a requested change can still be applied. No universal cutoff should be assumed.
For a change, record the allocation ID, replaced revision, revised details, approver and affected shipment units. Confirm whether labels already exist or goods have been handed over. Where a label is replaced, identify how the obsolete one is removed from use. Editing a shared address cell without notifying the dispatch owner leaves a physical label disconnected from the current record.
Close the record at the agreed handoff
- Released allocations reconcile with packed quantities and identified shipment units.
- Each label uses the approved destination revision and is matched to its physical unit.
- Holds, cancellations and unresolved records remain distinguishable from released work.
- The handoff evidence identifies what was transferred and which dispatch references are available.
- A named owner receives later exceptions and can link them back to the allocation ID.
A dispatch reference records a shipping step; it does not by itself establish successful delivery. Agree what later status information will be shared and who handles exceptions. For PR kit and launch packaging, Contact Us with the destination countries, address count and proposed kit split to discuss the packaging and delivery handoff scope.
