> 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/cullinan-financial-transaction-services/configuring-cullinan-financial-transaction-interface/using-department-sales/department-sale-with-at-for-pricing.md).

# Department Sale with At-For Pricing

Pricing for some department items is based on purchase of a particular quantity for example, 3 candy bars for $1.00. This is known as At-For Pricing (@/pricing).

{% hint style="info" %}
At-For Pricing cannot be used with items sold in fractional quantities.
{% endhint %}

{% stepper %}
{% step %}
Enter the quantity

Key quantity being sold and press \[QTY].
{% endstep %}

{% step %}
Enter the pricing basis

Key number of items on which the price is based (for example, if the item sells three for $1.00, then key \[3]).
{% endstep %}

{% step %}
Enter the base price

Press \[QTY] and key the base price (for example, key \[1]\[0]\[0]).
{% endstep %}

{% step %}
Select the department

Do one of the following:

* Touch the department
* Press \[OTHER DEPT] and then touch the department in the Other Department list
  {% endstep %}
  {% endstepper %}

Recap: To ring up one unit of item that sells 3 for $1.00 - Press \[3] \[QTY] \[3] \[QTY] \[1] \[0] \[0] this will look on screen like 3\@3/100, then department.


---

# 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/cullinan-financial-transaction-services/configuring-cullinan-financial-transaction-interface/using-department-sales/department-sale-with-at-for-pricing.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.
