This section covers Metapack's preparations for the Windsor Framework.
Metapack is working with more than 50 carriers to understand the changes that each will require. We will apply changes to the technical integration between Metapack and the carrier to meet these requirements.
Metapack has extended the DM and MPM API to enable Shippers to provide:
-
New optional attributes for Shipper and Recipient UKIMS Numbers
-
A new optional attribute,
movementIndicator, enables shippers to indicate B2B/B2C/C2C/C2B. For some carriers, this information is mandatory for B2B. -
A new optional attribute for a declaration of the risk that the goods will be onward shipped into the EU (True/False)
-
Further technical detail on these new data attributes can be found by referring to the Metapack API specification for the product you use. These new data attributes are available now for Customer functional testing.
See the Changes to Metapack API section of this article.
-
Delivery Manager
-
MPM
-
Some carriers are using this opportunity to introduce additional mandatory changes. We are required to apply any additional data validations as stipulated by the carriers.
Metapack is developing changes as required for the carrier integrations impacted by this phase of the Windsor Framework. Your Metapack Account Manager can inform you about the current estimated date when each carrier will be available for testing.
Check with your carriers. They will have the best and latest understanding of any changes they might implement. We may not yet have visibility of recent changes that carriers apply to their API integrations, such as additional data validation.
Metapack can confirm if the product description is being provided to the carrier (via API or EDI) but cannot confirm that it meets the carrier’s or HMRC requirements.
Requirements may differ between each carrier. Only they can confirm that customers are providing them with the complete and accurate data elements they require.