The Netherlands and Belgium are typically the first international markets German DTC brands expand into. The proximity makes it attractive – shipping from a German warehouse to the Netherlands takes two to three days, and adding iDEAL as a payment method covers around 70% of Dutch online transactions.
On the forward logistics side, the expansion usually works well. On the returns side, it often doesn't. The reason is straightforward: the returns process was designed for one country, and the operational requirements for cross-border returns are meaningfully different from domestic ones.
We've seen this pattern repeatedly among German brands entering the Benelux. The forward journey works, customers start ordering, and within a few weeks the first returns come in. That's when the friction starts.
Carrier infrastructure varies by country
In Germany, DHL is the default. Most brands have a business contract with DHL, and drop-off points are dense across the country. A German customer returning a parcel is rarely more than a few minutes from a DHL point or Packstation.
In the Netherlands, PostNL controls roughly 60% of domestic parcel volume, with DHL at approximately 35% and DPD at around 5%. Dutch consumers expect PostNL return labels and access to PostNL's 5,000+ drop-off points. Sending them a DHL label works technically, but DHL's drop-off network in the Netherlands is significantly smaller. A customer in Groningen or Friesland may need to travel considerably further to reach a DHL point than a PostNL one.
In Belgium, bpost is the national carrier. Belgium itself adds a language layer: Flanders (Dutch-speaking) and Wallonia (French-speaking) have different ecommerce adoption patterns. Flanders behaves more like the Netherlands in terms of online shopping maturity. Wallonia behaves more like France.
If you're using a single German DHL contract for all markets, the return experience for your Dutch and Belgian customers is likely worse than what they're used to from local retailers. Unless you use DHL Retoure International – in which case DHL cooperates with the most widely used local carriers in each country.
Dutch return expectations are shaped by bol.com
Understanding return expectations in the Netherlands requires understanding bol.com. The marketplace handles roughly 45% of Dutch ecommerce and has set the benchmark for what Dutch consumers consider a normal return experience: click a button, get a PostNL label, drop the parcel at one of thousands of nearby locations, and receive the refund within days.
According to the Thuiswinkel Market Monitor, the Dutch ecommerce market reached €34.7 billion in 2023, with over 80% of Dutch consumers shopping online. That's one of the highest ecommerce penetration rates in Europe. These consumers are experienced, they have high expectations, and they compare every return experience to bol.com whether you like it or not.
For a German brand, this means that a returns process requiring an email to customer service, taking seven to ten days for a refund, or providing a DHL label when PostNL is expected, isn't just inconvenient – it's a reason to leave a negative Trustpilot review. The Netherlands has one of the highest Trustpilot adoption rates in Europe, and return experience features prominently in online reviews.
The marketplace returns layer
Many German brands expanding to Benelux also list on bol.com as a marketplace channel. This adds a separate returns management layer that's often underestimated.
Returns through bol.com follow bol.com's policies, not yours. The marketplace controls the customer return experience, the return window, and in many cases the refund timeline. Your returns management system needs to handle both direct returns (through your own returns portal) and marketplace returns (through bol.com's process) without the team manually reconciling two separate flows.
This is operationally complex. Most returns tools built for DTC brands assume all returns come through a single channel. Marketplace returns involve different carrier logic, different refund timelines, and sometimes different return addresses. Bol.com's seller documentation details these requirements, and they are distinct from what you'd configure for your own webshop.
VAT and return accounting across borders
Within the EU, cross-border returns don't involve customs. But VAT handling for international returns creates real accounting complexity. If you're shipping from Germany to the Netherlands under the EU One-Stop-Shop (OSS) scheme and a customer returns an item, the VAT adjustment needs to flow through your accounting system correctly.
For German brands, this means the returns platform needs to support DATEV-compliant export formats that handle cross-border transactions – not just domestic returns. If your DATEV export only covers German transactions and you're processing 200 Dutch returns a month, your bookkeeper or Steuerberater has a manual reconciliation problem.
Setting up cross-border returns properly
Based on what works for brands managing Benelux returns effectively:
1. Local carrier options per market
You need PostNL for the Netherlands and bpost for Belgium, in addition to your German DHL contract. Alternatively, DHL Retoure International can generate local carrier labels (like PostNL for Dutch customers) through your existing DHL integration. Your returns portal should automatically route the correct return label based on the customer's country. A Dutch customer gets a PostNL label. A German customer gets DHL. A Belgian customer gets bpost. This routing should be rule-based and automatic, not requiring manual intervention.
Carrier aggregators like Sendcloud, EasyPost, or Seven Senders offer multi-carrier access through a single integration, which simplifies the technical setup. The routing logic and carrier-specific settings still need careful configuration, though – not all aggregators support all local carriers equally well.
2. Returns portal in the local language
A Dutch-language returns portal isn't optional for the Netherlands. The returns portal, all status emails, the return policy page, and any communication during the return process should be in Dutch. According to Ingrid's research on the Dutch market, Dutch shoppers are multilingual and tech-savvy, but they show a clear preference for domestic ecommerce experiences.
For Belgium, you ideally need Dutch (for Flanders) and French (for Wallonia), on top of German for your home market. That's three languages for two additional markets, and your returns management platform needs to handle this at the portal level, the email level, and the policy level.
3. Country-specific return policies
Return windows and conditions may need to differ by market. Dutch consumers expect at least the EU-mandated 14-day withdrawal period, but many Dutch retailers offer 30 or even 60 days. Ingrid's benchmark data shows that approximately three quarters of top UK fashion retailers offer 28 to 30 days, and Dutch expectations are broadly comparable.
If your competitors in the Dutch market offer 30-day returns and you offer 14, that's a measurable conversion disadvantage. Your returns system needs to support different rule sets per country: different return windows, different carrier assignments, and potentially different return address routing.
4. Return address strategy
Shipping a return from the Netherlands back to a German warehouse costs more and takes longer than a domestic return. A single international return might cost €6–8 compared to €3–4 for a domestic German return. At 500 international returns per month, that's an additional €1,500–2,000 in return shipping costs alone.
For higher volumes, consider a return hub in the Netherlands or work with a fulfillment partner that offers one. Some brands use consolidation services: Dutch returns are collected locally, consolidated into bulk shipments, and sent to the German warehouse weekly. This reduces per-return shipping costs and improves the customer experience because the local drop-off is fast and nearby.
Exporto, which handles cross-border logistics for over 200 customers and 4.5 million parcels per year, is one example of a partner that can help manage cross-border return consolidation for DACH brands expanding internationally.
5. Marketplace and direct channel reconciliation
If you sell on bol.com alongside your own webshop, you need a documented process for handling returns from both channels. Where a direct integration between your returns platform and bol.com isn't available, a middleware sync (e.g., Tradebyte, ChannelEngine) can route marketplace orders into your primary shop system so returns can be processed in one place. At minimum, document separate return processes for each channel and make sure your warehouse team knows how to handle both. The worst outcome is marketplace returns getting lost in a process that was only designed for direct-channel returns.
The cost of getting this wrong
Cross-border return friction compounds. A Dutch customer with a poor return experience doesn't just not reorder – they leave a review, and that review is visible to every future potential customer in the market. In a market where bol.com has set the baseline for what "easy returns" looks like, your return experience is evaluated against that standard.
The Benelux opportunity for German brands is real. Geographic proximity, high average order values, and Europe's second-highest ecommerce penetration rate make it an attractive first international market. But the returns experience is part of the purchase decision for Dutch and Belgian consumers. They evaluate it before they buy.
Build the cross-border returns infrastructure before you launch in a new market, not after the first wave of complaints.
Automate and manage your returns easily starting now
Sources:
