datawebotCoupang product data: seller IDs, APIs & crawl rules
Map Coupang sellerProductId, productId and vendorItemId; compare seller and affiliate APIs, KR/TW scope, option-level stock fields and crawler rules.
Coupang's buyer site, seller API and Partners program expose different data
Coupang product research can start from a shopper-facing listing, a seller's authorized WING/Open API account, or Coupang Partners' affiliate tools. These are distinct interfaces with different identities and access: a public product page is not a seller inventory response, and a seller's own catalog API is not a market-wide feed.
Scroll to compare →
| Surface | Relationship and purpose | What it does not establish |
|---|---|---|
| Buyer-facing product pages | Shopper-visible product/catalog presentation, with market and page state | A complete set of all sellers, variants, stock or historic prices. |
| Coupang Open API | Seller-account management of registered listings, options, prices, stock, orders and operations | Read access to other sellers' private catalog or inventory. |
| Coupang Partners | Affiliate product promotion and partner reporting under its own program | Seller WING access or vendor-item inventory. |
| Robots and sitemap | Coupang's published crawl directives and sitemap location | Terms, API credentials or permission to collect data. |
Coupang uses separate IDs for seller listings, catalog products and options
Coupang's identifier FAQ, dated May 15, 2019, explains why these six API IDs should not be normalized into one SKU. Its current seller APIs still use the same field families. The 2026 product-identifier notice treats an officially verifiable GTIN or model number as separate product information, not a replacement for these seller, catalog or option keys.
Scroll to compare →
| Field | Coupang definition or use | Model it as |
|---|---|---|
| vendorId | Vendor ID issued by Coupang for a seller account | Seller/account context for the authorized API request. |
| sellerProductId | Seller's registered or listed product ID; 2019 FAQ says it cannot change | Seller-managed listing group, separate from the shared catalog. |
| productId | Exposed Coupang catalog product ID; 2019 FAQ says merge/unmerge can change it | Potentially changing catalog-match key, not the seller's permanent SKU. |
| sellerProductItemId | Seller option ID needed when modifying option values | Seller's option row and update operation. |
| vendorItemId | Coupang option ID queried for item-level price, stock and sale status; FAQ calls it a stable lowest-level key | Selected purchase option, distinct from the product group. |
| externalVendorSku | Seller-entered product code | Seller-maintained reference; never a Coupang-wide identifier. |
Seller product-list queries are vendor-scoped and paginated
The Coupang Product list paging query documentation, checked October 4, 2026, requires vendorId and uses nextToken to retrieve later pages. It identifies Korea and Taiwan as the available buyer markets for this endpoint and documents a maximum page size of 100. The response describes the specified vendor's registered product records, not the whole public marketplace.
Scroll to compare →
| Request or response field | Documented meaning | Capture with it |
|---|---|---|
| vendorId | Required seller ID issued by Coupang | Authorized account and buyer market. |
| nextToken | Page token; null when there is no next page | Request sequence and completion state. |
| maxPerPage | Results per page; default 10 and maximum 100 | Requested page size and response count. |
| sellerProductId and productId | Seller listing ID and exposed catalog product ID | Preserve both, even when one product appears in a shared catalog. |
| statusName | Under review, temporarily saved, awaiting approval, approved, partially approved, denied or deleted | Source status and capture time. |
| category, brand and sale dates | Display category code, category, brand and sale-period fields | Current seller listing context; category schema can change. |
Stock, salePrice and onSale are option-level observations
Coupang's Query quantity/price/status endpoint, checked October 4, 2026, takes vendorItemId and returns item-level amountInStock, salePrice and onSale. Its own response example pairs zero stock with onSale: true. Preserve stock quantity and sale status independently; the latter does not prove an item can be bought or that checkout will succeed.
Scroll to compare →
| Field or amount | Where it appears | Interpretation |
|---|---|---|
| amountInStock | Inventory response for one vendorItemId | Reported remaining quantity for that seller's option at response time. |
| salePrice | Option inventory response and product-option fields | Seller-side current amount; keep source currency and account context. |
| onSale | Inventory response boolean | Sale status can be true while reported stock is zero. |
| originalPrice | Product creation/option field used as a discount base | Keep distinct from salePrice and from a buyer's final checkout amount. |
| Timestamp | Your API response time and market context | A dated seller-side observation, not a completed transaction or history by itself. |
Category attributes and approval state can affect product exposure
Coupang's Product list paging query, Product creation docs and May 27, 2026 Product Identifier Requirement notice describe different exposure checks. The API names missing verification and mandatory-option flags as suppressed, invalid attributes as low-impression, and missing category-required options/attributes as registration or exposure restrictions. The identifier notice says to enter a GTIN/model number only for branded products with officially verifiable identifiers; it says not to substitute a seller SKU or option value.
Scroll to compare →
| API evidence | Coupang's stated outcome | Useful check |
|---|---|---|
| IN_REVIEW / APPROVING / PARTIAL_APPROVED | Under review, awaiting approval or partially approved | Keep each status separate from a live buyer offer. |
| NO_VA_V2 | Products that need verification; documented as suppressed | Record violation status and category/product scope. |
| MOTA_V2 | Missing mandatory option values; documented as suppressed | Check the category's required size/color or other option fields. |
| ATTR | Invalid attributes; documented as low impression | Validate against the current category metadata and required value names. |
| displayCategoryCode and attributes | Category and option values are required or category-governed during registration | Store the category metadata version and each option/value pair. |
| GTIN/model number | May 27, 2026 Coupang notice; API registration effective August 1, 2026; applicable categories and brands expand sequentially | Use an officially verifiable product identifier when one exists; never repurpose externalVendorSku, inventory code or option combination. |
Korea, Taiwan and fulfillment programs are separate dimensions
The cited product endpoints name Korea and Taiwan as supported buyer markets, while the developer portal lists separate product, CGF/CGF Lite and Rocket Growth API families. A market code is not a fulfillment mode. Preserve the endpoint, market and logistics program so a seller-side listing is not presented as a buyer's delivery promise.
Scroll to compare →
| Dimension | Evidence to preserve | Avoid assuming |
|---|---|---|
| Buyer market | KR or TW as documented by the endpoint or request context | That every endpoint, category or seller field is identical across both markets. |
| Seller account | vendorId and account authorization | That an Open API key sees unrelated sellers' private records. |
| Logistics/product family | Standard seller product, Rocket Growth, CGF or CGF Lite endpoint path | That the shared Coupang brand means all inventory follows one fulfillment workflow. |
| Shipping and returns | Seller-configured method and location fields from product creation or logistics endpoints | A quoted shipping method as a current delivery promise for every buyer. |
Coupang Partners affiliate data does not replace seller inventory
Coupang's current Partners portal describes a separate affiliate flow: display partner product ads on a partner site, a visitor clicks through and buys on Coupang, and the partner relationship includes commission, reporting and settlement. That public description does not provide a seller's WING registration, vendorItemId inventory or seller-management access.
Scroll to compare →
| Record | Relationship | Do not map it as |
|---|---|---|
| Affiliate product or referral | Partner program discovery and promotional link/reporting context | SellerProduct listing or inventory response. |
| Seller Open API product | Authorized seller's registered listing and purchase options | Affiliate conversion or public competitor catalog. |
| Buyer page | A storefront representation for a specific market and page state | A seller API response or completed order. |
Coupang robots.txt blocks OpenAI crawlers and unspecified bots
In Coupang's robots.txt file checked October 4, 2026, the company explicitly disallows GPTBot, ChatGPT-User and OAI-SearchBot from /. Its final User-agent: * group also disallows /. Named Googlebot, Bingbot, Naver/Yeti and Daum groups publish different, selected path rules. These directives describe Coupang's crawler policy for those user-agent groups; they do not establish how any other AI system retrieves or answers about products.
Scroll to compare →
| Crawler group in the file | Published rules | Discovery implication |
|---|---|---|
| GPTBot, ChatGPT-User, OAI-SearchBot | Each has `Disallow: /` | These named OpenAI crawlers are not invited to fetch Coupang URLs directly. |
| Wildcard `*` | `Disallow: /` | Unspecified crawlers are disallowed by the catch-all group. |
| Googlebot, Bingbot, Naver/Yeti, Daum | Named groups allow selected product, category, campaign and search paths | Traditional search crawler policy is not the same as the OpenAI groups. |
| Operational paths | Cart, direct orders, vendor-items and other paths are disallowed for named search agents | Do not confuse private or transaction paths with public product discovery. |
| Sitemap reference | The file lists `https://www.coupang.com/sitemap/sitemap.xml` | A sitemap URL does not override the crawler directives above. |
Treat crawl rules, API credentials and marketplace data as different boundaries
Coupang's robots file sets crawler directives; its Seller Open API is a signed, vendor-authorized interface; the Coupang Partners portal describes a separate affiliate program. None establishes the access, permissions or coverage of the others. For each record, retain the exact source interface, account relationship, market, field grain and observation time.
Scroll to compare →
| Evidence | What it can support | What it cannot establish by itself |
|---|---|---|
| Robots file | Crawl directives for named user agents and wildcard bots | Legal permission, product API availability or an exception to account controls. |
| Seller Open API | Documented access to an authorized vendor's own operations | Access to another seller's private listing, orders or inventory. |
| Coupang Partners portal | Affiliate ads, click-through purchases, commission and partner reports/settlement described by Coupang | Seller account credentials or a market-wide seller feed. |
| Buyer listing | Displayed product/catalog information at a particular time and market | A complete catalog or historical price/stock series. |
Content reviewed 2026-10-03.