POS ID Item Import - Coming Soon

Function Coming Soon

Merging POS items by POS ID is a function that is coming soon and not yet available to customers.

Point of Sale (POS) items in R365 are imported from connected POS systems. POS items are linked to menu items to power menu item mapping, recipe depletion, and reporting.

Previously, POS items were imported to R365 and merged based on their name alone. Now, R365 is enabling ID-based POS item import. R365 will first use any available POS IDs for item matching. POS IDs are unique identifiers that a POS system assigns to each button or item, separate from its display name. It lets R365 tell same‑named items apart so they can be mapped accurately to the correct menu items.

With POS IDs:

• Users will no longer need to create odd, lengthy, or misspelled menu items to differentiate between items (Ex. No Cheese*****, SUB GRL CHIKEN).

• Renaming will not disrupt mapping in R365.

• Modifier management will become simpler and more accurate.

ID-Based POS Items

Current Behavior: Name-Based POS Item Ingestion

Currently, R365 ingests POS items and merges them based on name alone. This means if multiple POS items share the same name (for example, No Cheese), R365 merges them into a single POS item in R365. It does not consider that identically named POS items may belong to different dishes or represent different ingredients or portions. This has led to inaccuracies in mapping and depletion tracking, particularly when items that appear the same name are actually used in different Item contexts.

Future Behavior: ID-Based POS Item Ingestion

To improve depletion accuracy and menu item reporting,  R365 is switching to an ID-based ingestion. Going forward, R365 will use a POS item’s unique ID (when available) in addition to its name.

With ID-based POS item ingestion, the following may occur:

• When a POS item has a unique ID, that item will be merged based on its ID and not by name. Unique POS Item IDs become their own POS items in R365, even if their display is the same.

• When a POS item does not have an ID, the item will continue to be merged by name.

• When a customer uses more than one POS and some items have IDs while others do not, then the system treats same-named items as distinct when an ID exists, but merges same-named items when the ID is null.

  • For example:

    • POS item No Cheese with ID 17 → mapped to No Cheese (Menu Item A)

    • POS item No Cheese with ID 18 → mapped to No Cheese (Menu Item B)

    • POS item No Cheese with no ID → mapped to No Cheese (Menu Item C, and merged with all other no-ID No Cheese items)

Name to POS ID Transition

To prevent menu item disruption during the move to ID-based POS imports, the system  will apply rules to determine how new ID-based POS items are linked to existing menu items.

When a POS item is imported with an ID (meaning, the POS item is newly created in R365), the system will check how existing POS items with the same name are already mapped.