> For the complete documentation index, see [llms.txt](https://guide.wiseapp.co.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.wiseapp.co.kr/notices/2026/07-27.md).

# 7월 27일 : \[와이즈리테일] 데이터 업데이트 안내

안녕하세요. 와이즈앱·리테일입니다.\
소매시장분석 리포트에서 총결제자수 데이터에서 이상이 발견되어 데이터가 재 업데이트되었습니다.

### 데이터 재 업데이트 대상 <a href="#undefined" id="undefined"></a>

* 대상 : 리포트
* 기간 : 2026년 1월 \~ 현재 / 월간

<a href="https://www.wiseapp.co.kr/wiseretail/ranking/retail-brand" class="button primary">와이즈리테일 바로가기</a>

감사합니다.

와이즈앱·리테일 드림


---

# 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://guide.wiseapp.co.kr/notices/2026/07-27.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.
