<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/0365a700d23b4e14b8e210bdd0fb1c59&quot; frameborder=&quot;0&quot; width=&quot;1904&quot; height=&quot;1428&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1428</height><width>1904</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1428</thumbnail_height><thumbnail_width>1904</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/0365a700d23b4e14b8e210bdd0fb1c59-6bde8b15d0f17448.gif</thumbnail_url><duration>719.723</duration><title>Linking Recipes to POS IDs for Efficient Inventory Management</title><description>In this video, I walk you through the process of linking recipes to our POS IDs, using cocktails as a primary example. I demonstrate how to map ingredients like Kraken Dark Rum and mixers such as Coke and Diet Coke to their respective recipes, ensuring we avoid duplication. I also explain how to handle modifiers that don’t change the recipe, like cooking preferences for steaks, and how to dismiss irrelevant POS IDs. I encourage you to follow along and apply these steps to streamline our recipe mapping process. Please make sure to check for existing recipes before creating new ones to maintain efficiency.</description></oembed>