SB StartupBasket
All ideas
65 /100 VALIDATE Low complexity

Drempel — kwaliteitsscore forecaster for bol.com sellers

Projects a bol.com seller's 22-week quality score weeks ahead and names the orders to fix before each cliff.

Retail SaaS EU Marketplace-sellerDutch-firstPlatform-contractSolo-builderSMB
— views
Evaluation Scores
65/100

VALIDATE

Overall Score

14
Problem
10
Demand
12
Build
10
Distrib.
8
Revenue
7
Time
4
Defense

Drempel — kwaliteitsscore forecaster for bol.com sellers

1. One-liner

Projects a bol.com seller’s 22-week quality score weeks ahead and names the orders to fix before each cliff.

2. Trend signal — why now?

Three dated changes landed on 45,500 bol.com selling partners inside ten weeks, and all three turn one weekly number into money.

24 June 2026 — the score swap. bol retired the six-week, three-norm prestatiescore and replaced it in the koopblok (buy box) with the kwaliteitsscore: a 0–100 weighted average of five service norms (items on time, cancellations, track & trace, returns, customer questions) measured over a rolling 22 weeks. bol’s own partner page states the thresholds plainly: “Partners moeten minimaal een score van 65 halen”; “Bij een score vanaf 70 krijg je extra voordelen” (Select-deals); at 75+ a one-week delivery slip between 90–93% earns no strike. Below 65 you get a warning and four months to fix it before termination. ecommercenews.nl reported the change on 29 May 2026 and noted bol’s own warning that quality scores will “average lower” than the old performance score.

1 July 2026 — the score became a commission discount. Groeibeloning gives partners three personal quarterly revenue targets and unlocks up to a 10–15% discount on variable commission for hitting them. Entry requires a kwaliteitsscore of at least 69, a leverbeloftescore of at least 60, and a two-year-old account. dutchcowboys.nl called the catch on 26 March 2026: the discount becomes the norm for compliant sellers, so anyone under 69 is now structurally more expensive than their buy-box competitors.

3 September 2026 — strikes reached the API. bol’s Retailer Information API v11 beta added a Performance Status endpoint exposing “strikes and policy points, data not previously available via the API.” The weekly KPI scores behind the five norms have been available for 30 weeks of history via the performance-indicators endpoint for years. The kwaliteitsscore itself is not in the API yet; bol says it is “working to add the quality score to it during the beta.” So the inputs are programmatic, the output is not, and the projection is nobody’s.

The strike ladder is the hard stop. bol’s strike-process page: five strikes in the rolling 22 weeks and “je winkel tijdelijk gesloten” with three weeks to file an improvement plan; seven and the account closes for a minimum of one year. Strikes drop off exactly 22 weeks after they are earned, or earlier if you post two consecutive weeks at 98.5% on time, ≤0.5% cancellations and 90% of cases answered within 24 working hours. Every one of those dates is computable in advance. bol shows none of them as a calendar.

Complaint mine (Trustpilot, partnerplatform.bol.com, 2026): “van de 100 bestellingen heb ik 3 klantvragen… winkel 8 dagen gesloten als straf” (Marvin, April); performance score “dropped from 100% to 53% after undelivered package” (Anastassiya, June); a “negatieve aantekening/waarschuwing” after cancelling ~100 orders on a pricing error “despite taking immediate action” (Robin, 13 Aug); “harder ‘afgestraft’ m.b.t. strikes” (Noura, September). On higherlevel.nl a seller whose shop was closed after seven strikes was told by the community: “Je hebt hun vertrouwen namelijk 7x geschaad door het verkrijgen van strikes.”

Incumbent check: Boloo (Starter €29.95, Business €39.95, Enterprise €69.95/month, “10,000+ sellers” community) lists product research, listing AI, repricing, invoicing and a customer-support AI. Its own comparison page contains no mention of prestatiescore, kwaliteitsscore, strikes, response-time metrics or forecasting. Bolmate (from €15/month) shows the current score per logistics stream and “which products drive recurring issues” — a display, not a projection. Bollie sells outsourced customer service and openly pitches it as strike prevention. Nobody sells the calendar.

Provenance:

3. The opportunity

bol built a 22-week rolling meter, published four cash cliffs on it, and then gave partners a dashboard that only shows where the meter is today. That is the “free dashboard stops at history” shape. A seller who cancelled 100 orders in week 30 because of a pricing error does not need to be told their score dropped. They need to know that the cancellation norm will keep dragging the weighted average until week 52, what the score will read in each of the next eight weeks as good weeks push bad ones out, whether that path crosses 69 and forfeits the Groeibeloning discount for the quarter, and which specific open cases and untracked shipments this week would lift the trajectory fastest.

The Amazon world solved this a decade ago. Sellerboard, Helium 10 and Amazon’s own Account Health page project ODR and late-shipment rates against the published thresholds and tell sellers exactly how many more defects they can absorb. bol.com has 45,500 partners and a tooling ecosystem that stopped at product research and invoices. Boloo’s product tracker has “30+ layers and 8 unique ML algorithms” for finding products to sell; it has zero features for keeping the account that sells them alive.

The gap is fresh for three reasons. The old six-week score was short enough to eyeball. The new 22-week score is not; a single bad week now has a five-month half-life and the maths of when it stops hurting is genuinely non-obvious. Second, the score is not in the API, so the local tools that pull everything from the Retailer API cannot simply display it and have not bothered to reconstruct it. Third, the market is Dutch and Flemish only, so no international account-health vendor will ever ship a bol module. This is a niche exactly the right size for one builder and exactly the wrong size for everyone else.

4. Target market

  • Primary customer: The owner-operator of a Dutch or Belgian bol.com shop doing 100–3,000 orders a month, shipping via Verzenden via bol or their own carrier, often also on LVB. One to five people. bol’s own numbers put the average partner at €87,500 annual bol revenue and the median at €34,000; the top half of that distribution is the buyer. Roughly 15,000–20,000 shops.
  • Why they buy: In their words: “winkel 8 dagen gesloten als straf.” A closed shop is zero revenue; a lost koopblok is a 30–70% revenue haircut on the affected SKUs; a score under 69 is a 10–15% commission surcharge relative to the competitor who qualifies. The weekly score email is the moment of pain, and the current workaround is a spreadsheet or a phone call to an agency like Distilo, whose koopblok audit pitch quotes €5,000–€15,000 a month of recoverable revenue for a 200-SKU shop.
  • Rough TAM reasoning: 45,500 partners in total, declining from 52,000 in 2023 as bol tightens. Take 18,000 as the serious band. At €29–49 per month that is a €6–10M ceiling on bol alone. This is a €1–2M ARR business, not a €5M one, unless the same engine is pointed at Kaufland, Amazon.nl and Zalando’s partner programme, each of which runs its own rolling seller metric.
  • Why now for them: Before 24 June the score reset in six weeks and had no cash attached. Since 1 July it is a commission rate. Since 3 September their strike count is machine-readable. The first full 22-week window under the new score closes in late November 2026; every partner will discover the half-life problem at the same moment.

5. Product sketch (MVP)

  • Connect with the partner’s own Retailer API client credentials (created self-serve under Instellingen → Diensten → API Instellingen); pull 30 weeks of weekly KPI scores for all five norms plus the v11 strike and policy-point status.
  • Reconstruct the kwaliteitsscore per week and calibrate against the number bol displays in the verkoopaccount, so the projection matches bol’s rounding within a point.
  • Eight-week forward projection: “Assuming this week repeats, your score reads 72, 71, 70, 68… as weeks 31–34 age out.” Shown as a single line with the 65/69/70/75 cliffs drawn on it.
  • “This week’s list”: the open customer cases inside their 24-working-hour window, shipments missing a valid track & trace code, and pending seller-initiated cancellations, each tagged with how many points it is worth on the projection.
  • Strike calendar: each active strike with its earned week and exact expiry week, plus the two-week early-expiry condition (98.5% on time, ≤0.5% cancellations, 90% response in 24h) and whether the current week is on track to meet it.
  • Groeibeloning guard: distance from the 69/60 entry floor and from each of the three quarterly revenue targets, and the euro value of the commission discount at stake.
  • Unhealthy-stock alert: LVB units about to cross the 180-day line where storage is billed at +100% per month (from 1 January 2026), with the sell-through needed to avoid it.
  • Weekly Dutch-language email and WhatsApp digest the morning the score updates, in Dutch, with the projection and the list. Nothing else.

6. AI angle — what’s load-bearing

The projection is arithmetic, not AI, and I am not going to pretend otherwise. AI does two real jobs. First, the calibration: bol does not publish the norm weights or the per-category targets (“niet iedere categorie wordt hetzelfde beoordeeld”), so the weights are fitted per account from the displayed score against the API inputs; that is a small regression that has to converge fast and flag when bol changes the formula. Second, the triage: ranking which open cases and shipments to act on requires reading the case text, spotting the ones that will turn into a return or a cancellation, and drafting the 24-hour reply in Dutch or French. Boloo has a support AI; nobody has one that is scored against the servicenorm it protects. Remove the AI and you still have a useful projection and a worse to-do list. That is honest, and it is why defensibility scores low.

7. Localization angle (if any)

This is a localization play by definition. Dutch-first UI, Flemish and French for Belgian partners, iDEAL and SEPA direct debit for billing, pricing in euros, and a WhatsApp digest because that is where Dutch owner-operators read things. The vocabulary must be bol’s own: koopblok, servicenorm, strike, verkoopstop, leverbelofte, Groeibeloning. An English “seller health” product would be dead on arrival here, and that is the moat against Helium 10.

8. Business model — path to $1M–$5M ARR

  • Pricing: €29/month for one shop up to 1,000 orders; €59/month above that or with the triage and reply-drafting layer; €19/month per extra bol account. Annual at ten months.
  • ACV: €400–500 blended.
  • Rough math to $1M ARR: ~2,200 paying shops at €39 average, which is 12% of the 18,000-shop serious band. Aggressive for a single Dutch marketplace. €500K ARR at 1,100 shops is the realistic 18-month target and is a fine solo business.
  • Rough math to $5M ARR: Not on bol alone. Requires the same rolling-metric engine on Kaufland (seller performance score), Amazon.nl/.de account health and Zalando’s partner KPIs, sold as one “EU marketplace account-health” product to the ~40% of bol partners who also sell on Amazon or Kaufland. That is a year-two decision, not a launch premise.
  • Expansion path: per-account fees for multi-shop operators and agencies (Distilo, Bolscale, Marktscale run dozens of client accounts); the triage/reply tier; a white-label agency dashboard at €199/month.

9. Go-to-market wedge — first 100 customers

  • Complainers first. Trustpilot for partnerplatform.bol.com has a steady stream of 1–2 star reviews from named partners describing closed shops and collapsed scores. DM the 2026 reviewers on LinkedIn (most Dutch shop owners are findable) with a one-line offer: “Ik laat je zien op welke week je score weer boven 70 komt.” Expect 30 conversations, 10 connected accounts.
  • Free projection as the hook. A one-page tool: paste your five weekly percentages from the verkoopaccount and get the eight-week projection with the cliffs drawn. No API needed for the first look. Post it in the bol-seller Facebook groups and the Boloo community (10,000+ members), and on the r/ondernemers and higherlevel.nl threads where the strike ladder is discussed. Convert the “how do I see this every week” replies to the connected product.
  • Agencies as resellers. Distilo, Bolscale, Marktscale, Bol Specialist Almelo and a dozen similar Dutch bol agencies sell koopblok audits by hand. Offer each a white-label view of their client roster’s projections at a flat fee; five agencies at ten clients each is fifty accounts.
  • The November moment. The first full 22-week window under the new score closes around week 47. Publish a Dutch explainer (“Waarom je kwaliteitsscore in november pas écht zakt”) in October, timed for the discovery. This is content, but it is dated content aimed at a known moment, not evergreen SEO.
  • Bollie and the customer-service outsourcers. They sell response-time compliance and will happily bundle a tool that shows their clients the score moving; approach two of them with a revenue share.

10. Build complexity — justification

Low. The Retailer API is self-serve OAuth client credentials, the KPI endpoint hands back 30 weeks of numerator/denominator pairs per norm, and the v11 beta adds strikes and policy points. The custom work is the score reconstruction and its calibration against the displayed score, a projection routine, and a Dutch email/WhatsApp digest. A solo builder ships the projection in four weeks and the triage layer in another four. The risk is not engineering; it is that bol changes the weights silently and the calibration has to notice.

11. Gating checklist

GatePass?Note
Legal in target market✅Partner’s own API credentials; bol explicitly supports third-party authorised parties
Ethical — no harm / dark patterns✅Helps sellers meet bol’s own published norms; no gaming
Market exists (evidence above)✅Paid tooling at €15–70/month, agency audits, outsourced CS all sold against the same score
1–5 person team can build this✅Solo, eight weeks
Launchable with <$50K / ₹40L✅Under €5K

12. Feasibility score

AxisWeightScoreNotes
Problem intensity2014/20Shop closure and koopblok loss are hair-on-fire when they hit; for most partners the pain is a weekly number with a commission rate attached. Real, regular, not daily.
Demand evidence1510/15Boloo’s 10K community pays €30–70/month for adjacent tooling; agencies and Bollie monetise the same score by hand; Trustpilot complaints are specific and dated. Nobody is yet searching for a forecast by name.
Build feasibility1512/15Self-serve API, weekly inputs, small stack. Docked because the weights are unpublished and calibration is a moving target.
Distribution clarity1510/15Named channels: Trustpilot complainers, Boloo community, five named agencies, one dated November moment. Conversion rate is a guess.
Revenue mechanics158/15€29–59 pricing is benchmarked against Boloo/Bolmate. $1M ARR needs 12% of the serious band on one Dutch marketplace; $5M needs a second and third marketplace.
Time to first revenue107/10Free projection to paid connection is a 4–8 week funnel.
Defensibility104/10Boloo could add this in a quarter. When bol ships the score in the API, half the reconstruction moat disappears; the projection and the Dutch niche brand remain.
Total10065/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · sales-heavy — a Dutch-speaking builder who can read the Retailer API docs and DM shop owners on LinkedIn in their own language. Non-Dutch founders should skip this one.

Key assumptions to validate (3–5)

  1. Assumption: The kwaliteitsscore can be reconstructed within ±1 point from the five weekly KPI scores. How to test: Connect ten partner accounts, fit weights, compare to the displayed score for four consecutive weeks.
  2. Assumption: Partners will pay €29/month for a projection when bol shows the current score for free. How to test: Free paste-in projection page; measure the share of users who ask for the weekly version and pay within 14 days of the connected trial. Target 8%.
  3. Assumption: Boloo does not ship a score module within six months of launch. How to test: Watch their changelog monthly; keep the triage/reply layer as the differentiator they cannot copy by displaying a number.
  4. Assumption: The v11 beta’s strike endpoint reaches general availability and stays self-serve. How to test: Register for the beta today; confirm credentials work on a fresh partner account without manual approval.
  5. Assumption: Groeibeloning entry at 69 is a real money lever for the median partner. How to test: Ask 20 partners for their commission line and whether they qualified in Q3; if fewer than a third care, drop it from the pitch and lead with strikes.

Risk flags

  1. Platform dependency: One marketplace, one API, one country pair. bol has already tightened partner terms twice in 2026 (NL/BE establishment requirement, 180-day storage surcharge) and could restrict third-party API scopes at any time.
  2. Incumbent absorption: bol says it is adding the score to the API “during the beta.” Once it does, the reconstruction moat is gone and the pitch has to be entirely projection plus triage.
  3. Market ceiling: 45,500 partners and falling. This is a good solo business and a poor venture; a $5M path needs Kaufland and Amazon.nl, which brings Sellerboard and Helium 10 into the room.
  4. Vendor blogs disagree on facts: Agency posts quote a 40% surcharge at 270 days; bol’s own page says 100% per month at 180 days from 1 January 2026. Build against bol’s page and treat every agency number as unverified.

14. Structured verdict

Score:                  65/100
Verdict:                VALIDATE
Confidence:             Medium
Best-fit builder:       Dutch-speaking solo technical founder who already sells on bol or has run a bol agency
Time to revenue:        6–8 weeks
Capital to launch:      €3–5K
Top 3 assumptions to validate first:
  1. Score reconstruction accuracy — ten connected accounts, four weeks, ±1 point vs displayed score
  2. Willingness to pay for projection over bol's free current-score view — 8% free-to-paid within 14 days
  3. v11 strike endpoint is self-serve at GA — register a fresh partner account for the beta this week
Kill criteria:
  - Abandon if reconstruction cannot get within ±3 points on more than half of the ten pilot accounts after four weeks
  - Abandon if fewer than 5 of the first 50 free-projection users convert to a paid connected account within 30 days
  - Abandon if Boloo or Bolmate ships an eight-week score projection before the November window closes

15. Next step — 1-week validation sprint

  • Day 1–2: Register a bol partner account for the v11 beta; pull 30 weeks of KPI scores and the strike status from three friendly partner accounts (ask in the Boloo community; offer the projection free for life). Fit weights, compare to the displayed score.
  • Day 3–4: Ship the paste-in projection page in Dutch. Post it in two bol-seller Facebook groups and DM the ten most recent 1–2 star Trustpilot reviewers on LinkedIn. Count connected-account requests.
  • Day 5: Go if reconstruction is within ±2 points on all three accounts and at least 15 of the first 100 projection-page users ask for the weekly connected version. No-go if the weights will not converge or fewer than 5 ask.

Interested in a detailed proposal?

Get a deep-dive with market research, competitive analysis, and implementation roadmap.

Contact us

info@startupbasket.ai