Adobe Commerce replenishment board for daily buying decisions

By General Input

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.

Integrations

  • Adobe Commerce (Magento)
  • Google Sheets
  • Slack

Type

App

Categories

  • Operations

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.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentLocal listing health board for every location you manageWin back LiveChat visitors whose chats went unansweredLet support send one-off Loops emails without an engineerStop cold emails to anyone with a live deal in PipedriveiMessage campaign console with pre-flight checks and delivery boardChat quality review board for LiveChat support leadsLinkedIn Ads budget pacing dashboard for every client accountFront desk appointment confirmation board for the next 3 daysGive your team Looker numbers without buying more seats