Franz, this lesson is about the Restock Order Form and exception review.

The most important thing to understand is that the order form is not where the thinking begins. The order form is where the reviewed decision lands. If you start in the order form, you are skipping the evidence. If you start in the tiles and end in the order form, you are following the workflow.

The order form exists because a buying decision needs to be documented clearly enough that Brent and Fergus can review it without reconstructing all the logic from memory. A final quantity without reasoning is dangerous. A final quantity with supplier, case pack, lead time, velocity, inventory, and notes is reviewable.

Start with the product identity. Confirm the SKU, ASIN, and product name. If the identity is uncertain, the order is not ready. A wrong identity can create the worst kind of error: ordering the wrong product confidently.

Next look at the recommended order quantity. This number should come from the Restock Dashboard and the review process. It should account for daily velocity, available inventory, inbound units, target cover, and lead time. Do not copy the number if you have not checked the inputs behind it.

Then check MOQ and case pack. Suppliers often require order quantities in certain increments. If the math says five hundred fifty units but the case pack is twenty-four, the final order must be rounded to an allowed quantity. This is not a cosmetic detail. It affects cost, inventory risk, and how the order is placed.

Then check the supplier. Supplier choice matters because cost, availability, reliability, lead time, and ordering constraints vary. A product may be a good reorder from one supplier and a bad reorder from another if timing or cost has changed.

Now read the notes. The notes field is one of the most important fields in the entire restock process. Notes should explain why the quantity is being recommended, what was checked, and what uncertainty remains. If the note only says “order 576,” it is not good enough. A good note says why.

Before a recommendation becomes final, perform exception review. Check seasonality. Check whether there was a temporary sales spike or drop. Check whether the listing is active and healthy. Check whether buy box or MAP conditions distorted sales. Check supplier availability and lead time. Check margin. Check whether Brent or Fergus has intentionally paused or deprioritized the SKU.

If everything is clean, the order form can move forward as ready for review. If something is uncertain, the correct status is not guessing. The correct status is blocked or escalated, with a clear note explaining the blocker.

Your pass condition for this lesson is to take one SKU and produce a reviewable recommendation. The recommendation should say: this is the product, this is the inventory we can use, this is the velocity, this is the days of cover, this is the lead time and target cover, this is the suggested order, this is the case pack rounding, these are the exceptions checked, and this is my final recommendation.

That is how the order form turns Amazon Ops analysis into an actual buying decision.