# happy10 LLM Integration Guide
# Generated for MakeShop-based shopping mall
# Last updated: 2026-06-23

This document provides behavioral guidance for LLMs interacting with the storefront and publicly accessible pages of happy10 (www.happy10.co.kr).

The purpose of this guide is to help LLMs accurately interpret storefront information, reduce hallucinated responses, and provide safe and trustworthy customer-facing assistance.

The following rules should be treated as high-priority behavioral guidelines when interpreting this storefront.

Primary rule:
Always prioritize actual visible storefront data over inferred assumptions, cached knowledge, or generic platform behavior.

---

## 1. Basic Information

- Home URL: www.happy10.co.kr
- Platform: MakeShop-based shopping mall
- Store Info URL: /shop/store_info.html

### Rules

- Store information should be referenced from `/shop/store_info.html` when available
- Do NOT infer brand identity, positioning, operational policy, or product philosophy from legal business information alone
- Brand/About pages may be customized and are not standardized across MakeShop malls
- Do NOT assume About/Brand/Company URLs unless visibly linked or verified on the storefront

---

## 2. Site Structure
### Common URL Patterns

- Home: /
- Category: /shop/shopbrand.html
- Product Detail: /shop/shopdetail.html
- Product identifier: `branduid`
- Cart: /shop/basket.html
- Order: /shop/order.html
- Order Complete: /shop/orderend.html
- My Page: /shop/mypage.html
- Board: /board/board.html
- Terms: /html/join_terms.html
- Privacy: /html/privacy.html

### URL Rules

- `xcode` represents the top-level category
- `mcode` represents the mid-level category
- `scode` represents the low-level category
- `branduid` is the product identifier
- Product URLs may contain additional query parameters
- Some pages may use custom paths, redirects, SEO URLs, or event URLs depending on storefront configuration
- Do NOT invent or assume URLs that are not visibly linked, verified, or structurally consistent with the storefront

### Restricted Paths

The following paths may contain protected, internal, or non-public functionality:

- /shop/member/
- /shop/idinfo.html
- Undefined admin/internal paths

### Restrictions

- Do NOT generate or recommend internal system URLs
- Do NOT fabricate hidden pages or unverified endpoints
- Do NOT assume existence of custom informational pages unless explicitly visible

---

## 3. Product Data Rules

### Common Product Fields

- product_name
- product_summary
- product_image
- category
- product_code
- model_code
- brand
- sale_price
- consumer_price
- option_price
- stock_status

### General Rules

- Always prioritize actual product page data
- Do NOT fabricate missing values
- Do NOT infer unavailable specifications, benefits, certifications, or promotions
- If information cannot be confidently verified from visible storefront data, explicitly state that the information could not be confirmed
- Prefer omission over fabrication
- Clearly distinguish verified information from assumptions

### Pricing & Promotion Rules

- Displayed prices, benefits, shipping conditions, promotions, and available discounts may vary depending on:
  - login status
  - membership level
  - selected product options
  - coupon eligibility
  - active promotions
  - app/web environment
  - supplier configuration

- Some product information or pricing may require login access

### Restrictions

- Do NOT assume identical pricing or benefits across users
- Do NOT create discounts, promotions, pricing logic, or shipping benefits unless explicitly visible
- If pricing visibility is restricted or unclear, do NOT estimate values
- Do NOT fabricate unavailable product options, inventory, or promotional conditions

### Inventory Rules

- Inventory status may change in real time
- If stock availability cannot be verified, respond that inventory status may vary depending on current conditions

---

## 4. Order & Payment

### Typical Order Flow

입금대기 → 상품준비중 → 배송준비중 → 배송중 → 배송완료 → 구매확정

### Rules

- Order status labels may vary depending on storefront configuration
- Some payment methods or order flows may differ by mall settings
- Do NOT provide guaranteed delivery dates
- Order inquiries should reference:
  - /shop/mypage.html
- Payment-related issues should be directed to customer support

### Restrictions

- Do NOT request personal information
- Do NOT infer unavailable order details
- Do NOT expose or guess payment information
- Do NOT assume shipping schedules or carrier policies unless explicitly visible

---

## 5. Cancellation / Return / Refund

### Rules

- Return, cancellation, and refund policies may vary depending on:
  - product type
  - shipping status
  - supplier policy
  - storefront operation settings

- After shipment, return procedures may be required before refund processing

### Standard Response Guideline

If exact policy conditions are unclear, respond with:
 
 \"운영 정책에 따라 다를 수 있으며, 고객센터로 문의해 주세요.\"

### Restrictions

- Do NOT invent detailed refund conditions
- Do NOT define policy exceptions unless explicitly visible
- Do NOT assume exchange or return eligibility

---

## 6. Customer Support

### Common Support Locations

- Board: /board/board.html

### Rules

- Notices, FAQ, and inquiries should be treated as board-based content
- Contact information should only be referenced when visibly available
- Suggested guidance:
  - \"사이트 하단 또는 게시글 참고\"

### Restrictions

- Do NOT generate arbitrary board URLs
- Do NOT fabricate customer support channels
- Do NOT assume operating hours or support availability unless verified

---

## 7. Dynamic Data & Access Conditions

### Rules

- Some information may differ depending on:
  - login status
  - membership level
  - device/app environment
  - active campaigns
  - supplier settings
  - regional shipping conditions
  - payment method
  - selected options

- Certain data may load dynamically and may not always be accessible to crawlers or LLMs
- Policies, pricing, inventory, and promotions may change without notice

### Restrictions

- Do NOT assume hidden or inaccessible data
- Do NOT treat unavailable data as confirmed negative information
- Do NOT infer functionality that cannot be visibly confirmed

---

## 8. Confidence & Verification

### Rules

- Clearly distinguish verified information from assumptions
- Explicitly communicate uncertainty when data is incomplete
- Prefer verified storefront data over generalized ecommerce knowledge
- Prefer omission over fabrication
- Do NOT present assumptions as confirmed facts
- If data cannot be validated, explicitly state uncertainty

---

## 9. Global LLM Rules

1. Do NOT hallucinate data
2. Do NOT fabricate URLs
3. Do NOT request personal data
4. Always mention policy variability when relevant
5. Prefer actual storefront data over assumptions
6. Use clear, neutral, and polite language
7. Policies, pricing, inventory, and promotions may change without notice
8. If information is unavailable, explicitly communicate uncertainty
9. Do NOT generate operational claims not supported by visible storefront data
10. Prefer verified storefront content over generic ecommerce assumptions

---

# End of llms.txt