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 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.
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.
Every bin in your product map contains the fields below. Whether you imported a template or added bins manually, review and complete each one before the map goes live. Tap a field to expand it.
- 1You know the PA code (selection code, e.g. A3 or B6) for each product from the machine's keypad layout.
- 2You have the MDB codes for each bin from the machine's technical documentation or manufacturer, not from another machine's product map.
- 3You understand that MDB codes are machine-specific and must be verified for each machine individually.
- 4If you plan to use remote price changes, you have the PC code (motor code) for each bin.
- 5If you are importing a template from another machine, you have confirmed the MDB codes match the destination machine's physical slot layout.
Field Definitions
Tap a field to expand it and see how it works.
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.
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.
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
PA1line of that file and verified against the product map.
A3 or B12. This distinguishes them from MDB codes, which are always numeric only.
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.
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 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.
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 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.
The PAR Formula
Nayax Core uses this formula to calculate the Missing value for every bin automatically.
Sometimes, but not always, and they should never be assumed to be the same. The PA code is a selection code that may include letters, such as A3. The MDB code is always numeric and specific to the bin's position in the machine's communication protocol. They can coincidentally share a number, but they serve completely different functions. Always enter them separately from their respective sources, the PA code from the machine's selection layout and the MDB code from the machine's physical slot configuration.
You need the PA code and MDB code for every product on a product map, these are required for sales to record correctly and for the right bin to dispense. The PC code is required if you intend to use the Bulk Remote Price Change feature for that product. If you manage prices manually or at the machine level, the PC code is less critical, but it is best practice to enter it correctly from the start so you have the option to use remote pricing later.
MDB codes come from the machine itself, specifically from the machine's MDB configuration or from the machine manufacturer's documentation for that model. They are not generated by Nayax Core. If you are unsure of the codes for your machine, contact the machine manufacturer or check the technical documentation that came with it. Entering codes that do not match the machine's actual configuration will cause incorrect products to dispense and inaccurate sales data.
The template carries the MDB codes from the original machine. If the new machine has the same physical slot layout and the same MDB configuration, they will be correct. If the machines are different models or have different slot arrangements, the MDB codes will need to be updated for the new machine before the map goes live. Always verify MDB codes against the destination machine's physical configuration before importing, do not assume identical machine models share identical MDB codes.
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 reached the machine but was applied to a different slot, or could not be applied at all. Open the product map for that machine in Nayax Core, locate the product, and verify that the PC code matches the motor code in the machine's documentation. If it is incorrect, update it and re-issue the price change.
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.
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.
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.
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
Software
Did you find this article helpful?