Metapack's Preparation with Carriers for Windsor Framework Changes

Metapack has modified carrier integrations to respect each carrier's requirements for the Windsor Framework. Not all carriers have required Metapack to make changes. Customers are advised to discuss their requirements with Metapack or with the carriers they use to ship from GB to NI to understand how this may affect any changes the Customer may be planning.

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	A few carriers implemented additional mandatory changes and data validation as part of their readiness for Windsor Framework data regulations that came into effect on 01st May 2025. 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 has implemented additional validation as directed by the carrier. For some carriers, these validations are not yet enabled, and they will be only when the carrier indicates they are required. Metapack will signal to our Customers when these validations are planned to be enabled in production. Customers may need to consider further testing at that point to ensure there is no operational disruption when this happens
`movementIndicator`	This new attribute has been added to the Metapack API at the shipment level. The `movementIndicator` attribute will accept these values: B2B, B2C, C2C, and C2B. The `movementIndicator` is not mandatory for GB-NI volume for all carriers. However, Metapack recommends that our Customers do populate this attribute for all GB-NI volume. A few carriers have agreed for Metapack to apply B2C as a default value if `movementIndicator` is not provided by the shipper. Currently, the `movementIndicator` is mandatory for Royal Mail, DHL, DPD, and DX. Some carriers have indicated Metapack may default this value to B2C if none is provided. Please raise a case in the Customer portal if you wish to learn if this applies to the carriers you plan to use to ship GB-NI after 1st May 2025. The possible use of a default value for this attribute increases the emphasis on Customers to ensure the correct `movementIndicator` is provided for B2B. Metapack considers it good practice for Customers to populate this new attribute for all movement types. C2B (returns) is supported for future compatibility. As of June 2024, no carrier has stated C2B as mandatory.
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: Country Of Origin Quantity Description (Basic and Detailed) Value Weight Tariff Code See Metapack's existing guidance on Product-level information. Shipment.ConsignmentDataFlag If providing Product Level data, DM customers should set Shipment.ConsignmentDataFlag to `FALSE`.
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.

Shipment.ConsignmentDataFlag