Weekly Clover reorder brief in Slack

Every Monday at 8am in the merchant's timezone, produce a weekly reorder brief for the Clover store manager and post it as a Slack message.

Pull the last seven days of orders from Clover with List Orders, filtered by createdTime within the past seven days. For each order, expand the line items with List Order Line Items — Clover caps nested arrays in expand at 100, so fetch line items per-order rather than trying to inline everything in one request. Aggregate quantities by item to compute unit sales per SKU across the week.

Get the current inventory picture next. Call List Inventory Items to enumerate the merchant's items, and List All Item Stock to read on-hand quantities for each tracked item. Join the two so every item has a name, SKU, weekly units sold, and current stock.

Have an agent classify each item into one of three buckets:

• Hot sellers running low — high weekly velocity plus low stock, projected to stock out within the coming week.

• Dead stock — zero or near-zero sales in the last seven days but still sitting on the shelf.

• Everything else — neither urgent nor stalled; leave off the message.

Draft a short Slack message using Send a Message. Put the reorder shopping list at the top (the hot sellers that need restocking now), dead stock at the bottom, and skip the middle bucket entirely. Include a one-line 'why' next to each pick — for example, 'sold 24 this week, only 5 left' or 'zero sales in the last week, still holding 18 units' — so the manager can act in five minutes. Keep the total message tight enough to read on a phone in the parking lot.

Native Clover reports show the raw numbers but do not synthesize a reorder list. The value here is combining velocity and on-hand stock into a prioritized action list, not a spreadsheet the manager still has to interpret.