Overview Product Maps, MDB Codes & PA Codes | How They Work Together

Before you can track sales, manage stock, or generate a picklist, your machine needs a product map. This overview explains what a product map contains, what PA and MDB codes do, and what breaks when either is wrong.

General

 
 
Overview

Product Maps, MDB Codes & PA Codes |
How They Work Together

A product map is the link between your physical machine and Nayax Core. Without one, every sale is just a payment amount - no product name, no stock movement, no picklist. This overview explains what a product map contains, what each code does, and what goes wrong when either is incorrect.

 
Unattended Vending
 
All operators
Real Operator Scenario
"The machine is taking payments - but every transaction in the report says Unknown Product."

Priya manages 14 machines across a hospital trust. A new machine went live on Monday. By Wednesday, the site manager calls: patients are buying drinks, payments are going through, but the Nayax Core sales report is useless - every line says "Unknown Product" and stock levels have not moved at all.

The terminal was installed and connected correctly. But nobody built the product map. The machine knows how to take a payment - Nayax Core does not know what was sold, at which slot, or how many remain.

Consequence: Priya has no inventory data for the first two days of trading. The picklist for that machine is empty. The driver over-fills two slots and misses three others entirely on the first service visit.

FAQ

FAQ

Did you find this article helpful?

Related articles

How to Create a Product Map with MDB Codes | OperationsVending Machine Protocols | Nayax CoreHow to Create a New Product in Classic Core | AdministrationHow to Export Products Map to an Excel | OperationsHow to Create a Product Group | Administration