> For the complete documentation index, see [llms.txt](https://support.gamoshi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.gamoshi.com/gamoshi-wiki/general-information/inventory-incoming-request-workflow-overview.md).

# Inventory Incoming Request Workflow Overview

## Overview

This article provides a high-level overview of how the Gamoshi platform processes incoming inventory requests before sending them to an advertiser.

After you configure inventories and advertisers in your account, requests begin arriving from your inventory partners. Each request passes through a series of validation, filtering, capping, list-processing, and mapping stages. The platform then identifies the relevant campaigns and advertisers and sends the processed request to the applicable advertiser.

The advertiser runs the RTB auction and submits a bid. The winning bid is returned to the publisher.

***

## Incoming Request Workflow

{% stepper %}
{% step %}

### Receive the Inventory Request

The request is received in your account from an inventory partner.
{% endstep %}

{% step %}

### Validate the Request

The platform validates the incoming request according to the applicable RTB protocol guidelines.
{% endstep %}

{% step %}

### Apply Inventory Filters and Capping

The platform applies the filters and capping settings configured for the Inventory.
{% endstep %}

{% step %}

### Process SCHAIN and PCHAIN

The platform automatically processes the request’s SCHAIN and PCHAIN information.

* If the original request contains an SCHAIN object, the platform adds a node.
* If the request does not contain an SCHAIN object, the platform creates one with a single node.
* The node values are taken from the Business Partner’s sellers information when available. If this information is not configured for the Business Partner, the values are taken from the Inventory’s sellers information.
  {% endstep %}

{% step %}

### Process Inventory Allow Lists and Block Lists

The platform applies the allow lists and block lists configured for the Inventory.
{% endstep %}

{% step %}

### Process Inventory Mapping Rules Defined as an Allow List

The platform processes Inventory mapping rules defined as an allow list.
{% endstep %}

{% step %}

### Process Inventory Mapping Rules

The platform applies mapping rules in the following order:

1. Rules defined for all Inventories.
2. Rules defined specifically for the Inventory.
   {% endstep %}

{% step %}

### Identify Valid Campaigns

The platform determines which campaigns are valid for the incoming request.
{% endstep %}

{% step %}

### Apply Campaign and Advertiser-Level Settings

For each valid campaign and advertiser, the platform processes the applicable filters, allow lists, block lists, and mapping rules.
{% endstep %}

{% step %}

### Process Advertiser Mapping Rules

For each advertiser that remains relevant after filtering and list processing, the platform applies mapping rules in the following order:

1. Rules defined for all Advertisers.
2. Rules defined specifically for the Advertiser.
   {% endstep %}

{% step %}

### Send the Request to the Advertiser

After all processing stages are completed, the request is sent to the relevant advertiser.
{% endstep %}
{% endstepper %}

***

## Understanding Request Sampling

{% hint style="info" %}
When sampling an Inventory, the sample displays the raw request before mapping rules are applied.

To review the request after mapping-rule changes have been applied, create the sample at the Advertiser level.
{% endhint %}

***

## Related articles

* [Gamoshi Open RTB Specification](/gamoshi-wiki/general-information/gamoshi-open-rtb-specification.md)
* [Gamoshi bid request & bid response examples](/gamoshi-wiki/general-information/gamoshi-bid-request-and-bid-response-examples.md)
* [Mapping rules](/gamoshi-wiki/general-information/mapping-rules.md)
* [Advertiser & Campaign Filters](/gamoshi-wiki/general-information/advertiser-and-campaign-filters.md)