Naver SmartStore Connector for Odoo — South Korea
Sync Naver SmartStore orders, inventory and dispatch through your own Naver Commerce API keys (BYOK)
Connect Odoo straight to your Naver Commerce API Center application. Pull SmartStore product-orders into Odoo Sales, accept paid orders, push courier and tracking numbers back as dispatch confirmations, and keep stock and price in sync per product — all driven by the Application ID and Secret issued to your own store. No third-party middleman, no data leaving your server except the calls to Naver you configure.
Key Features
Order Sync (pull)
A scheduled job and an on-demand button read the Naver
last-changed-statuses feed, page through every changed product-order,
and fetch full detail with product-orders/query. Product-orders are grouped
by their parent Naver order so each Odoo sale order aggregates the lines of one SmartStore
order with customer, Korean shipping address and delivery memo.
Line Resolution
Order lines are matched to your products by seller management code, then by Odoo internal reference, barcode, Naver SKU or origin-product number. Unit price comes straight from the payload, or is derived from the line total and quantity when Naver only reports the total.
Accept & Dispatch
Accept (place) paid orders on Naver with one click or automatically on import. Report the shipment back to Naver via the dispatch endpoint — the courier is resolved to a Naver delivery-company code (CJ Logistics, Hanjin, Lotte, Korea Post and more) and the tracking number is taken from the order or its delivery picking.
Bulk Dispatch Wizard
Select many Naver orders in the list, pick a courier, optionally apply one tracking number, and dispatch them all in a single action. Already-dispatched orders are skipped and per-order errors are reported without stopping the run.
Stock & Price Push
Push available quantity and sale price to your SmartStore listings by origin-product number, per product, in bulk from the product list, or via an hourly scheduled job. The connector reads the current origin product, mutates only stock and price, and writes it back so no other listing field is disturbed.
Secure BYOK Authentication
The connector mints short-lived OAuth2 bearer tokens using Naver's published bcrypt electronic-signature grant from your own Application ID and Secret. Tokens are cached and refreshed automatically. A Test Connection button validates your keys in one call.
How It Maps to Naver Commerce API
| Odoo action | Naver Commerce API endpoint |
|---|---|
| Mint access token | POST /external/v1/oauth2/token |
| Discover changed orders | GET /external/v1/pay-order/seller/product-orders/last-changed-statuses |
| Fetch order detail | POST /external/v1/pay-order/seller/product-orders/query |
| Accept / place order | POST /external/v1/pay-order/seller/product-orders/confirm |
| Dispatch / ship order | POST /external/v1/pay-order/seller/product-orders/dispatch |
| List / read products | POST /external/v1/products/search · GET /external/v1/products/origin-products/{no} |
| Update stock & price | PUT /external/v1/products/origin-products/{no} |
Built for Reliability
Rate-limit aware
Automatic retry with exponential backoff on HTTP 429 and 5xx, 30-second timeouts, and a unified API call log for troubleshooting.
Idempotent import
A unique constraint on the Naver order id means re-running a fetch never duplicates orders; existing orders only have their status refreshed.
Editable endpoint
The Naver base URL is configurable, so you can point at a reverse proxy or a future host without touching code.
Requirements
Odoo 18.0 or 19.0 (Community or Enterprise) · the sale_management and
stock apps · an active Naver Commerce API Center application with an
Application ID and Secret for your SmartStore.
This is a BYOK connector. It generates the Naver-format requests and transmits them using your own application credentials. It is not affiliated with or certified by Naver Corp.
Screenshots
Api Log
Naver Orders
Settings
Update date: 2026-07-02