I would like to have a counter to count all the matchings (see the example below with the added counter "numberOfMatchings")
{
"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
}
Hi,
We are sorry but this feature will not be implemented.
To monitor your labels, you can use the "GET timeline" API call and follow of all the matchings, among other things.
BR,
Emmanuelle
Thank you for all the details.
I think that the mentioned idea on the number of flashes is the idea VCLD-I-54 "Transmissions and flashes counter". No worries, we did not lost the idea.
All your suggestions will be examined soon by the technical team.
Regards,
Emmanuelle
In my original enhancement idea, I also mentioned the counter for "How many times the flash has been used". Now that you did split my suggestion in three parts, that idea is lost. However, the reasoning for that counter is the same as explained below.
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: This information would simply help us analyze, how the label has been used. However, if you would provide us a complete list of all the EAN codes in which a single label has ever been connected to (as described in another Aha!-idea), we can get this value from the length of the EAN code array.
Dear customer,
Can you please give us more information / use case on this request so we better understand your need ?
Regards,
Emmanuelle Benferhat