Complete Packaging¶
The complete packaging schema contains information regarding the complete packages that are used to create loads. These maybe created from a single component or a combination of components from the components schema.
Table¶
Column | Status |
Format | Notes |
---|---|---|---|
identifier | required |
String | A globally unique identifier. See identifiers section for information on how to construct this identifier |
name | recommended |
String | The name of this complete packaging. |
description | recommended |
String | A brief description of this complete packaging. |
externalIdentifiers | recommended |
Dictionary | A dictionary of identifiers that might be used to identify the complete packaging in other systems. For example: manufacturer’s own internal identifier, bar codes or global trade item number (gtin). To provide external identifiers please follow this format. {'externalIdentifierName1': 'identifier1', 'externalIdentifierName2': 'identifier2'} |
imageURLs | recommended |
List | URL(s) that links to a picture of the complete packaging. Please see the guidelines below on how to capture the image and name the URL. |
completePackagingConstituentsIdentifier | required |
List | The information regarding the consituents that are combined to create this complete packaging. The entries should be from the Complete Packaging Constituents Relationship List identifier. |
LOWcodeWOproduct | recommended |
String | The list of waste code for only the complete packaging, by itself (excluding the product). LOW code is synonymous with European Waste Catalogue Code (EWC). For example: an empty bottle would have a LOWcode of 15 01 02 . Please use Dsposal or legislation.gov to find the LOWcode. Note: The LOWcode can based on its combination with other components and the actual product contained in the complete packaging. Be sure to only include the complete packaging LOWcode and not the complete packaging with the product. If you cannot find the code or are uncertain please enter Uncertain . |
productType | recommended |
String | Information about the product contained in the complete packaging. The entry here should be drawn from the product type controlled list. |
componentContactWithProduct | required |
List | What components (if any) come into direct contact with the product before purchased by a consumer? If none of the components come into contact with the product use NA . |
LOWcodeWproduct | recommended |
String | The list of waste code for everything in the complete packaging. LOW code is synonymous with European Waste Catalogue Code (EWC). For example: an empty bottle would have a LOWcode of 15 01 02 . Please use Dsposal or legislation.gov to find the LOWcode. Note: The LOWcode can based on its combination with other components and the actual product contained in the complete packaging. Be sure to include the complete packaging LOWcode with the product. If you cannot find the code or are uncertain please enter Uncertain . |
onTheGo | required |
Boolean | Is the complete packaging often classed as packaging that will end up in street bins? Answer as: TRUE for yes and FALSE for no. |
householdWaste | required |
Boolean | Is the complete packaging often classed as packaging that will end up in kerbside collections? Answer as: TRUE for yes and FALSE for no. |
depositReturnSchemes | required |
List | Which countries support a deposit return scheme for this particular complete packaging? The entries here should be drawn from the deposit return scheme controlled list. |
completePackagingEndOfLifeRoutes | recommended |
List | The information regarding this complete packaging’s proposed end of life routes. The entries should be the complete packaging end of life routes identifiers. |
recyclability | recommended |
Boolean | Is the complete packaging recyclable (as determined by a reputable source)? Answer as: TRUE for yes and FALSE for no. |
recyclabilityClaims | recommended |
List | The information regarding this recyclability claims. The entries should be the recyclability claims relationship list identifiers. |
height | recommended |
Numeric | The height of the complete packaging. Please see the guidelines below on how to properly measure and report the height. |
heightDate | recommended |
String | The date that the height was last verified/measured. Use the format dd/mm/yyyy . |
width | recommended |
Numeric | The width of the complete packaging. Please see the guidelines below on how to properly measure and report the width. |
widthDate | recommended |
String | The date that the width was last verified/measured. Use the format dd/mm/yyyy . |
depth | recommended |
Numeric | The depth of the complete packaging. Please see the guidelines below on how to properly measure and report the depth. |
depthDate | recommended |
String | The date that the depth was last verified/measured. Use the format dd/mm/yyyy . |
volume | recommended |
Numeric | Using the height, width, and depth found using the measurement guidelines, calculate the complete packaging’s volume using: height x width x depth . |
volumeDate | recommended |
String | The date that the volume was last verified/measured. Use the format dd/mm/yyyy . |
weight | required |
Numeric | The weight of the complete packaging. |
weightTolerance | required |
Numeric | The threshold of weight that complete packaging can vary by. This can be given in grams or percentage. |
weightToleranceType | required |
String | Either grams or percentage based on the value provided in weightTolerance |
weightDate | recommended |
String | The date that the weight was last verified/measured. Use the format dd/mm/yyyy . |
servingCapacity | recommended |
Numeric | The serving capacity of the complete packaging - how much of a product that can be contained in the complete packaging. |
servingCapacityDate | recommended |
String | The date that the serving capacity was last verified/measured. Use the format dd/mm/yyyy . |
partOfMultipack | required |
Boolean | Is the complete packaging part of a multipack? Answer as: TRUE for yes and FALSE for no. |
certification | recommended |
Boolean | Does the complete packaging have a certificate (e.g. FSC, REACH, FSA etc.)? Answer as: TRUE for yes and FALSE for no. |
certificationClaims | recommended |
List | The information regarding the certifications. The entries should be the certification claims relationship list identifiers. |
updateDate | required |
String | The date that the complete packaging was provided/last updated. Use the format dd/mm/yyyy . |
releaseDate | recommended |
String | The date that the complete packaging will be available to use. Use the format dd/mm/yyyy . |
discontinueDate | recommended |
String | The date that the complete packaging will no longer be available to use. Use the format dd/mm/yyyy . |
Diagram¶
erDiagram
COMPONENTS }o--o{ COMPLETE_PACKAGING : within
COMPLETE_PACKAGING {
identifier String
name String
description String
externalIdentifiers Dictionary
imageURLs List
completePackagingConstituentsIdentifier List
LOWcodeWOproduct String
productType String
componentContactWithProduct List
LOWcodeWproduct String
onTheGo Boolean
householdWaste Boolean
depositReturnSchemes List
completePackagingEndOfLifeRoutes List
recyclability Boolean
recyclabilityClaims List
height Numeric
heightDate String
width Numeric
widthDate String
depth Numeric
depthDate String
volume Numeric
volumeDate String
weight Numeric
weightTolerance Numeric
weightToleranceType String
weightDate String
servingCapacity Numeric
servingCapacityDate String
partOfMultipack Boolean
certification Boolean
certificationClaims List
updateDate String
releaseDate String
discontinueDate String
}
COMPLETE_PACKAGING }o..o{ CONTROLLED_LISTS : attributes
COMPLETE_PACKAGING }O..O{ RELATIONSHIP_LISTS : attributes
COMPLETE_PACKAGING }o..o{ MULTIPACK : within
COMPONENTS }o..o{ MULTIPACK : within
COMPLETE_PACKAGING }o..o{ LOAD_CATALOGUE : within
MULTIPACK }o..o{ LOAD_CATALOGUE : within
COMPONENTS }o..o{ LOAD_CATALOGUE : within
CONTROLLED_LISTS {
productType recommended
depositReturnScheme recommended
}
RELATIONSHIP_LISTS {
completePackagingEndOfLifeRoutes required
completePackagingConstituentsIdentifier required
recyclabilityClaims recommended
certificationClaims recommended
}
Template¶
Complete packaging should be provided as a separate csv file. The specification of this csv file is as follows:
Example¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 |
|
Guide for how to take measurements¶
Units¶
All measurements should be given using the metric system.
- Height: millimetre (mm)
- Width: millimetre (mm)
- Length: millimetre (mm)
- Volume: cubic metre (m3)
- Weight: grams (g)
- servingCapacity: grams (g)
Numbers should be entered with a decimal place, a space between the number, and the unit as specified above. Use the decimal / full stop / period character as a separator. For example: volume = 20.000 mm3. Do not exceed 3 decimal places.
Important: When converting between systems of measurement, perform the conversion first and then apply rounding. This will give more accuracy and consistency.
Default Front of a complete packaging¶
As with taking and reporting measurements for components, we use the GS1 method for taking measurements. Now, with all the components put together to form the complete packaging, first find the default front, the the face with the largest area, where area is equal to the width times the height.
- The side with the maximum area then becomes the default front of that complete packaging.
Measuring the height, width, and depth of a complete packaging¶
After the default front has been determined, it is possible to determine the height, width, and depth of the complete packaging. Please follow the measurement guidelines provided by GS1
Guide for complete packaging images¶
As with providing measurements, please first find the default front of the complete packaging. The image capturing process and naming convention is similar to GS1.