<?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/dad3dae0c8574fceaa4caf5f128a60a6&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/dad3dae0c8574fceaa4caf5f128a60a6-537b84dd395802e1.gif</thumbnail_url><duration>300.264</duration><title>Building an Order System for Production</title><description>This Loom explains how a food production company built an order system to replace Slack for day to day production communication. The author found Slack messages were largely irrelevant to production, and production needed specific information like order amounts, deadlines, delivery timing, and upcoming large orders. They consolidated the work using Google Sheets and ChatGPT, creating an order section and order status view so all departments could check progress without constant back and forth calls. Because new client data was repeatedly added, they also introduced a client entry form stored separately, enabling sales to select clients and articles from drop downs and submit orders once, after which production could add batch numbers and expiry dates.</description></oembed>