> For the complete documentation index, see [llms.txt](https://help.flowerbuddy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flowerbuddy.co/reference/event-page/order/review-order-needs.md).

# Review needs and placed orders

Use **Summary** to compare what the event recipes require with what is already on event-linked purchase orders. The planning side describes the current recipe need. The ordered side describes quantities recorded on purchase orders. They can differ when an order is incomplete, when the recipe plan changes, or when a vendor sells an item in a different group size.

The Summary view places planning quantities, ordered quantities, and the remaining need in one table for each vendor location.

<div data-with-frame="true"><figure><img src="https://2616748322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtdSEPutB4SrRwwUMOIx%2Fuploads%2Fgit-blob-2b925db8ee319ed1a0322f19cf8ce658a838b69c%2F01-populated-order-summary.jpg?alt=media" alt="FlowerBuddy Event Order Summary showing a vendor item with Planning Qty., Group Qty., Cost, Ordered quantity, and Need columns, plus Change Vendor, Export Plan, and Order controls." width="550"><figcaption></figcaption></figure></div>

## Read the planning values

1. Open the event and select **Order**.
2. Select **Summary**.
3. Find the item under its vendor location. Items without a selected vendor appear under **Unknown Location**.
4. Read **Qty.** for the individual quantity required by the event recipes.
5. Read **Group Qty.** for the number of vendor groups needed.
6. Read **Cost** for the current planning cost.

Before a purchase order exists, Summary also shows **Waste**. This is the difference created when a vendor group cannot be divided into the exact individual quantity required by the plan.

## Compare placed quantities with needs

After a purchase order is linked to the event, Summary separates the values into **Planning** and **Ordered**. The ordered side shows the quantity recorded on linked purchase orders. **Need** explains the difference:

* A positive **Need** means the event still requires that quantity.
* `0` means the placed quantity covers the current plan.
* An **extra** value means the placed quantity is greater than the current plan.

For example, a plan for 18 stems with 10 stems on purchase orders still needs 8 stems. If 20 stems are on the orders, Summary shows 2 extra. These values compare purchasing with the recipe plan. They do not change the recipe itself.

An item can remain in Summary when its current planned quantity is zero if a linked purchase order still contains it. Review that row before deleting or changing an order because the placed quantity can affect the event's purchasing picture.

## Inspect where the numbers come from

Select the arrow beside an item to expand its sources. The purchase-order details show the order, delivery date, vendor, and quantity. The recipe details show the recipe quantity and the item quantity contributed by each recipe. Compare both sections with the parent row's **Qty.**, ordered quantity, and **Need**.

When an order is associated with more than one event, Summary can warn that the event view may be incomplete or inaccurate. Use **Manage Orders For This Event** to open **Purchasing**, where the shared order can be reviewed with all of its linked events.

## Review a quantity mismatch

An item can show a warning when its planning price and a purchase-order price use different quantities per group. Select the warning to open **Price Group Quantity Mismatch** and compare the planning price with the prices on the purchase orders. Different group sizes may be intentional, but the comparison helps explain why a group count or cost does not line up with the current plan.

You can update the planning price with **Edit Cost** on Summary or edit the item's price in the purchase order. Recheck **Group Qty.**, ordered quantity, **Need**, and the order total after either change.