> For the complete documentation index, see [llms.txt](https://shopping-docs.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shopping-docs.toss.im/shopping-operations/price.md).

# 가격 관리

- [기간판매가 등록하기](https://shopping-docs.toss.im/shopping-operations/price/register.md): 기간판매가를 등록하는 방법이에요.
- [기간판매가 수정하기](https://shopping-docs.toss.im/shopping-operations/price/register/edit.md): 기간판매가를 수정하고 종료하는 방법이에요.
- [가격 관리 사용하기](https://shopping-docs.toss.im/shopping-operations/price/management.md)
- [셀러 부담 쿠폰 생성하기](https://shopping-docs.toss.im/shopping-operations/price/seller-coupon.md): 이제 토스쇼핑 파트너스를 통해 직접 셀러 부담 쿠폰을 생성 할 수 있어요.
- [장바구니 알림 쿠폰 생성하기](https://shopping-docs.toss.im/shopping-operations/price/undefined.md): 장바구니에 상품을 담았지만 구매하지 않은 고객에게 쿠폰을 자동 발급하여 구매 전환을 유도해보세요.


---

# 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://shopping-docs.toss.im/shopping-operations/price.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.