> For the complete documentation index, see [llms.txt](https://docs.hub88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hub88.io/hubconnect-supplier-zone/supplier-promotions/brand-requests.md).

# Brand Requests

**Brand Requests** in the **HubConnect Supplier Zone** consolidate all Operators' proposed personalised promotions directly to you.&#x20;

Operators submit structured promotion requests — including product, games, brands, discount, and dates — and you review, approve, adjust, or decline them in one place.&#x20;

When you approve a request, Hub88 automatically creates the targeted promotion and opts in the requesting operator, with no manual coordination needed.

<div><figure><img src="https://3012741343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMTWFNZ1g2QuImiZFIO1o%2Fuploads%2FiABIwRyN7flLUEcjNArS%2FSupplier%20zone%20-%20promotion%20requests%20(3).png?alt=media&amp;token=8c1d64eb-d64a-41c9-b529-267a4d3b58d1" alt=""><figcaption></figcaption></figure> <figure><img src="https://3012741343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMTWFNZ1g2QuImiZFIO1o%2Fuploads%2F72D1DEUcGS7IQ3wwWM8v%2FSupplier%20zone%20-%20promotion%20requests%20(4).png?alt=media&amp;token=9640034a-c35a-4acf-9800-1544367094ce" alt=""><figcaption></figcaption></figure></div>

With Brand Requests, you can:

* **Review** incoming promotion requests grouped by operator brand.
* **Approve** requests individually or in bulk.
* **Propose changes** to the terms before approving.
* **Decline** requests with a clear reason for the operator.
* **Go live automatically** — approved requests become targeted promotions with the operator already opted in.

***

### Reviewing Requests

Incoming requests are available under **My Promotions → Brand requests**, grouped by operator brand with a count of new requests per brand.

To find and review requests, you can:

* Search by promotion name or game.
* Filter by promotion type, brand, date or period, and games.
* Expand a brand group to see its individual requests, including request ID and submission date.
* Open a request to see the full detail: operator name and brand, promotion name and type, product, games, dates, discount type and value.

<div data-with-frame="true"><figure><img src="https://3012741343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMTWFNZ1g2QuImiZFIO1o%2Fuploads%2FRSMRYhEZoNEHUNSZNRCm%2FSupplier%20zone%20-%20promotion%20request%20details%20(1).png?alt=media&amp;token=1cd16074-faef-4342-bfa3-bfdbc712a942" alt=""><figcaption></figcaption></figure></div>

For each request, you have three options: **Approve**, **Make Changes**, or **Decline**. You can also select multiple requests within a brand group to **bulk approve** or **bulk decline**.

{% hint style="info" %}
Operators often submit requests as monthly batches, so a single brand may send many requests at once. Bulk actions let you handle these efficiently while still opening individual requests when a closer review is needed.&#x20;
{% endhint %}

### Approving a Request

If the requested terms work for you, approve the request as submitted — individually or in bulk. On approval, Hub88 automatically:

* Creates the targeted promotion using the standard promotion creation rules.
* Opts in the requesting operator brand, the operator does not need to opt in separately.
* Notifies the operator that the promotion is ready.

The resulting promotion appears under **My Promotions** alongside your other promotions.

<div data-with-frame="true"><figure><img src="https://3012741343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMTWFNZ1g2QuImiZFIO1o%2Fuploads%2FRSMRYhEZoNEHUNSZNRCm%2FSupplier%20zone%20-%20promotion%20request%20details%20(1).png?alt=media&amp;token=1cd16074-faef-4342-bfa3-bfdbc712a942" alt=""><figcaption></figcaption></figure></div>

### Making Changes to a Request

If you want to offer different terms — for example a different discount value or date range — you can propose changes instead of declining.

<div><figure><img src="https://3012741343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMTWFNZ1g2QuImiZFIO1o%2Fuploads%2FpFvLIVcZmD3xeDF2HEKg%2FSupplier%20zone%20-%20edit%20promotion%20request%20(3).png?alt=media&amp;token=9d23bc4e-5b98-4640-8419-3e3bf25bd4d1" alt=""><figcaption></figcaption></figure> <figure><img src="https://3012741343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMTWFNZ1g2QuImiZFIO1o%2Fuploads%2FmelESqcpu4NMPsAzzwp0%2FSupplier%20zone%20-%20edit%20promotion%20request%20(4).png?alt=media&amp;token=6ec916b5-732d-4311-be82-9a852e1342e8" alt=""><figcaption></figcaption></figure></div>

1. Open the request and select **Make changes**.
2. Update the relevant fields. You can adjust the brand name, promotion type, product, games, discount value and type, start and end dates, restricted countries, terms and conditions, tech and positioning requirements, thumbnail, banner, and promotion materials URL.
3. Add a **note** explaining your changes. This is required and shown directly to the operator.
4. Submit. The request status changes to **Changes Made**, and the operator is notified to review.

<div data-with-frame="true"><figure><img src="https://3012741343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMTWFNZ1g2QuImiZFIO1o%2Fuploads%2FS46FSPYB5aatd4biyB1e%2FSupplier%20zone%20-%20edit%20promotion%20request%20(5).png?alt=media&amp;token=4552a2eb-e65e-4361-bf16-6c82bf5eb695" alt=""><figcaption></figcaption></figure></div>

The operator sees your updated values highlighted next to their original request, together with your note. They can then:

* **Accept your changes** the promotion is created with the updated terms and the operator is opted in automatically.
* **Decline your changes** the request is closed, and no promotion is created.

{% hint style="info" %}
**Changes to core deal terms (discount value or type, start and end dates, and games)**

These changes require the operator's confirmation before the promotion is created. Supplier-side details such as restricted countries, terms and conditions, tech or positioning requirements, and promotional assets are informational and don't require a confirmation round
{% endhint %}

Each request supports one change cycle. If the operator declines your changes, the request closes, as a new offer starts with a new request from the operator.

### Declining a Request

To decline a request, select **Decline** and provide a **decline reason**. The reason is required and is shown to the operator on their request.

Declined requests remain visible under **Declined requests** in Supplier Zone, so you can refer back to them at any time.

<div data-with-frame="true"><figure><img src="https://3012741343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMTWFNZ1g2QuImiZFIO1o%2Fuploads%2FRSMRYhEZoNEHUNSZNRCm%2FSupplier%20zone%20-%20promotion%20request%20details%20(1).png?alt=media&amp;token=1cd16074-faef-4342-bfa3-bfdbc712a942" alt=""><figcaption></figcaption></figure></div>

#### Request Statuses

* **Submitted** - A new request from an operator, awaiting your review.
* **Supplier Review** - You've opened or are reviewing the request.
* **Approved** - You approved the request as submitted; the promotion is created, and the operator is opted in.
* **Changes Made** - You proposed changes and the operator's confirmation is pending.
* **Accepted Changes** - The operator accepted your changes; the promotion is created, and the operator is opted in.
* **Declined by Supplier** - You declined the request.
* **Declined by Operator** - The operator declined your proposed changes and the request is closed.

#### Notifications

You'll receive notifications by email, in the dashboard banner, and in the bell notification centre when:

* An operator submits a new brand request, including batches with multiple requests.
* An operator accepts or declines your proposed changes.
* Requests are awaiting your action (reminder if no action is taken within a few business days).

Notifications link directly to the relevant request, and the notification centre lets you filter by read and unread.

***

### FAQ

**Can I approve or decline several requests at once?**\
Yes. Select multiple requests within a brand group and use bulk approve or bulk decline.

**Do I need to create the promotion after approving a request?**\
No. Approval automatically creates the targeted promotion and opts in the requesting operator brand.

**Can I negotiate terms with an operator?**\
Each request supports one change cycle: you propose changes once, and the operator accepts or declines them. For a different offer, the operator creates a new request.

**Does this replace my existing promotions?**\
No. Creating and managing your own promotions works exactly as before, see [Supplier Promotions](/hubconnect-supplier-zone/supplier-promotions.md). Brand Requests adds an operator-initiated path alongside it.

**Is there a deadline to respond to a request?**\
There's no hard deadline, but you'll receive a reminder if a request hasn't been actioned within a few business days. Operators can see the current status of their requests at any time.


---

# 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://docs.hub88.io/hubconnect-supplier-zone/supplier-promotions/brand-requests.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.
