What this desk is, and what it is not

The short version

This is an information, tools and index site covering the HipoBuy purchasing route and the cross-border problems that follow it. It is organised by destination first, because the destination decides more about a haul than the goods do.

Information, tools and an index — not a shop. There is no cart, no stock state and no checkout here. When you want to see the goods themselves, the links go to a list site, and that relationship is disclosed on every page rather than buried in a footer.

Who writes it

The desk is edited by a small group who buy through this route themselves and who got tired of answering the same questions in chat threads. Everything published here started as a question somebody actually asked, which is why the answer pages are shaped as verdict, evidence and exception rather than as encouragement.

We use an editorial voice rather than individual bylines, and we say so rather than implying a larger organisation than exists. Our qualifications are practical: we have run hauls through this route, we have had parcels held, and we have paid invoices we did not expect. That is the extent of it, and we do not claim expertise we do not have on customs law or on carrier operations.

What we deliberately do not do

We do not publish prices, stock or availability, and we do not emit structured data describing an offer. Calls to action here describe what a destination site contains, not what it will cost you.
We do not mirror product photography. The visual system on this desk is typographic and diagrammatic, which is a design choice and also the reason the pages are light.
We do not publish coupon codes, and the method page explains the test that led to that decision.
We do not run accounts, comments or a newsletter. There is nothing to sign up for, and no personal data is collected beyond aggregate request counts.
We do not link to other sites in this category. Where we compare, we compare practices rather than pointing at competitors.

How to send a correction that gets acted on

Corrections are the most useful mail we receive, and most of the ones we cannot act on are missing one of three things. Include all three and the correction usually lands in the next review.

The page path. Not the page title, because titles change. A path looks like /regions/canada/ or /tools/volumetric/. If you send a screenshot instead, the address bar is the most useful part of it.
The specific claim. Quote the sentence or the table cell. A correction that says a page is wrong somewhere is one we have to re-research from scratch, which is slower than the correction itself.
What it should say, and how you know. A published source is ideal. Your own experience counts as well, provided we can label it as one report rather than as a rule.

Write to [email protected]. We reply when a change is made, and every content change is listed in the changelog with its date.

What happens when we get something wrong

Three outcomes are possible, and we try to distinguish them rather than treating every report the same way.

We were wrong: The figure changes, the review date changes, and the change is recorded in the changelog.
We were right but unclear: The wording changes rather than the figure. This is the most common outcome, and it usually means a label was too short to carry its own scope.
Neither of us can settle it: The claim is marked as unverified or as a single report, and the uncertainty is written into the page rather than resolved by preference. We would rather publish a stated uncertainty than a confident guess.