Understanding PLU Codes
A PLU code is a number or alphanumeric code that uniquely identifies a product in your POS. When storekit sends an order to your POS, it includes the PLU code so the POS knows exactly which item was ordered.Example PLU Mapping
When PLU Mapping Is Required
Product codes must be entered by hand for manual linking integrations, where menus aren’t automatically synced. Each one reads a different field:
For automatic sync integrations (Zonal, Lightspeed, Toast), codes are filled in automatically during menu sync.
Setting Up PLU Mapping
Step 1: Export PLU List from POS
Get a complete list of PLU codes from your POS:- Log into your POS back office
- Export or print your product list with PLU codes
- Include modifiers and variants
Step 2: Add PLUs to storekit Products
For each product:- Go to Menus and open the menu
- Click a product to open the Edit product panel
- Find the POS ID field (or PLU, for integrations that use it)
- Enter the exact code
- Click Save at the bottom of the panel
Step 3: Map Modifiers
Modifiers need PLUs too:- Open the product in the menu editor, switch to the Modifiers tab, and click Edit on the modifier group
- Click Edit option on the option’s row to open its panel
- Enter its code in POS ID (or PLU)
- Click Save at the bottom of the panel
Step 4: Verify Mappings
Before going live:- Review your PLU spreadsheet
- Check every storekit product has a PLU
- Verify PLUs match exactly (case-sensitive for some systems)
- Test with sample orders
PLU Mapping Best Practices
Keep a Master Reference
Maintain a spreadsheet that maps:- storekit product ID/name
- POS PLU code
- POS product name
- Last updated date
- Notes
Use Consistent Naming
When creating products in storekit, use naming that makes PLU matching easier:
Including PLU in the internal name helps during audits.
Handle Variants Correctly
Products with size or variant options often have different PLUs:
In storekit, you can either:
- Create separate products for each size
- Use modifiers with individual PLUs
Plan for Modifiers
Modifiers typically fall into categories:Some POS systems handle removals differently. Check with your POS provider how to configure “no X” modifiers.
Document Special Cases
Note any unusual mappings:- Products with multiple PLUs (combos)
- Time-based PLUs (lunch vs dinner pricing)
- Location-specific PLUs (multi-venue setups)
Common PLU Mapping Issues
Mismatched PLUs
Problem: Order shows wrong item in POS Cause: PLU in storekit doesn’t match POS Solution:- Check the PLU on the storekit product
- Verify against your POS product list
- Correct any mismatches
- Test with a new order
Missing PLUs
Problem: Order fails or items missing Cause: Product in storekit has no code assigned. Centegra fails the whole order; Tissl and Comtrex leave the item off and send the rest Solution:- Identify products without PLUs
- Look up correct PLU in POS
- Add PLU to storekit product
- Save and test
PLU Not Found in POS
Problem: Error indicates PLU doesn’t exist Cause:- PLU was deleted from POS
- Typo in PLU code
- PLU exists in different location/menu
- Verify PLU exists in POS
- Check for typos (extra spaces, wrong characters)
- Confirm PLU is active and visible
- Update storekit if PLU changed
Modifier PLUs Failing
Problem: Base product works but modifiers fail Cause: Modifier PLUs missing or incorrect Solution:- Check all modifier options have PLUs
- Verify modifier PLUs exist in POS
- Test each modifier individually
Multi-Venue PLU Management
If you have multiple venues:Same POS, Same Menu
- PLUs are typically consistent
- Use the same PLU mapping across venues
Same POS, Different Menus
- PLUs may differ per venue
- Maintain separate PLU mappings per venue
- Document venue-specific codes
Different POS Systems
- Each venue needs its own PLU setup
- Maintain separate reference documents
- Consider standardising where possible
PLU Audit Checklist
Run this audit before going live and periodically after:- All products have PLUs assigned
- All modifiers have PLUs assigned
- PLUs match exactly with POS (no typos)
- PLU reference document is current
- Test orders work correctly
- Price points are accurate
- Modifiers appear correctly on tickets
- New items added since last audit are mapped
Maintaining PLU Mappings
When Adding New Items
- Create product in POS first
- Note the assigned PLU
- Create product in storekit with PLU
- Update your reference document
- Test the new item
When Removing Items
- Remove from storekit (or mark unavailable)
- Update your reference document
- Optionally remove from POS
When PLUs Change
- Update storekit product with new PLU
- Update reference document
- Test affected products
- Note the change date for troubleshooting