EVA DTS for Vending: Reading Data from a Mixed Fleet
EVA DTS stands for the EVA Data Transfer Standard. Its purpose is to support information exchange between vending machines or payment systems and computer-based accounting and management systems. For an operator with equipment from several manufacturers, the practical question is whether the same collection technology can read the required equipment.
Why have a common vending data standard?
The European Vending and Coffee Service Association's technical standards page explains that EVA members develop and maintain EVA DTS. It describes information transfer to accounting and management systems, and in the other direction, to support equipment readout and programming.
The association specifically identifies reading machines from different manufacturers with the same collector as a reason for a common standard. That is the mixed-fleet problem the standard addresses: an operator needs usable information across its equipment, rather than a separate collection approach for every manufacturer.
This published purpose does not establish which functions a particular controller, payment device or software package implements. Ask the suppliers to identify the actual standard version and supported equipment in their proposed solution.
Why can a serial number need a manufacturer prefix?
EVA gives the example of two coin mechanisms both having serial number 123. The number alone would not distinguish equipment made by different suppliers. Its page explains the agreement to prefix serial numbers with a three-letter manufacturer-specific code and links a list of manufacturer codes.
For a reporting import, preserve the complete identifier supplied by the equipment. Ask the software provider how it retains the manufacturer portion and the serial portion, and how those fields connect to the operator's asset record. Removing a prefix merely to make a column shorter can discard the distinction the numbering approach is intended to provide.
The three-letter code identifies a manufacturer within that scheme. It is not a substitute for the individual serial number or for the site's own location reference. Confirm which piece of equipment each incoming identifier represents before assigning its records to a cabinet.
What should a mixed-fleet buyer request?
Provide a list of the machines and payment equipment to be included, with their model and software details where available. Request sample output from each proposed equipment combination and ask the collector provider to show how the identifiers are retained in the receiving application.
Then verify that the sample records are assigned to the intended equipment. Keep any unsupported model or missing field visible in the quotation. A standard name on a brochure does not demonstrate that an entire existing fleet has been integrated, or establish a reporting interval or cloud subscription.
For the separate roles of payment-device communication, audit reporting and application access, see our MDB, DEX and API interface guide. This article uses EVA's public overview; it does not claim a clause-by-clause review of the full standard or confirm EVA DTS support in a WEIMI configuration.
Send WEIMI your equipment requirements, collector details and intended reporting destination for configuration review: Get My Custom Quote.
