Skip to main content
PLU (Price Look-Up) codes are unique identifiers that link products between storekit and your POS system. Correct PLU mapping ensures orders flow accurately to your kitchen.

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:
  1. Log into your POS back office
  2. Export or print your product list with PLU codes
  3. Include modifiers and variants
Create a spreadsheet with columns for: POS PLU, POS Name, storekit Product Name, Category. This becomes your reference document.

Step 2: Add PLUs to storekit Products

For each product:
  1. Go to Menus and open the menu
  2. Click a product to open the Edit product panel
  3. Find the POS ID field (or PLU, for integrations that use it)
  4. Enter the exact code
  5. Click Save at the bottom of the panel
POS ID only shows for accounts with Tissl, Comtrex or Centegra switched on, and PLU only for accounts with PLUs switched on. If you don’t see the field you need, contact support.

Step 3: Map Modifiers

Modifiers need PLUs too:
  1. Open the product in the menu editor, switch to the Modifiers tab, and click Edit on the modifier group
  2. Click Edit option on the option’s row to open its panel
  3. Enter its code in POS ID (or PLU)
  4. Click Save at the bottom of the panel

Step 4: Verify Mappings

Before going live:
  1. Review your PLU spreadsheet
  2. Check every storekit product has a PLU
  3. Verify PLUs match exactly (case-sensitive for some systems)
  4. 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
Update this document whenever you make changes.

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:
  1. Check the PLU on the storekit product
  2. Verify against your POS product list
  3. Correct any mismatches
  4. 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:
  1. Identify products without PLUs
  2. Look up correct PLU in POS
  3. Add PLU to storekit product
  4. 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
Solution:
  1. Verify PLU exists in POS
  2. Check for typos (extra spaces, wrong characters)
  3. Confirm PLU is active and visible
  4. Update storekit if PLU changed

Modifier PLUs Failing

Problem: Base product works but modifiers fail Cause: Modifier PLUs missing or incorrect Solution:
  1. Check all modifier options have PLUs
  2. Verify modifier PLUs exist in POS
  3. Test each modifier individually
If your account has the PLU Manager, the PLU Manager button on the Menus page lets you review codes across menus in one place.

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

  1. Create product in POS first
  2. Note the assigned PLU
  3. Create product in storekit with PLU
  4. Update your reference document
  5. Test the new item

When Removing Items

  1. Remove from storekit (or mark unavailable)
  2. Update your reference document
  3. Optionally remove from POS

When PLUs Change

  1. Update storekit product with new PLU
  2. Update reference document
  3. Test affected products
  4. Note the change date for troubleshooting
For further assistance, contact support.