> ## Documentation Index
> Fetch the complete documentation index at: https://storekit.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# PLU Mapping Guide

> Best practices for mapping products between storekit and your POS using PLU codes. Avoid common pitfalls and ensure orders flow accurately to the kitchen.

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

| storekit Product            | POS PLU | POS Name   |
| --------------------------- | ------- | ---------- |
| Margherita Pizza            | 1001    | MARG-12    |
| Pepperoni Pizza             | 1002    | PEPP-12    |
| Extra Cheese (modifier)     | 2001    | MOD-CHEESE |
| Gluten Free Base (modifier) | 2002    | MOD-GF     |

## When PLU Mapping Is Required

PLU mapping is required for **manual linking integrations** where menus aren't automatically synced:

* TISSL
* Comtrex
* Centegra
* Other PLU-based integrations

For **automatic sync integrations** (Zonal, Lightspeed), PLU mapping happens 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

<Tip>
  Create a spreadsheet with columns for: POS PLU, POS Name, storekit Product Name, Category. This becomes your reference document.
</Tip>

### Step 2: Add PLUs to storekit Products

For each product:

1. Go to **Menu** in your storekit dashboard
2. Click on a product to edit
3. Find the **PLU** or **POS Settings** field
4. Enter the exact PLU code
5. Save the product

### Step 3: Map Modifiers

Modifiers need PLUs too:

1. Go to your modifier groups
2. Edit each modifier option
3. Enter the PLU code for each option
4. Save changes

### 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:

| Instead of           | Use                     |
| -------------------- | ----------------------- |
| "The Classic Burger" | "Classic Burger (1001)" |
| "Large Fries"        | "Fries - Large (2050)"  |

Including PLU in the internal name helps during audits.

### Handle Variants Correctly

Products with size or variant options often have different PLUs:

| Product | Variant | PLU  |
| ------- | ------- | ---- |
| Latte   | Small   | 3001 |
| Latte   | Medium  | 3002 |
| Latte   | Large   | 3003 |

In storekit, you can either:

* Create separate products for each size
* Use modifiers with individual PLUs

### Plan for Modifiers

Modifiers typically fall into categories:

| Type                                     | PLU Strategy                                  |
| ---------------------------------------- | --------------------------------------------- |
| **Add-ons** (extra cheese)               | Unique PLU per add-on                         |
| **Removals** (no onions)                 | May not need PLU, or use specific removal PLU |
| **Substitutions** (swap chips for salad) | PLU for the substitution item                 |

<Info>
  Some POS systems handle removals differently. Check with your POS provider how to configure "no X" modifiers.
</Info>

### 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 PLU assigned

**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

## 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](/getting-started/contact-support).