Already smart
Keep the machine and evaluate whether VendingTracker can become the software layer that runs it.
Compatibility / Retrofit
Vending machine compatibility and MDB/Pulse retrofit.
VendingTracker supports many smart vending machines and offers an upgrade path for legacy MDB and Pulse equipment, subject to model review.
If a machine is not yet integrated, DMVI can assess a new integration when the hardware and protocol information are available.
Three paths
Three ways into the platform.
This page is here to reduce technical buying friction, not to pretend every machine fits the same path.
Legacy MDB / Pulse
Add a screen, add the Android IPC, and move older assets into a more modern software environment.
Not integrated yet
Unusual hardware is often a scoping conversation, not an automatic no, provided the technical inputs are available.
Retrofit
Add the modern software layer without replacing the whole cabinet.
For legacy MDB and Pulse machines, the retrofit path may include a screen and a DMVI-supplied Android IPC running VendingTracker, subject to machine review and deployment fit.
Older machine, limited software layer
Preview showing before-state proof: older interface, limited data visibility, and fragmented operating workflows.
Connected retail endpoint
Preview showing retrofit proof showing visibility, alerts, branding, content, and reporting inside one platform.
What the upgrade unlocks
From older machine to connected retail endpoint.
Once connected, the machine can be brought into the same operating environment used for visibility, alerts, inventory, planograms, branding, content, and reporting across the wider fleet.
VisibilityBring retrofit machines into the same operating view as the wider fleet.
AlertsRoute machine issues before they become prolonged service noise.
MerchandisingManage products, layouts, and pricing from the same software layer.
Branding and contentPresent a more modern shopper experience once the machine is connected.
Integration process
If it is not integrated yet, that is usually the start of the conversation, not the end.
Review the machine model and current setup, assess protocol or SDK access, work from supplied hardware for testing, and validate the target workflow before rollout.
Collect manufacturer, model, controller, and current environment details.
Check protocol, SDK, hardware, and payment-path inputs before scoping.
Confirm the deployment path and the shopper or operator workflow the machine needs to support.
Typical integration timing may range from about one week to one month, depending on complexity, hardware access, and queue.
Required intake
Bring the details that actually matter.
Compatibility should route into a technical intake, not a generic calendar slot with no context.
Recommended intake fields
- Company and fleet size
- Machine manufacturer and model
- Smart versus MDB/Pulse
- Current controller and payment terminal
- Protocol or SDK availability
- Country or region and target timeline
- Photos or documents upload
Route the next step cleanly.
Use compatibility for current machines, retrofit for legacy assets, and integration when the hardware is unusual.
Compatibility and retrofit fit depend on machine model, controller, payment setup, and deployment scope.
Show us the machine, and we will tell you the right retrofit or integration path.
Share the model, setup, and target environment so vending machine compatibility, retrofit scope, and integration risk can be assessed with real context.