Commission Implementing Regulation (EU) 2023/448 of 1 March 2023 amending Implementing Regulation (EU) 2018/574 on technical standards for the establishment and operation of a traceability system for tobacco products

	‘Payer_Address_1	Payer’s street name and house number (or road number and kilometre)	Text	S	M, if Payment_Payer1 = 0
	Payer _Address_2	Payer’s municipality (city, town or village)	Text	S	M, if Payment_Payer1 = 0
	Payer _Address_3	Payer’s postal code	Text	S	M, if Payment_Payer1 = 0	‘n/a’ is permitted value if no postal code has been assigned’

• 2.7. Section 5 in Chapter II is replaced as follows:

‘ Recalls

1. Recalls of requests, operational and transactional messages (possible for message types 2-1, 2-2, 2-3 (only within 24 hours from the original reporting of message 2-3, for Deact_Reason1 other than “2 – Product stolen”), 3-1 to 3-8, 4-1, 4-2 and 4-3)

Item #	Field	Comments	Data Type	Cardi-nality	Prioritt	Values
	Message_Type	Identification of message type	Text	S	M	5
	EO_ID	Economic operator identifier code of the submitting entity	EOID	S	M
	Recall_CODE	Message recall code provided to the message sender in the acknowledgement of the original message to be recalled	Text	S	M	Recall_CODE
	Recall_ Reason1	Reason for recalling the original message	Integer	S	M	1 – reported event did not materialise (only for message types 3-3, 3-5 and 3-8) 2 – message contained erroneous information 3 – other
	Recall_ Reason2	Description of the reason for recalling the original message	Text	S	M, if Recall_ Reason1 = 3
	Recall_ Reason3	Any additional explanations on the reason for recalling the original message	Text	S	O
Notice: A recall with respect to operational and logistic events results in flagging the recalled message as cancelled but does not lead to the deletion of the existing database record.’	Notice: A recall with respect to operational and logistic events results in flagging the recalled message as cancelled but does not lead to the deletion of the existing database record.’	Notice: A recall with respect to operational and logistic events results in flagging the recalled message as cancelled but does not lead to the deletion of the existing database record.’	Notice: A recall with respect to operational and logistic events results in flagging the recalled message as cancelled but does not lead to the deletion of the existing database record.’	Notice: A recall with respect to operational and logistic events results in flagging the recalled message as cancelled but does not lead to the deletion of the existing database record.’	Notice: A recall with respect to operational and logistic events results in flagging the recalled message as cancelled but does not lead to the deletion of the existing database record.’	Notice: A recall with respect to operational and logistic events results in flagging the recalled message as cancelled but does not lead to the deletion of the existing database record.’

• (3) The following Annex III is added:

‘ANNEX III

Structure of a unit-level unique identifier

	(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)
Element:	Symbology identifier	Mandatory data qualifier	ID issuer’s identification code	Optional data qualifier	Serial number	Optional data qualifier	Product code	Optional data qualifier	Time stamp
Type:	Qualifier	Qualifier	String (data element)	Qualifier	String (data element)	Qualifier	String (data element)	Qualifier	String (data element)
Position within the unique identifier:	Fixed	Fixed	Fixed	Non-fixed	Non-fixed	Non-fixed	Non-fixed	Fixed	Fixed
Regulated by:	Art. 21(1) and ID issuer’s coding structure	Art.3(4), Art.8(1)(a), Art. 21(1) and ID issuer’s coding structure	Art.3(4) and Art.8(1)(a)	Art. 21(1) and ID issuer’s coding structure	Art.8(1)(b)	Art. 21(1) and ID issuer’s coding structure	Art.8(1)(c)	Art. 21(1), Art. 21(4) and ID issuer’s coding structure	Art.8(1)(d) and Art.21(4)
Applicable international standards:	ISO/IEC 16022:2006, or ISO/IEC 18004:2015, or ISS DotCode Symbology Spec.	ISO 15459-2:2015 and ISO 15459-3:2014	ISO 15459-2:2015 and ISO 15459-3:2014
Process:	Applied by economic operators	Applied by economic operators	Generated by ID issuers	Applied by economic operators	Generated by ID issuers	Applied by economic operators	Generated by ID issuers	Applied by economic operators	Applied by economic operators
Transmission to the repositories system:	No	No	Yes	No	Yes	No	Yes	No	Yes
Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’	Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure.’