N11 Store Score and Order Performance: How to Improve It
How the N11 store score is calculated and which order metrics drag it down. Fix approval time, dispatch time, cancellations and returns to raise your score.
The N11 store score is an average, over a set period, of how quickly you approve orders, how quickly you ship them, how many orders you cancel through your own fault, how many come back as returns and how customers rate you. Raising it is not one big move but the routine, order-level tracking of those five metrics. This guide explains how each metric affects the score and how a multichannel operation keeps them under control. For the marketplace basics, see our N11 integration overview.
Why the store score matters so much on N11
On N11 the product page belongs to the seller. Sellers listing the same product do not share a single page as on Amazon; they appear side by side in search results. The shopper decides which one to click based on the store score as much as on price, and the score is displayed prominently on both the product card and the store page.
That means visibility and score are the same thing on N11. A high-scoring store ranks higher in search, gets invited to campaigns and gets clicked without hesitation. A low-scoring store falls behind even when it lists the same product for less.
Because the score is a period average it neither drops nor recovers suddenly. One bad week of shipping can weigh on it for weeks. Managing the score is therefore not about reacting when it falls but about not letting it fall.
The metrics behind the score
N11 revises the weights and thresholds from time to time; check the performance page in your seller panel for current values. The logic of the metrics, however, is largely stable.
Order approval time
The window you are given to approve an order after it lands. An unapproved order is cancelled automatically after that window, and the cancellation is charged to you. For sellers who approve by hand, weekends and holidays are the biggest risk.
Dispatch time
The time between approval and handover to the carrier. Every package that exceeds the delivery promise shown on the product page pulls the score down.
Seller-caused cancellations
Orders you cancel for reasons such as no stock, wrong price or item not found. Cancellations initiated by the customer do not count here. In practice this is the metric that sinks a score fastest, because a single stock sync failure can produce dozens of cancellations in a day.
Return rate
The share of delivered orders that come back. Returns for wrong item, damaged item and "not as described" weigh the most; size exchanges are treated more lightly.
Customer ratings
The score and comments the customer leaves after the order. Shipping speed, packaging and communication decide this one.
The typical mistakes that lower the score
Most sellers whose N11 score has dropped share the same five causes:
- Orders seen late. The order lands in the N11 panel, but the team checks once a day. The approval window expires.
- Double selling. The item sold on Trendyol, N11 stock was not updated, and an N11 order arrived too. The result is a seller-caused cancellation. See stock synchronization and double selling.
- Forgotten shipping notification. The package went out, but the tracking number was never entered on N11. The system still counts it as being prepared.
- Misleading product content. Photos and descriptions do not match reality, and "not as described" returns climb.
- Unanswered customer questions. Pre-sale questions go unanswered and post-sale messages are seen late; the rating drops.
What these five have in common is that none of them is about price. They are all operational and information-flow problems.
A step-by-step plan to raise the score
The sequence for a store whose score has dropped, or that wants to keep it from dropping:
- Find out which metric fell. Read the five metrics separately on the performance page. Focus on the lowest one, not the average.
- Automate order approval. If the order writes to your system the moment it lands and passes a stock check, approval stops being a manual task.
- Move to a single stock pool. Every channel should see the same stock; an item sold on one channel should drop from the others instantly. This is the root of seller-caused cancellations.
- Tie shipping notification to the barcode. When the label prints or the package is scanned, the tracking number should go to N11 automatically.
- Keep the delivery promise realistic. If you cannot meet the promised time, lengthen it rather than shorten it; a late package hurts more than a longer promise.
- Classify return reasons. Give every return a reason code. Fix the content of products where "not as described" returns cluster.
- Set response times for questions and messages. Gather every channel's questions in one inbox and define who answers within how many hours.
- Establish a weekly check. Read the five metrics on the same day each week. Catch a decline in the first week, not at period end.
On N11 the score measures not what you did but what you failed to do: the unapproved order, the unreported shipment, the unanswered question.
Managing the score as a multichannel seller
If N11 is your only marketplace, the plan above is enough. If you sell on five, there is also a coordination problem. Every marketplace uses similar metrics with different time limits; a warehouse preparing Trendyol, Hepsiburada and N11 packages on the same day needs to know which is most urgent.
The answer is one list of every channel's orders, sorted by remaining time. The warehouse then works not on "N11 packages" or "Trendyol packages" but on "packages about to expire". Comparative channel reporting is covered in marketplace performance reports and KPIs, and the order flow itself in multichannel order management.
How it works with Bulutegra
Bulutegra pulls the N11 order through the N11 API the moment it lands, runs a stock check and writes it to your ERP with customer, line items and carrier; approval no longer depends on someone being at a desk. A single stock pool drops an item sold on N11 from every other channel instantly, removing the main cause of seller-caused cancellations, and low-stock alerts flag products approaching zero. When the warehouse scans a barcode, the tracking number goes to N11 automatically. The Integration Panel's order screen sorts every channel's packages by remaining time. The quality tab helps fix missing titles, colors and categories with one click, which trims a good share of "not as described" returns. N11 questions land in the CRM module's shared inbox alongside WhatsApp and email. Channel monitoring sends a notification to your phone when the N11 connection goes quiet.
To see how fixing the order flow raises your N11 store score, request a demo, or explore how it fits with your other marketplaces in the solutions section.
Frequently asked questions
How is the N11 store score calculated?
The N11 store score is an average, over a set evaluation period, of metrics such as order approval time, dispatch time, seller-caused cancellation rate, return rate and customer ratings. N11 can update the weights and thresholds, so check N11's seller help pages for the current calculation method.
What happens when my N11 store score drops?
A low score pushes your products down in search results, can block you from certain campaigns and reduces buyer trust. If the score falls below a threshold, N11 may warn the store or restrict sales. Knowing which metric caused the drop is the first step to recovery.
How long does it take for the N11 store score to recover?
Because the score is a period average, a fix made today does not show immediately; the score rises as old poor orders age out of the window. If you shorten approval and dispatch times and bring seller-caused cancellations close to zero, the difference shows in the next evaluation period. The exact timing depends on N11's current calculation window.
