Prevent Stockouts Before They Happen

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Shopify, use the Admin API to subscribe to the inventory_levels/update webhook, and also run a scheduled Admin API check across InventoryLevel, InventoryItem, ProductVariant, and Location records so missed webhook events are caught. 3. For each SKU and location, compare available inventory to the reorder threshold stored in Shopify metafields or the merchant's inventory policy sheet; enrich the alert with recent sales velocity from Shopify orders, days of cover, seasonal spikes from the same period last year when available, and a suggested reorder quantity. 4. Send the right email immediately: procurement gets a concise internal stockout-risk alert, and the supplier gets a reorder request only when the SKU is approved for supplier outreach. 5. Run this in MultiMail autonomous oversight mode so time-critical alerts go out without delay. Ask me only for Shopify access, supplier/procurement contacts, reorder thresholds if they are not already stored, and brand/sender details needed to go live.

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In NetSuite, use a saved search or SuiteAnalytics Workbook for inventory items where quantity available is at or below reorder point, grouped by item and location; run it on a frequent schedule, and use SuiteTalk REST Web Services or SuiteScript only if deeper item, vendor, or purchase history is needed. 3. For every low-stock item, pull preferred vendor, lead time, open purchase orders, recent consumption or sales, location, reorder point, and preferred stock level; calculate urgency, suggested order quantity, and whether an existing purchase order already covers the gap. 4. Compose and send alert emails to procurement with the item list, affected locations, days of cover, recommended order quantities, and supplier-ready wording; send supplier emails only for approved vendors and approved reorder scenarios. 5. Run this in MultiMail autonomous oversight mode. Ask me only for NetSuite access, procurement and supplier contact rules, any threshold overrides, and brand/sender details needed to go live.

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Microsoft Dynamics 365 Supply Chain Management, use built-in inventory data, master planning outputs, and OData data entities or Business Events to detect items whose available inventory, coverage, or planned supply falls below the configured reorder threshold by warehouse. 3. For each triggered item, gather warehouse, on-hand quantity, reserved quantity, open purchase orders, demand forecast, lead time, vendor, and recent issue or sales history; calculate projected stockout date, seasonal demand adjustment, and suggested order quantity. 4. Email procurement an immediate stockout-risk alert with the affected SKUs, warehouses, timing, and recommended action; when supplier outreach is allowed, draft and send supplier reorder emails with the requested quantity and required-by date. 5. Run this in MultiMail autonomous oversight mode so urgent inventory alerts are not delayed. Ask me only for Dynamics 365 access, procurement and supplier contact rules, threshold policy, and brand/sender details needed to go live.