# Curate menu recommendations for each channel

**Console: Settings → Location settings → Recommendations.** For the menu lead
choosing useful additions to an order. Confirm the location, real product
availability and the guest/staff channel before editing.

## Build the lists

1. Under **Featured upsells**, open **Default** and use **Add item** to select
   appropriate saved products. A list can hold up to eight items.
2. Drag to reorder the list and remove picks that are no longer appropriate.
   Review each product, price and actual selling availability.
3. Open **Dine-in**, **Pickup**, **Delivery**, **Counter**, or **Kiosk** to
   create an order-type override. A nonempty override replaces the Default list
   for that type; it is not an addition to it.
4. Read **Using Default** or **Override active** before editing. An empty
   override uses Default. **Use Default instead** clears the draft override;
   save and reopen to verify the intended saved state.
5. Review all changed scopes before the page save. Reopen and check the same
   location afterwards; the selected tab alone does not limit other draft
   changes being saved.

## Decide who should see a pick

Open the item's settings and review **Operator-only**. This is a flag on the
recommended item and can affect that item across the lists using it. It keeps
that recommendation on staff surfaces rather than customer-facing ones; it is
not the catalogue's separate staff-only product setting or an access grant.

Check the guest ordering drawer, kiosk checkout and staff recommendation surface
where used. A configured list is not a promise that every pick appears. Items
already selected, sold out or ineligible for the channel can be withheld, and
surface layouts show different numbers of candidates. Active dietary filters and
warnings still need verified kitchen information; they do not certify a dish
safe for an allergy.

## Review assisted suggestions

In **AI Copilot**, confirm the current scope, add a useful optional hint, then
use **Generate for …**. Review the proposed items, reasons, prices and
suitability for this restaurant before **Apply to …**.

Apply replaces that scope's draft list with the suggestions. It does not itself
save the location configuration. Review the resulting order, staff-only flags
and other changes, then save and verify. **Discard** in the suggestion card
removes the generated proposal; the page's draft/save controls are separate.

Generated reasons are proposals, not verified menu facts or authority to change
allergens, prices, availability or promotions. Do not include guest contacts,
credentials or private staff notes in a hint.

## Set coaching goals

**Average order value target** uses the location's currency. **Attach-rate
target** is the percentage of orders that include an upsell addition. These are
operator coaching targets, not guaranteed results, automatic discounts or a
requirement imposed on guests. Review actual outcomes in the appropriate reports
on the same basis.

## Verify and recover saved settings

After saving, reopen every affected scope and inspect the actual guest/staff
flow. In the current implementation, clearing an existing override, switching a
staff-only flag off or blanking a goal needs particular care: a draft change may
not clear the previously saved value. If the old value returns, preserve the
result and ask the authorised settings owner/support to resolve it. Do not
broaden other channels or remove catalogue items as a workaround.

After a timeout, reopen the same location before applying suggestions or saving
again. Keep location, scope, product, intended/saved setting, affected surface
and exact error for support. See [Menu setup](/guides/menu-management),
[Menu recovery](/troubleshooting/menu-availability), and
[Kiosk setup](/settings/location/kiosk).