8 replies to this topic

[chah93]

Hello all,

I have some confusion, is Traceability and mock recall is two different things? And what is actually a forward and backward traceability?

Thanks in advance!


Sent from my iPhone using Tapatalk

[mahantesh.micro]

Hi Chah,

Traceability and recall are interlinked, If you have to recall any of your product batch then you need to carryout traceability exercise of your batch in question to know where the problem has come from.

 

According to ISO 22000-2018 standard Traceability is defined as below

 

ability to follow the history, application, movement and location of an object through specified stage(s) of production, processing and distribution

Note 1 to entry: Movement can relate to the origin of the materials, processing history or distribution of the food (3.18).

Note 2 to entry: An object can be a product (3.37), a material, a unit, equipment, a service, etc.

 

Forward traceability is tracing a batch from raw material till end product and till it reaches the customer.

Back ward is tracing of a batch of finished product to its raw materials.

 

Mahantesh

[zanorias]

Hi chah93,

 

Forwards/backwards defined as post above.

 

A mock recall is an exercise that tests the systems and procedures in place to recall a product from the marketplace.

 

It's worth noting that slight differences in traceability and mock recalls will likely exist depending on the local regulatory requirements and any scheme applicable.

[mahantesh.micro]

Yes i forgot to mention about Mock recall,  What Mr. Zanorias said about mock recall is right.

[chah93]

Well explained, thanks everyone


Sent from my iPhone using Tapatalk

[Charles.C]

Someone might have mentioned that Traceability requirement  is typically "one step forward and one step back". eg -

 

 traceability.pdf   68.9KB   292 downloads

[BostonCream]

Our auditor defines "traceability exercise" is done internally, knowing where the finished product went to from our shipping record.

"Mock recall" involves one step further, to send a notification to hat customer/CFIA/CB to verify their contact info is correct. 

[Charles.C]

Our auditor defines "traceability exercise" is done internally, knowing where the finished product went to from our shipping record.

"Mock recall" involves one step further, to send a notification to hat customer/CFIA/CB to verify their contact info is correct. 

 

Indeed, there are an infinity of interpretations.

BRC has -

 

Traceability - Ability to trace and follow raw materials, components and products, through all stages of receipt, production, processing and distribution both forwards and backwards

 

 

It does not take a genius to see what a nonsensical definition this is from a practical point of view.

 

Sadly, or perhaps luckily,  the OP failed to provide any specific details as to their "requesting source"

[Hoosiersmoker]

I agree with the majority of the above information. For a "mock recall", we were told that one step forward, one step back is just that, only one. A good example is: If our product is completed and packaged for the customer then goes to, say, a their distribution center and could potentially go from there to 5 different locations. We can trace all of the raw materials used to manufacture our products back to either the manufacturer or a secondary seller (one step back) and our finished goods to the distribution center, who better be certified to a GFSI standard too, (One step forward) it leaves our control from that point and the responsibility moves to the customer's distribution whom we would identify during the "mock recall" or, we might sell direct AND send product to the distribution center so all direct customers would be identified also. There are hundreds of scenarios which I believe is why the description isn't suppliers and customers as they might not be that one step forward or back. Hopefully this is not muddying but helping clarify what one step is.