# Adobe Commerce replenishment board for daily buying decisions

> Open one board each morning to see which Adobe Commerce products run out soonest, edit reorder quantities inline, and push stock corrections back to your store.

- Workflow type: app
- Services: Adobe Commerce (Magento), Google Sheets, Slack
- Categories: Operations
- Published: 2026-08-14

## What it does

- Lists the products running low in your store and sorts them by how many days of stock are left, not by raw quantity remaining, so the most urgent items rise to the top
- Works out how fast each product has been selling from your recent orders and turns that into a days-of-cover figure your buyer can actually act on
- Lets the buyer type a reorder quantity straight into the row, choose whether an item keeps selling while it is out of stock, and save corrected stock numbers back to the store
- Collects the chosen lines into a purchase order draft grouped by supplier, appends it to a Google Sheet ordering log, and posts an optional wrap-up to your buying channel in Slack

## What you'll need

- An Adobe Commerce or Magento store you can connect, with permission to view products and orders and to update stock levels
- A Google account and a spreadsheet you want to use as the ordering log
- A Slack workspace and the channel your buying team works in, if you want the end-of-session summary

## Prompt

Build me an interactive replenishment board that my buyer works out of each morning to decide what to reorder in Adobe Commerce. This is a working tool with editable fields and real write-back to the store, not a read-only report. The buyer opens it, sorts through what is running out, edits numbers, and leaves with a purchase order draft.

The main view is a board of low-stock SKUs. Load the candidates with Get Low Stock Items in Adobe Commerce, using a configurable quantity threshold. Enrich each row with Get Stock Item for the current quantity, stock availability and backorder setting, and with List Products for the product name, SKU, price and supplier attribute. Show one row per SKU with product name, SKU, quantity on hand, days of cover, recent daily sales rate, suggested reorder quantity and supplier.

Days of cover is the point of the board, so compute it properly. Measure recent sales velocity by pulling orders from a trailing window with List Orders (default the last 30 days, make the window configurable) and their line items with List Order Items, then total the units sold per SKU and divide by the number of days in the window to get a daily sales rate. Days of cover is quantity on hand divided by that daily rate. Default the board to sorting by days of cover ascending, so the SKU that runs out soonest is the top row, and let the buyer re-sort by quantity, velocity or supplier. When a SKU has no sales in the window, label it as no recent sales instead of showing an infinite or blank days-of-cover value, and sort those to the bottom rather than dropping them.

Be honest about where a quantity comes from. Stores running Multi Source Inventory hold stock across several warehouses, so label each quantity with the stock source it was read from and never present a single figure as a company-wide total when the store has more than one source. If only one source exists, say so plainly and move on.

Every row is editable inline. The buyer can type a suggested reorder quantity directly into the row, seeded with a sensible default such as the units needed to reach a target days of cover, and can toggle whether backorders should be allowed while the item is out of stock. Rows the buyer has touched should be visibly marked as edited. Provide a save action per row, and a bulk save for selected rows, that pushes stock corrections and the backorder setting back to the store with Update Stock Item. Confirm what was written, show the store's response, and surface any failure clearly against the row that failed rather than swallowing it. Reorder quantities and supplier notes live in the app until the buyer explicitly pushes a stock change, so nothing is written to the store by accident.

Selected lines get collected into a purchase order draft. Group the draft by supplier, taking the supplier from a product attribute chosen in settings and falling back to an unassigned bucket the buyer can fill in by hand, remembering those manual assignments for next time. Each supplier group shows its lines, quantities, unit costs where available and a group total. The buyer reviews the draft, adjusts quantities one last time, then commits it.

Committing the draft appends one row per purchase order line to a Google Sheet ordering log with Append Values, writing the date, supplier, SKU, product name, quantity ordered, quantity on hand at the time, days of cover and the buyer who approved it. The spreadsheet and tab are set in app settings.

Finally, offer an optional end-of-session summary posted to the buying channel in Slack with Send a Message. Keep it short: how many SKUs were reviewed, how many lines were ordered, the supplier split and any stock corrections pushed back to the store. This is a wrap-up the buyer chooses to send, not the purpose of the app, so it must never fire on its own.

Persist edits, supplier assignments, the working purchase order draft and the app settings between sessions so a buyer can start in the morning, get pulled away, and come back to the same board. Include a refresh action that re-reads stock and sales data while preserving edits the buyer has already made.

## How to customize

- Change the low-stock threshold and the length of the sales window used to judge how fast something is selling
- Pick which product field identifies the supplier, or assign suppliers by hand in the board and have it remember them
- Turn the Slack wrap-up on or off, or point it at a different channel

## FAQ

### How is this different from the low stock report already in my Magento admin?

The built-in report simply lists products that dropped below the notify quantity you set on each one. It has no sense of urgency, so a product with 20 units left looks safer than one with 5 even when the first sells 10 a day and the second sells one a week. This board adds recent sales speed, ranks by how soon you actually run out, and lets you edit and save changes instead of just reading a list.

### Will this change stock levels in my live store?

Only when you choose to save a change. You can correct a quantity or switch backorders on for an item in the board, and those specific edits are written back to your store. Reorder quantities and supplier notes stay inside the app until you decide to push something.

### What happens to products that have not sold recently?

They are shown as having no recent sales rather than being given a misleading days-of-cover number. Slow movers stay visible in the board so you can still judge them, but they do not crowd out the items that are genuinely about to run out.

### Does it work if I hold stock in more than one warehouse?

Yes, and the board is explicit about it. Each quantity is labelled with the stock source it came from, so a buyer never mistakes the figure for a company-wide total when stock is spread across several locations.

### Do I have to use the Google Sheet and Slack parts?

No. The board works on its own as a place to review and edit. The ordering log and the channel summary are there for teams who want a paper trail and a quick end-of-session note, and either can be left switched off.

Use this prompt in General Input: https://www.generalinput.com/prompts/adobe-commerce-replenishment-board-for-daily-buying-decisions