Product Map Field Definitions & Troubleshooting

Understand every field in your Nayax Core product map from PA and MDB codes to PAR, On-Hand, and Missing so your bins are configured correctly and your inventory tracking is accurate from day one.

FAQ

Description

Product and Inventory Management › Nayax Core

Product Map Field Definitions

Know what to enter before you open the product map editor. This guide explains every bin field from product assignment and selection codes to inventory tracking so your maps are accurate, your sales data is clean, and your restocking is effortless.

Field Definitions

Every bin in your product map contains the following fields. Whether you imported a template or added bins manually, you need to review and complete each one before the map goes live.

Product Field

The name of the item sold from this bin slot. Product names appear in your sales reports in Nayax Core and in the MoMa app, making it easy to identify what is selling at each location.

A product can be assigned to multiple machines and must belong to a Product Group.

💡
Tip: Use clear, consistent naming conventions for example, "Coca-Cola 20oz" rather than just "Coke" so your reports are easy to read across all your machines.
Product Group Field

A category that organizes products on your operator profile. Product Groups act as folders that house related products, making them available to assign to product maps across your machines. For example, a "Beverages" group might contain all your drink products.

⚠️
Note: If a Product Group does not exist yet for your product, you need to create one before you can assign the product to this bin. Refer to the Creating a Product Group guide for steps.
PA Code Code

A PA code identifies the physical button or keypad selection that a customer presses on your machine to vend a specific product. It represents the customer-facing selection the number or letter combination printed on the machine's selection panel.

PA codes appear in your sales data alongside MDB codes once the product map is fully set up. How PA codes are used depends on your sales data source:

  • Live Transactions: The PA code identifies which button was pressed on the machine during a real-time vend event.
  • DEX / DDCMP: Product data is read directly from the DEX file. PA code information is found in the PA1 line of that file and verified against the product map.
ℹ️
Format note: PA codes can contain letters for example, A3 or B12. This distinguishes them from MDB codes, which are always numeric only.
MDB Code Code

The MDB code is a numeric identifier that comes directly from the vending machine's controller board when a product is vended. Unlike the PA code (which identifies the button pressed), the MDB code identifies the row or channel on the machine's internal control system that was activated during the vend.

MDB codes appear in sales reports alongside PA codes once your product map is complete. You can verify your MDB codes are correctly mapped by vending an item and checking whether your inventory count updates as expected in Nayax Core.

⚠️
Important: MDB codes are numeric only they never contain letters. If you see a code with letters, that is a PA code, not an MDB code.

Inventory Fields

These three fields work together to give you a real-time picture of how full each slot is and exactly how many units to bring on your next service run.

PAR Inventory

PAR stands for Periodic Automatic Replenishment. In the context of a product map, PAR represents the maximum capacity of a bin slot the total number of units that can physically fit in that selection at one time.

Think of PAR as the "full" mark for that slot. If a selection column holds 15 bags of chips, its PAR is 15. Setting an accurate PAR is the foundation of inventory tracking because it tells Nayax Core the target quantity for each slot, allowing the platform to calculate how many units are missing at any given time.

💡
Set PAR once, update rarely. PAR only needs to change if you modify the physical capacity of a slot — for example, by changing the spring coil to accommodate fewer or more items.
On-Hand Inventory

On-Hand is the current quantity of a product actually present in that bin slot. This number decreases as products are vended and should be updated each time you restock the machine.

Keeping On-Hand accurate gives you a real-time view of how full each slot is, helping you prioritize restocking and avoid out-of-stock situations across your machines.

Missing Calculated

Missing is a calculated field Nayax Core computes it automatically using PAR and On-Hand. It tells you exactly how many units you need to bring on your next service run to fully restock that slot.

You do not enter this value manually. It updates automatically whenever PAR or On-Hand changes.

The PAR Formula

Nayax Core uses this formula to calculate the Missing value for every bin automatically.

PAR
On-Hand
=
Missing
Example: Your PAR is 13 (the slot holds 13 units when full) and your On-Hand is 7 (7 units are currently in the machine). Your Missing value is 6 meaning you need to bring 6 units on your next restock visit to fill that slot completely.

Repeat this across all bins and you have a complete pick list for every machine restock.

Readiness Checklist

Before you open the product map editor, confirm you have the right information to hand. Entering codes that do not match your machine's actual configuration causes incorrect products to dispense and inaccurate sales data.

  • You know the PA code (selection code, e.g., A3 or B6) for each product from the machine's keypad layout.
  • You have the MDB codes for each bin from the machine's technical documentation or manufacturer — not from another machine's product map.
  • You understand that MDB codes are machine-specific and must be verified for each machine individually.
  • If you plan to use remote price changes, you have the PC code (motor code) for each bin.
  • If you are importing a template from another machine, you have confirmed the MDB codes match the destination machine's physical slot layout.

FAQ

Troubleshooting Common Issues

The wrong product is dispensing from a bin

Check the MDB code entered for that bin in the product map. If the MDB code does not match the machine's actual slot configuration, vends will be recorded against the wrong product. Open the product map in Nayax Core, locate the bin, verify the MDB code against the machine's technical documentation, and update it if incorrect.

 

Inventory count is not updating after a vend

Verify that the MDB code in the product map matches the bin's actual position on the machine. When MDB codes are mapped correctly, a vend event decrements the On-Hand count automatically. If the count is not changing, the vend is likely being recorded against a different bin or not matched at all. 

 

A remote price change went through but the machine is still charging the old price

Check the PC code (price change code) entered for that product in the product map. If the PC code does not match the correct motor code for that bin, the price change was applied to the wrong slot or could not be applied at all. Open the product map, locate the product, verify the PC code against the machine's documentation, update it if incorrect, and re-issue the price change. 

 

MDB codes fom an imported template are not matching the new machine

A product map template carries the MDB codes from the original machine. If the new machine has a different model or a different physical slot arrangement, the MDB codes need to be updated before the map goes live. Never assume that identical machine models share identical MDB codes always verify against the destination machine's physical configuration. 

 

Properties

Line of Business

Unattended Machines

Software

Nayax Core

Did you find this article helpful?