It would be nice if I could find all the EAN codes the label has ever interacted with. See the example below.
{
"storeId": "MyStoreId",
"labelId": "C51E99EC",
"creationDate": "2020-01-16T16:04:40.444Z",
"modificationDate": "2020-01-16T16:04:40.444Z",
"status": "SYNCHRONIZED",
"matching": {
"matchingDate": "2020-01-16T09:37:27.257Z",
"scenario": {
"scenarioId": "TEMPLATE_1",
"name": "Template 1"
},
"items": [
{
"id": 3000000000502,
"name": "Cola bottle 33cl",
"price": 2.3
}
],
"numberOfMatchings": 0,
"allEANs": [123243566453, 9859574812731]
}
Guest
Good afternoon,
Unfortunately, this feature will not be implemented. We cannot keep all data.
However, you can use the GET timeline API call to monitor your matchings and view the items associated to your labels.
BR,
Emmanuelle
Dear Customer,
We will call you to discuss this topic.
BR,
Emmanuelle
This suggestion would help us to analyze how the label has been used in the store. Thus, it would help us to resolve warranty cases at our end.
Example case: Store sends back a label that is dysfunctional and the reason for this can not be determined from the appearance of the label meaning that there is no physical damage.
Solution: By being able to see, which EAN codes the display has been connected to, we could analyze if the display has been, for example, used or kept in an environment where the temperature is below the recommended value. This would help us to sort out those displays that won't go under the warranty agreement. Thus, this would reduce the unnecessary shipping and handling of those labels, that won't be replaced by your warranty (mainly at your end).
Dear customer,
Can you please give us more information on the use case associated to this idea ?
Thank you in advance,
Regards,
Emmanuelle Benferhat