# Product & Inventory Feed

## Merged Product & Inventory Feed Response From Nebim v3

Below is an example of a Product using JSON format:

{
    "id": "string (a unique product id fixed for lifetime)",
    "brand_name": "string",
    "title": "string",
    "description": "string",
    "content_language": "string",
    "target_country": "string",
    "currency": "string",
    "price": "string",
    "link": "string",
    "image_link": "string",
    "condition": "enum (new, used, refurbished)",
    "gtin": "string -> GTIN-12, GTIN-13 or GTIN-14 barcode (UPC, 12-digit converted UPC-E code, EAN, JAN, ISBN, ITF-14)",
    "mpn": "string",
    "gender": "enum (male, female, unisex)",
    "color": "string",
    "size": "string",
    "pattern": "string",
    "material": "string",
    "age_group": "enum (newborn, infant, toddler, kids, adult)"
}

Below is an example of an Inventory using JSON format:

{
    "store": "string (a unique code/id that is used primarily for matching a location in GBP (formerly GMB))",
    "quantity": "number",
    "availability": "enum (in stock, out of stock, limited availability, on display to order, preorder)"
}

What we expect is the combination of product feed & inventory feed **merged**, as shown below. We want the feed merged, in form of product+inventory.

Assume **X** is a *Product*, **Y** and **Z** are *Location*s. The response should contain X to be appeared twice for both Y location’s stock quantity and Z location’s stock quantity. There should be two entries with combination of X+Y (inventory information for Product X on Location Y) and of X+Z (inventory information for Product X on Location Y):

[
    ... // rest of the feed
    {
        ... // details of Product X as in example above
        "store": "string", // unique code for Location Y     
        "quantity": "number",
        "availability": "enum"
    },
    {
        ... // details of Product X as in example above
        "store": "string", // unique code for Location Z     
        "quantity": "number",
        "availability": "enum"
    }
]

## Fields
| Field | Description | Is Mandatory? | Default |
| ---------------- | ------------------------------------------------------------------------------------------------- | ------------- | -------- |
| id | A unique product identifier | Y | |
| brand_name | Product's brand name | Y | |
| title | Product title | Y | |
| description | Product description | Y | |
| content_language | A valid ISO 639-1 language code | N | tr |
| target_country | Product target country, A valid CLDR territory code | N | tr_TR |
| currency | Product's price currency | N | TRY |
| price | Product's price in TRY | Y | |
| link | Product link on webpage | Y | |
| image_link | An accessible product image link | Y | |
| condition | Product's condition or current state | N | new |
| gtin | Product’s Global Trade Item Number (GTIN) (UPC, 12-digit converted UPC-E code, EAN, JAN, ISBN, ITF-14) | N | |
| mpn | Product's manufacturer part number | N | |
| gender | enum (male, female, unisex) | N | unisex |
| color | Product's color: red, brown, etc.. | N | |
| size | small, medium, S, XL, etc.. | N | |
| pattern | Product’s pattern or graphic print, stripped, solid, etc.. | N | |
| material | leather, platinum, cotton, etc.. | N | |
| age_group | enum (newborn, infant, toddler, kids, adult) | N | |
| store | a unique code/id that is used primarily for matching a location in GBP (formerly GMB) | Y | |
| quantity | stock quantity in that location | Y | |
| availability | stock availability in that location | N | in stock |

## Next Steps?
1. First of all, we need to know which mandatory fields you cannot provide. Please, send us feedback about the fields.
* We are aware of the case that `link` & `image_link` may not exist on your system (Nebim). We can fetch these details from online partner (e-commerce)
3. And then we're going to investigate how we get that unavailable data.
4. We might want to arrange meetings with you or another partner to find answers for these fields.