The structure of your Ordering End-to-End data feed is defined by the relational inventory schema. The Ordering End-to-End data feed consists of the following top-level entities:
Restaurantentities: Which restaurants you service.
Serviceentities: Timing, location, and conditions of your service.
Menuentities: Details of each restaurant's menu.
The following diagram shows how
represent a single restaurant:
Restaurants per file: Each data file should represent one restaurant with its related
Menuentities. Use filenames that can help you search a file for a restaurant.
Data file format: Data files need to be formatted in newline-separated JSON files (ndjson format).
DateTime and Time values: For properties that require a
Timevalue, use the formats specified in DateTime and Time formats. For example,
IDs: Use an
@idproperty to identify all unique entities within an entity type. The maximum length is 300 characters. An
@idis a unique identifier of the entity of that type, but across entities, IDs can overlap. For example, assume you define a
Serviceentity with the
@idproperty set to
a16. You cannot create another
Serviceentity with an
a16. However, you can use
@idvalue of a
ID Generation: Keep your ids stable - do not use UUIDs or otherwise change/randomize ids between feed uploads. This allows easier support for entity-related issues.
Null values: Do not use the value
nullin place of objects. If an object is optional, you must omit it from your feed.
The client code generator in the Tools section is available to validate your Ordering End-to-End data feed.