EU consumer return rights and warehouse operating rules

Separate rights from tasks

The seller owns the customer policy and the legal interpretation. The warehouse owns execution once a parcel arrives. Mixing those roles creates poor decisions, such as restocking a disputed product, discarding evidence, or telling customer support that a refund is due. A good rule set starts by naming which return paths exist and which team may approve each outcome.

For withdrawal returns, the warehouse usually needs proof of receipt, product condition, accessory checks and packaging notes. For faulty-goods claims, the warehouse may need photos, defect descriptions, serial or lot data, and a hold status until the seller decides what happens next.

• Name each return path in the warehouse system
• Keep refund authority with the seller
• Define when goods are held rather than restocked

Receipt date and evidence

Return timing matters for customer support, but the warehouse should not decide whether a customer met a legal deadline unless that has been built into an approved process. The safer operational task is to capture the date received, carrier reference, return authorisation, parcel condition and any visible mismatch between the parcel and the expected return.

Evidence should be consistent. If photos are required, specify when they are taken, which angles are needed and where they are stored. If the customer included notes or accessories, the team should record them before any repacking or disposal step changes the state of the goods.

• Scan or record the return reference at receipt
• Photograph exceptions before handling changes the item
• Report unidentified parcels through an exception queue

Inspection states

A warehouse rule book should use a small set of inspection states that customer support and finance understand. Examples include unopened, opened but resaleable, missing component, damaged packaging, customer-reported fault, warehouse-confirmed damage and hygiene hold. The exact names matter less than using them consistently.

Some products need extra care because safety, hygiene, expiry or product rules can affect whether a returned item may be resold. The brand should obtain qualified product or legal advice where those restrictions apply, then turn that advice into concrete handling instructions for the fulfilment team.

• Use controlled condition codes
• Map each code to a permitted next action
• Train support teams on what each code means

Disposition authority

Disposition is the decision about what happens after inspection: restock, refurbish, replace packaging, hold for review, return to supplier, donate, recycle or dispose. The warehouse can execute these steps, but the seller should define who has authority, especially where value, safety or customer dispute evidence is involved.

Avoid vague instructions such as check and restock if fine. A better operating rule says which defects block resale, whether outer packaging damage matters, whether inserts must be replaced, and when a second review is required. That turns policy into repeatable work.

• Create a disposition matrix by product family
• Require seller approval for unclear or high-risk cases
• Keep disposal records where the brand requests them

Customer communication hand-off

The warehouse should feed customer support with facts, not promises. Useful facts include received date, item identity, condition code, missing items, evidence links and whether stock has moved to quarantine or restock. The support team can then apply the seller's policy and any legal guidance.

This hand-off is especially important when the customer expects a refund after sending goods back. The fulfilment workflow should make clear that physical receipt is not the same as refund approval unless the seller has explicitly designed it that way.

Exceptions and review rhythm

Returns expose weak master data quickly. Unknown SKUs, missing return references, mixed customer parcels and products without condition rules should be logged as exceptions rather than solved informally on the warehouse floor. Those exceptions show where the brand needs better portal settings, clearer customer instructions or more precise product data.

A monthly review can compare return reasons, condition outcomes, restock rates and unresolved holds without turning the warehouse into a legal adviser. The goal is operational control: fewer mystery parcels, faster decisions and cleaner evidence when the seller needs it.

• Review ageing held returns
• Update rules after new legal or product advice
• Keep withdrawal and faulty-goods reporting separate

Information to include in a fulfilment brief

• The warehouse records facts about a return; the seller keeps authority over refund and policy decisions.
• Withdrawal returns and faulty-goods claims need different evidence, condition codes and hold rules.
• Receipt date, carrier reference and parcel condition should be captured before inspection changes the goods.
• Disposition rules should say exactly when to restock, hold, refurbish or dispose of a returned item.
• Qualified legal or product advice is needed before setting resale rules for restricted or hygiene-sensitive products.
• A returns review should expose weak data and unclear decisions, not turn warehouse staff into policy makers.

VareYa can scope the warehousing and fulfilment work from a clear operating brief. Customs, tax, product and legal responsibilities should be checked with qualified advisers before inventory moves.

Questions teams often ask

Related VareYa Knowledge Center guidance

• EU returns solution for international brands
• Shopify returns in Europe
• VareYa versus traditional warehousing: fulfilment differences
• HS codes and customs data for ecommerce inventory
• Importer of record responsibilities for EU ecommerce inventory
• EORI numbers for ecommerce inventory entering the EU