> For the complete documentation index, see [llms.txt](https://docs.horizon.ipaper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.horizon.ipaper.io/data/standard-briefing-data.md).

# Standard briefing data

This document provides a description of the columns in the standard briefing file and how they interact with the Google Merchant Feed.

#### Overview

The **briefing file** is a list of products used to generate digital leaflets in Horizon. Each row represents a product, and products can be grouped into offers.\
The briefing file works in combination with a [standard Google Merchant Feed](https://support.google.com/merchants/answer/7052112?hl=en\&utm_source=chatgpt.com), which supplies product attributes such as titles, descriptions, prices, and images.

> **Disclaimer:** This content may change. Before implementing changes (e.g., new mappings, column definitions, or custom attributes), coordinate with the iPaper team.

***

#### File Templates

* [📥 Download the example page briefing file (.XLSX)](https://docs.google.com/spreadsheets/d/1G0BZPwIR3BTK4AlLOdeitd9RC5lqKjW7/export?format=xlsx)

***

#### Quick Reference Table

| Column name           | Required?                    | Description                                                                                  | Example                          |
| --------------------- | ---------------------------- | -------------------------------------------------------------------------------------------- | -------------------------------- |
| `product_id`          | ✅ Yes                        | Unique identifier matching the `id` in the product feed.                                     | `SKU12345`                       |
| `offer_id`            | No. Defaults to `product_id` | Groups products into a single offer. If blank, `product_id` doubles as `offer_id`.           | `OFFER_001`                      |
| `priority`            | No. Defaults to B priority.  | Offer priority: `A` = High, `B` = Medium, `C` = Low.                                         | `B`                              |
| `page`                | No                           | Places the offer on a specific page. Only used with page-controlled import; see below.       | `4`                              |
| `section`             | No                           | Groups offers into sections (e.g., categories, themes) much like chapters in a book.         | `Essentials`                     |
| `header`              | No                           | Offer title. Defaults to product title from feed.                                            | `Premium Coffee`                 |
| `summary`             | No                           | Short description. Defaults to product description from feed.                                | `Freshly roasted Arabica beans.` |
| `splash`              | No                           | Promo text (e.g., discount, special deal).                                                   | `Save 20%`                       |
| `image_url`           | No                           | Custom offer image. Defaults to feed image(s).                                               | `https://example.com/offer.png`  |
| `sales_price`         | No                           | Override price. Defaults to feed price.                                                      | `199,-`                          |
| `sales_price_aside_1` | No                           | Text shown above price (e.g., quantity deal).                                                | `2 for 1`                        |
| `sales_price_aside_2` | No                           | Text shown below price (e.g., original price, weight).                                       | `Was 299,-`                      |
| `logos`               | No                           | Up to 3 comma-separated **full URLs** to logo/image assets (e.g., brand or eco-label logos). | `https://brand.com/logo.png`     |
| `offer_url`           | No                           | Product page, or special offer URL. Defaults to feed if available.                           | `https://shop.com/item/123`      |

***

#### Two ways to place offers on pages

**Automatic (default)** — Leave `page` empty. Horizon groups offers by `section`, orders them by `priority`, and fills pages using your page templates. This is the standard approach and needs no extra setup.

**Page-controlled** — Fill in `page` for every offer. You decide exactly which offers appear together on each page, giving complete control over the leaflet layout. Offers without a page number are placed after the numbered pages. For a multi-product offer, the page is read from its first row.

> **Note:** Page-controlled import requires iPaper to configure your automation. Each page is given a template based on how many offers you placed on it, so agree the offer counts you will use with the iPaper team before starting (e.g. 3-offer and 6-offer pages need two templates). If a page holds more offers than its template has room for, the extra offers are left unplaced.

***

#### Product columns (only without a feed)

These columns are only used in the cases where **no product feed is** added. They create the products directly from the briefing file.

| Column name           | Required? | Description                                      | Example                              |
| --------------------- | --------- | ------------------------------------------------ | ------------------------------------ |
| `product_title`       | No        | Product title.                                   | `Premium Coffee 1kg`                 |
| `product_description` | No        | Product description.                             | `Organic Ethiopian coffee beans.`    |
| `product_sale_price`  | No        | Product price.                                   | `199,-`                              |
| `product_image_urls`  | No        | Comma-separated **full URLs** to product images. | `https://cdn.example.com/coffee.png` |
| `product_url`         | No        | Product page URL.                                | `https://shop.com/item/123`          |

> **Note:** Without a feed, nothing in the leaflet updates automatically. Prices, images and text stay exactly as written in the briefing file until you import a new one. If you have a feed, leave these columns empty and let the feed supply the product data.

***

#### Column Details & Best Practices

* **`logos`** (Optional)\
  Supports up to **3 comma-separated full URLs** to external assets.
  * Only absolute URLs are supported (e.g., `https://cdn.example.com/logo.png`).
  * Relative paths, local file names, or inline base64 images are **not supported**.
  * Recommended format: transparent PNG at \~200×200px.
* **`section`** (Optional)\
  Used to define sections of offer groupings in leaflets.\
  Example use cases: ensure grouping of related offers.
* **`priority`** (Optional, highly recommended)\
  Controls visibility order in the leaflet.
  * Use `A` sparingly — otherwise “everything is important, so nothing is.”
  * Recommended ratio: a few A’s, some B’s, and a majority of C’s.
* **`summary`** (Optional)\
  Override long feed descriptions with concise text tailored to the leaflet.
  * Example: Feed description = *“A 1 kg pack of hand-roasted Ethiopian coffee beans, organic, with notes of citrus.”*
  * Summary = *“Organic Ethiopian coffee, 1kg.”*
* **`image_url`** (Optional)\
  Overrides feed images.
  * Recommended format: JPG/PNG.

***

#### Mapping Merchant Feed Attributes

| Feed Attribute                                | Briefing File Column           | Default Behavior                                      | Override Behavior             |
| --------------------------------------------- | ------------------------------ | ----------------------------------------------------- | ----------------------------- |
| **id**                                        | `product_id`                   | Links product to feed attributes.                     | Must match exactly.           |
| **title**                                     | `header`                       | Uses feed title.                                      | Overridden by `header`.       |
| **description**                               | `summary`                      | Uses feed description.                                | Overridden by `summary`.      |
| **price** / **sale\_price**                   | `sales_price`                  | Uses feed pricing.                                    | Overridden by `sales_price`.  |
| **image\_link** / **additional\_image\_link** | `image_url`                    | Uses feed images.                                     | Overridden by `image_url`.    |
| **link**                                      | `offer_url`                    | Uses feed URL.                                        | Overridden by `offer_url`.    |
| **energy\_efficiency\_class**                 |                                | Used for EU energy labeling of electrical appliances. | Populated directly from feed. |
| **min\_energy\_efficiency\_class**            |                                | Defines the lower bound of the energy label scale.    | Populated directly from feed. |
| **max\_energy\_efficiency\_class**            |                                | Defines the upper bound of the energy label scale.    | Populated directly from feed. |
| **custom\_label\_0–4**                        | Various (FX brand logos, etc.) | These can be mapped to briefing columns as needed.    | Define mapping with iPaper.   |

> **Note:** `sale_price_effective_date` is not supported. Update `sale_price` manually when necessary.

***

#### Example

Here’s how a **3-product offer** might look in the briefing file:

| product\_id | offer\_id | priority | page | section    | header         | summary                  | splash   | sales\_price | sales\_price\_aside\_1 | sales\_price\_aside\_2 | logos                                                                                     |
| ----------- | --------- | -------- | ---- | ---------- | -------------- | ------------------------ | -------- | ------------ | ---------------------- | ---------------------- | ----------------------------------------------------------------------------------------- |
| SKU001      | OFFER123  | A        | 1    | Front Page | Premium Coffee | Organic Ethiopian, 1kg   | Save 20% | 199,-        | 2 for 1                | Was 299,-              | <https://cdn.example.com/brand\\\\_logo.png>                                              |
| SKU002      | OFFER123  | A        | 1    | Front Page |                | Organic Colombian, 1kg   |          |              |                        |                        | <https://cdn.example.com/eco\\\\_label.png>                                               |
| SKU003      | OFFER123  | A        | 1    | Front Page |                | Organic Decaf Blend, 1kg |          |              |                        |                        | <https://cdn.example.com/brand\\\\_logo.png>, <https://cdn.example.com/eco\\\\_label.png> |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.horizon.ipaper.io/data/standard-briefing-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
