> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/smart-suggestion/using-smart-suggestion/basic-sales-with-plu-suggestions.md).

# Basic Sales with PLU Suggestions

| Scenario on the POS                                                                | Verified Behaviour                                                                                                                                          |
| ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scan items, press Total, add one suggested product, pay cash                       | Panel shows prompt message, four product tiles with prices, disclaimer, and both buttons; selected item added at qty 1; receipt and transaction log correct |
| Add one suggested product with quantity raised to 3 via '+'                        | Quantity Bar increments correctly; all 3 units added and priced on the receipt                                                                              |
| Ring a product normally, then add 4 more of a suggested product                    | Regular and upsell quantities combine correctly in the basket                                                                                               |
| Scan an item, accept a suggestion, pay by EMV credit                               | Panel completes before card flow; EMV insert/tap proceeds normally                                                                                          |
| Select multiple different products in one panel session with individual quantities | Each tile keeps its own quantity; all selections added on one 'Add To Cart'                                                                                 |
| Trigger the suggestion from an expanded-menu item instead of a scan                | Menu-based basket entries match rules identically to scanned PLUs                                                                                           |
| Trigger from an overlay-menu item, then decline                                    | Panel appears for menu triggers; decline leaves basket unchanged                                                                                            |
| Department sale in the basket alongside suggestion-triggering items                | Department sales co-exist with the panel; upsell items added normally                                                                                       |
| Repeat of the core accept/decline flows with the 'total required' flag disabled    | With the flag off, tender proceeds without a second Total press in all paths                                                                                |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/smart-suggestion/using-smart-suggestion/basic-sales-with-plu-suggestions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
