> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/how-do-i-create-submit-claims-and-returns-b2b.md).

# How do I Create / Submit Claims & Returns (B2B)

{% hint style="info" %}
Mind you this guide explains how to send a claim in a B2B basis, for B2C you should follow a self service portal in the Retailer or Supplier website.
{% endhint %}

#### &#x20;Steps to Submit a Ticket as a Retailer:

**1. Go to New Ticket and select the right brand**

<figure><img src="/files/Zka1mqtbVu4uoXgn479I" alt=""><figcaption></figcaption></figure>

**2. Choose Ticket-type:**

<figure><img src="/files/rJhAj7He882IFcEFFvsa" alt=""><figcaption></figcaption></figure>

**3. Add Product details:**

<figure><img src="/files/QBs7zifoaC4qJbxnO59G" alt=""><figcaption></figcaption></figure>

\- Click on “Save Product”.

**4. Proceed – optionally add more products:**

Add another product or click on “Next - Review Case” to proceed.

<figure><img src="/files/lTNRLE79Jzv5xxyojqrS" alt=""><figcaption></figcaption></figure>

**5. Review and Submit:**

<figure><img src="/files/IP728iOp8ZdyHjguPXPR" alt=""><figcaption></figcaption></figure>

\
**​Common Challenges When Submitting Tickets:**

Challenge 1:

You cannot find the product information, or it shows an error.

\- First, check the brand’s guide to see what format they use.

\- If your data input is correct but still shows an error, click on “I can’t find my style number” and then click “OK” on the pop-up screen to proceed. This will allow you to submit the case.

Challenge 2:

Forgetting to click “Next - Review Case” and “Submit Case”.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/how-do-i-create-submit-claims-and-returns-b2b.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
