> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/slab/content/blocks/cart/discount-input.md).

# Discount input

<figure><img src="https://3723856256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGnixyIfIYFWroNtVmZo6%2Fuploads%2Fgit-blob-aa5ba8bea977eedfd92e500e60febfd5bc79bb3a%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Overview

A discount code input block that allows customers to apply discount codes to their cart. Displays an input field with a button to apply the entered discount code.

## Common use cases

* Allow customers to apply discount codes in cart drawers or cart pages
* Ensure all translation keys are properly defined in locale files
* Configure button color to match your theme's design system
* Set appropriate padding based on surrounding content

## Block settings

### General

| Setting                | Description                 | Options                   |
| ---------------------- | --------------------------- | ------------------------- |
| Show advanced settings | Reveals visibility settings | Checkbox (default: false) |

### Spacing

| Setting                   | Description                                       | Options                   |
| ------------------------- | ------------------------------------------------- | ------------------------- |
| Enable horizontal padding | Adds horizontal padding around the discount input | Checkbox (default: false) |
| Enable top padding        | Adds top padding around the discount input        | Checkbox (default: false) |
| Enable bottom padding     | Adds bottom padding around the discount input     | Checkbox (default: false) |

### Color

| Setting      | Description                      | Options                                                                                                                      |
| ------------ | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Button color | Controls the button color scheme | <p>• Primary<br>• Secondary (default)<br>• Tertiary<br>• Neutral<br>• Plain<br>• Outline<br>• Inverted outline<br>• Blur</p> |

### Display

| Setting    | Description                        | Options                                                                                                                            |
| ---------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Visibility | Controls when the block is visible | <p>• All (default)<br>• Mobile only<br>• Desktop only</p><p><br><br>Visible when <strong>Show advanced settings</strong> is on</p> |


---

# 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://help.brickspacelab.com/slab/content/blocks/cart/discount-input.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.