Structural prototype v1 · B-20 · This page is built, its copy is not written yet, and the panel below names exactly why.

Routing article · Structure only

Return or resolve a shop product issue

Route a physical product problem to the team that owns it.

Shop, privacy and safety Route: /help/shop-returns B-20 Wave 3, target 2027-01-31

Waiting on a decision, not on writing time

What is missing before this page can be written

Missing
Shop ownership after the migration, and the return process that will apply. The shop contact page also still carries placeholder sample text, which is a live trust defect independent of this page.
Who can answer it
Shop owner, to be named by Ivo
Recorded as
G-28 · AR-025 · AR-017 Wave 3
Planned release
Wave 3, target 2027-01-31

Nothing on this page is invented. The structure, the customer questions, and the routes are real; the answers stay blank until the owner above supplies the fact.

The questions this page has to answer

Taken from the FAQ export and the gap register. The questions are known; the approved answers are what is waiting.

  • My order arrived damaged or faulty. Who do I contact?
  • How do I return a product?
  • Is the shop the same support team as the site?

The shape it will take

The eleven-part article template from blueprint v3, section 9. Every launch article uses it, so the structure can be reviewed and designed now.

1. Title

Action-oriented, in the customer's words.

2. Introduction

One sentence, outcome first.

3. Applicability

Product, account state, device, region, or route this applies to.

4. Before you start

The short checklist that prevents a failed attempt.

5. Steps

Numbered steps, one action per step.

6. Expected result

What the customer should see when it worked.

7. Troubleshooting

The exception paths, in the order customers hit them.

8. What to collect

The details to gather first, so the first support reply can resolve it.

9. The correct route

Liss, human, processor, shop, or safety, whichever fits the problem.

10. Related help

The parent heading and the neighbouring articles.

11. Source and maintenance

Source, owner, last-updated date, review cadence, internal tags.

If you need help with this right now

While this page is being written, the working routes are unchanged. Ask Liss from the Help Hub, or contact VOD support with the account email, what happened, when, and what you already tried.

Never send a password or a full payment-card number.