Metapack is working with more than 50 carriers to understand the changes each requires. To meet these requirements, we will apply changes to the technical integration between Metapack and the carrier.
We aim to make things easier for our customers by providing services that work with any carrier. While this might not always be possible, Metapack will negotiate with carriers to support a consistent solution.
The table in this section details shipping information requirements that Customers may need to consider when planning their changes to meet data requirements for the new Windsor Framework.
|
Update |
Description |
|---|---|
|
Change in Carrier’s Data Validation |
Some carriers are implementing additional mandatory changes and data validation to prepare for this phase of the Windsor Framework. For carriers that Metapack integrates with via API, this change is entirely under the carrier's control. For carriers that Metapack integrates with via EDI only (manifest), Metapack will implement any additional validation as required by the carrier to take effect from 01 October 2024. We are in discussion with more than 50 carriers, some of which have yet to provide Metapack with revised specifications for the technical integration. As such, there may be additional validations to come. Metapack strongly recommends that you execute testing on your Metapack test environment to validate if any changes will be required to meet carriers’ data requirements. We recommend a plan for testing all carriers you may use to ship GB-NI after 30 September, 2024. |
|
|
This new attribute has been added to the Metapack API at the shipment level. The The As most Metapack Customers ship only B2C, Metapack is in discussion with carriers to set this attribute as the default value if none is provided. This is not yet agreed upon for all carriers. If it is, Metapack will apply B2C as the default if no value is provided by the Customer. This default then increases the emphasis on Customers to ensure the correct |
|
UKIMS Numbers |
Two new optional attributes have been added to the Metapack API at the shipment level to enable Customers to supply a UKIMS number for the shipper and/or the recipient. This is required for B2B shipments only. Metapack understands that Customers should also supply the EORI number associated with each UKIMS number provided. Metapack will not apply validation on these attributes unless instructed to do so by individual carriers. A carrier's API may apply validation, which is outside Metapack's control. |
|
Product Level Data |
Metapack API enables Customers to provide the following details for each Product being shipped:
See Metapack's existing guidance on Product-level information. We are in discussion with more than 50 carriers and some have yet to provide us with revised specifications for the technical integration. Currently, Metapack has not identified a requirement for additional product-level detail for any carrier. As not all carriers have provided us with their final changes required, some additional product-level detail may yet be required. Metapack will update if this situation changes as we progress our analysis for all impacted carriers. Shipment.ConsignmentDataFlagIf providing Product Level data, DM customers should set Shipment.ConsignmentDataFlag to |
|
Not At RiskIndicator |
A new optional attribute will be added to the Metapack API at the shipment level enabling Customers to provide a TRUE/FALSE declaration that the goods may be onward shipped into the EU. This is required for B2B shipments only. Metapack will not apply validation to this attribute unless instructed to do so by specific carriers. Carriers may apply validation when using their API integrations. This validation is outside Metapack's control. |