Franz, this lesson explains how Brent and Fergus's restock process has been built into Amazon Ops.

The most important idea is this: do not start with the order form. The order form is the output. The decision comes from moving through the Amazon Ops tiles in the correct order.

Start with the dashboard. The dashboard is there to show urgency. You are looking for products with low days of cover, stockout risk, stale data, missing mapping, or any other warning that says this SKU needs attention. The dashboard is not meant to answer every question. It creates the priority queue.

Next, check Warehouse Inventory. This tells you what is physically in the building. That matters because we do not want to reorder a product if Brent already has usable units sitting in the warehouse, in golden stock, replacements, returns, or another section that has not been reflected correctly yet. Your job is to ask: is this current usable inventory, old starting balance, returns, replacements, or something that needs a manual count?

Next, check SKU Mapping Validation. Before trusting any quantity, confirm the product identity. A wrong SKU to ASIN connection can make perfect math produce the wrong order. Make sure the Amazon listing, internal SKU, supplier item, and warehouse count all refer to the same thing.

Then move to the Restock Dashboard. This is where the workflow starts becoming a buying decision. You should review on-hand inventory, inbound inventory, sales velocity, days of cover, lead time, target cover, suggested quantity, risk flags, and notes. Do not look at one number alone. Restock decisions come from the relationship between those fields.

Next, check Amazon-side inventory health. Total inventory is not always usable inventory. Some stock may be reserved, inbound, unfulfillable, aging, or stuck. The question is: what inventory can actually cover future customer demand?

Then review sales velocity. Velocity tells you how quickly the product is moving. Use short and longer windows together. Seven-day sales can catch a sudden change. Thirty-day sales are usually more stable. Sixty or ninety-day views can protect you from overreacting to a temporary spike or drop.

Once inventory and velocity are clear, calculate days of cover. The formula is available inventory divided by daily sales velocity. This is more useful than raw inventory because two hundred units can be safe for a slow product and dangerous for a fast product.

Then account for lead time and target stock. Lead time is the time before new inventory can actually help us. It can include supplier time, shipping, receiving, processing, check-in, and practical delays. Target stock is the cushion Brent and Fergus want to maintain. We buy before we are desperate because waiting until the product is low creates stockout risk.

The simple reorder formula is: target days plus lead time days, multiplied by daily velocity, minus available inventory. Then round to MOQ or case pack.

For example, if daily velocity is ten units per day, target stock is sixty days, lead time is twenty days, and available inventory is two hundred fifty units, then required coverage is eighty days times ten units, or eight hundred units. The suggested reorder is eight hundred minus two hundred fifty, which equals five hundred fifty units. If the supplier case pack is twenty-four, round to the nearest allowed case pack quantity.

After that, do manual exception review. This is the human part. Look for seasonality, temporary sales spikes, temporary sales drops, supplier delays, bad listings, margin concerns, discontinued products, or anything Brent and Fergus intentionally do not want to reorder. Amazon Ops gives you the recommendation. The business still requires judgment.

Only then should the quantity move to the Restock Order Form. The form should contain the final reviewed quantity, supplier, MOQ or case pack logic, and clear notes. If the notes do not explain why the order is being made, the order is not ready.

The pass condition for this module is simple: you should be able to explain one SKU recommendation in plain English. Not just what the spreadsheet says, but why it says it, what you checked, and what could make the recommendation wrong.