# Overview

This section specifies the feed files used to transmit your inventory data to
Ordering Redirect. The contents of your feeds defines which services you are
providing, what services are available, and when the services are available. The
structure of the inventory feeds are defined by the Google Maps Booking API. The
following feeds are mandatory for the Ordering Redirect integration:

- **[Merchants feed](https://developers.google.com/actions-center/verticals/ordering/redirect/reference/action-link-feeds/merchants-feed):** Contains data describing your merchants.

- **[Services feed](https://developers.google.com/actions-center/verticals/ordering/redirect/reference/action-link-feeds/services-feed):** Describes the services provided by your merchants.

> [!NOTE]
> **Note:** All feeds must be uploaded with processing_instruction `PROCESS_AS_COMPLETE`. `PROCESS_AS_INCREMENTAL` is deprecated and cannot be used.

Some fields in these feeds are required and some are optional. Any field marked
as optional can be left out of the feed when empty.

The feeds format is described using protocol buffer 3 syntax. You have the
option to upload the feeds file as a binary serialization of the protocol buffer
data in [pb3 format](https://developers.google.com/protocol-buffers/docs/proto3) or in a derived JSON format.
We recommend uploading the feeds in JSON format.

We recommend using [gzip to compress feeds](https://developers.google.com/actions-center/verticals/ordering/redirect/guides/tutorials/tutorial-compression)
prior to upload.

This guide is specific to the Ordering Redirect protocol buffers. For general
information on how to use the protocol buffers to generate a pb3 file,
[here is an example in Java](https://developers.google.com/protocol-buffers/docs/javatutorial).