Skip to content
Home Download
Guide

Naver Smart Store

Connect Naver orders to First Crack with Commerce API Client ID and Secret

Naver has no webhook, so First Crack polls for changed orders on a schedule.
Auth uses Commerce API Client Credentials + signature. (Official: Commerce API auth)

  1. Sign in to Commerce API Center.
  2. Register an application for the Smart Store (or sales channel) you will link.
  3. Copy:
    • Client ID (application ID)
    • Client Secret (secret — often looks like $2a$…)
  4. Use token type SELF. First Crack requests tokens with type=SELF.
  1. App → OrdersChannels
  2. Connect Naver Smart Store
  3. Enter:
    • Client ID
    • Client Secret
    • (Optional) display name — e.g. Main Smart Store
  4. Connect

The server validates by issuing a token and calling the order API. On failure, check keys, permissions, and store status.

  • Sync now: pull that channel (or all channels) immediately
  • Auto sync: periodic pulls when the server schedule is enabled

Collection (summary):

  • Changed product-order list → product order IDs
  • Detail fetch (up to 300 per call) → save as First Crack orders

Match channel product IDs / seller codes on order lines to First Crack product SKU.
Details: SKU mapping

Recommended:

  • Smart Store seller product code (sellerProductCode) = First Crack products.sku
  • Or register channel product / option codes as SKUs
Naver productOrderStatusFirst Crack
PAYMENT_WAITINGpending
PAYEDpaid
DELIVERINGshipped
DELIVERED / PURCHASE_DECIDEDdelivered
CANCELED / CANCELED_BY_NOPAYMENTcancelled
RETURNEDrefunded

Claims like CANCEL_DONE / RETURN_DONE map to cancel/refund first.

SymptomCheck
Connect / token errorsTypo in ID/Secret, bcrypt-style secret, SELF app
Zero ordersRecent changes? Paid status? Last sync time
401 GW.AUTHNToken expiry — next sync reissues. If repeated, reissue Secret

If it keeps failing, email Contact with display name, approx time, error text (never the Secret).