The words this industry uses

The cabinet that takes payment and hands over a product with nobody behind it. In the trade the word points at snack and drink machines first, but the same controller, the same bus and the same payment path sit inside coffee machines, lockers, car washes and EV chargers. What makes a machine "vending" is not what it sells — it is that it settles a transaction on its own.

The umbrella the industry moved to once "vending" stopped covering the range: machines, kiosks, micro markets, lockers, car washes, laundry. It is a useful term because it names the actual constraint — no cashier, so the machine has to take the money, prove the sale and report itself.

The broadest of the three: any machine a customer operates themselves. We use it on purpose, because the integration path does not care whether the cabinet drops a chocolate bar or fills a car wash bay.

Self-service beyond vending

An open shelf inside a closed space — an office, a factory floor — with a self-checkout terminal at the exit instead of a cabinet. No spirals, no glass. The payment and reporting problem is identical to a machine's; only the physical container is gone.

A free-standing, screen-first terminal: ticketing, ordering, check-in. What separates it from a vending machine is what it hands over, which is often nothing physical at all.

Not a category so much as a generation: a cabinet engineered to accept coins and frequently nothing else. These machines still earn, which is why converting them is a real market rather than a nostalgia exercise.

Converting coin-op machines to card payment

Umbrella for every method that is not notes and coins: cards, contactless, QR, meal cards, closed-loop credit. It says nothing about how the money is read or who settles it — only that cash is not involved. A specification that says "cashless" and stops has not specified anything yet.

A reading method, not a payment instrument: a card or phone held near the reader. It gets used as a synonym for "credit card", which is precisely how three quotes for the same job come back with three different price structures.

The chip-card standard behind card acceptance, and the reason a payment terminal cannot simply be written from scratch: the stack has to be certified, and certification is per terminal, per scheme, per country. It is the single largest hidden line in "we'll just build our own".

Should a machine builder write its own?

Payment initiated by scanning a code, shown either by the machine or by the phone. It takes the card reader out of the hardware cost; it does not take the certification, settlement and reconciliation work out of the project.

The field name for the terminal. Accurate about the hardware and misleading about the job: on an unattended machine the same device also drives the machine, reverses the payment when the product does not drop, and records the sale itself.

What the terminal accepts

The counter-top device a cashier uses, borrowed wholesale by this industry. The borrowing hides the one difference that matters: a counter POS assumes a human who can hand the product over, or refund it when something goes wrong. At a machine there is nobody standing there.

Credit that only spends inside one operator's estate: staff allowances, campus balances, loyalty. The transaction never leaves the platform, so the rules — who may spend, how much, on what — are the operator's own rather than a scheme's.

In Turkey, a regulated employee benefit instrument — Multinet Up, Edenred, Pluxee (formerly Sodexo), Setcard, MetropolCard, Macellan — each with its own acceptance rules and its own integration. Foreign teams costing a Turkish deployment routinely leave this line out entirely, and it is not a small one.

Data the machine produces on its own: sales, stock, temperature, door state, faults. The word says the data moves. It does not say who produced it, or whether it agrees with the payment record — and when two devices produce two versions of the same sale, that silence is the whole problem.

Vending telemetry

The management layer: machines and locations, planograms, pricing, stock and replenishment, routes, reports, user roles. Every platform contains one. Not every VMS has a platform underneath it, and that is the question worth asking before signing.

Management system or platform?

Everything beneath the panel: the device on the machine bus, the edge software, payment, connectivity, offline buffering, the cloud, updates. The difference shows up at month end — on a platform the sales figure is created by the payment transaction itself; on a management system it is imported from somewhere else and has to be reconciled.

The map of what sits in which slot, at what price. Roughly half of all "the machine is reporting wrong" calls are a planogram that has drifted from the physical shelf.

The order in which one person visits machines to fill and collect. This is where telemetry pays for itself first: a route built on what the machines actually report beats a route built on a calendar, and the saving is measured in trips not taken.

The audit-data format a vending machine can dump: cumulative counters, sales per selection, error history. Old, very widely implemented, and read-only — it tells you what happened, it does not run anything and it cannot take a payment.

The European vending data-transfer standard that DEX files travel inside. Its manufacturer-code registry is also one of the few third-party records of who actually builds in this industry — ours, DMS, has been listed since 2008 and is still in the current edition.

The 1996–2026 record

The serial protocol between a vending machine's controller and its peripherals — coin unit, note reader, cashless device. One master (the VMC), addressed peripherals, and a payment terminal joins the bus as a cashless device. "Standard" here means every machine implements it; it does not mean every machine implements it identically, which is where integration time actually goes.

What is the MDB protocol?

The board that owns the machine: motors, refrigeration, selection logic, prices. Payment does not replace the VMC and cannot overrule it — payment negotiates with it, which is why a terminal has to know the machine, not just the card.

The industrial controller found in machines never built as vending: car washes, EV chargers, laundry, lockers, industrial doors. No MDB, no concept of a cashless device — so payment has to arrive as an input the PLC already understands.

Payment on PLC-controlled machines

The protocol most PLCs speak, over serial or TCP. Registers and coils rather than vending messages — it is the path by which an approved payment becomes a signal a car wash bay acts on.

The most primitive integration there is: the terminal closes a contact and the machine reads it as a coin dropping. No data back, no confirmation that anything was delivered — and yet it is the reason a cabinet built in the 1990s can accept a contactless card today.

What this work was called in 1996, before the industry settled on "telemetry": a box between a machine that speaks one thing and a network that speaks another. The name aged out. The job did not.

Updating software on machines remotely. It is the difference between an estate you can fix from a desk and an estate that needs a van, and past a few hundred machines it stops being a convenience and becomes the operating model.

Built so the machine keeps selling when the link drops: authorize locally, vend, record, then reconcile when the network returns. In a basement corridor or a factory sub-level this is not a feature — it is the baseline the machine has to meet to be worth installing.