> 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/self-checkout-c18-sco.md).

# Self Checkout (C18 SCO)

{% hint style="info" %}
From Commander Release 57.02, suggestions can also appear while the sale is being rung up. See [Suggestions While the Sale Is Rung Up](https://commanderhelp.verifone.com/feature-references/features-and-products-references/smart-suggestion/using-smart-suggestion/suggestions-while-the-sale-is-rung-up.md).
{% endhint %}

| Scenario on the POS                                                          | Verified Behaviour                                                             |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Switch the lane POS ↔ SCO via App Selector                                   | Suggestions work on either side of the mode switch                             |
| Customer scans items and checks out; validates all panel prompts             | Panel renders to the customer with identical layout and text                   |
| Customer declines via 'No, Thanks' or the X icon; reappearance checked       | Both decline routes verified; checkout proceeds without a second press         |
| Customer orders a menu normally, adds multiple upsell products               | Menu + multi-product upsell verified in SCO                                    |
| Checkout press requirements after decline vs after accepting items           | Decline: no re-press needed. Accept: press Checkout again to refresh the total |
| Panel dismiss/reappear across repeated Checkout presses                      | Customer can still add suggested items on a later Checkout                     |
| Help pressed during an SCO suggestion                                        | Help available mid-offer; flow resumes                                         |
| Age-restricted upsell in SCO (cashier-assist mode)                           | Age check routed to the attendant as required                                  |
| 'Pay at counter' chosen before / after adding upsell items                   | Both counter-payment paths keep the upsell items intact                        |
| Adjustable vs non-adjustable items, maximum quantity, quantity limit in SCO  | Quantity rules enforced identically on self-checkout                           |
| SCO prepay fuel with a PLU suggestion                                        | Fuel prepay from the SCO with upsell verified                                  |
| Menu and message suggestion types on SCO, incl. age verification from a menu | All three suggestion types function in self-checkout mode                      |


---

# 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/self-checkout-c18-sco.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.
