Glossary
| TERM | DEFINITION |
|---|---|
| Application | Your registered client of the PAR Ordering API. Its application key goes in the Application header on every request. An application exists per environment, so you may have more than one if you are deployed in several regions. |
| Singular Point | Singular Points are physical or virtual destinations that orders are placed to. Singular Points exist within an Area - depending on the Area Type, the Area may have only one Singular Point (as is the case for Dine-in (QS) and Takeout) or multiple (such as for Dine-in (FS) - where every table is a Singular Point). |
| Order Type | How the order is handed to the customer: Dine-in (FS), Dine-in (QS), Takeout, Delivery, Curbside, Drive-thru, Catering Pickup or Catering Delivery. See Order Types. |
| Venue | The API's name for a store — a single restaurant location. The guides say "store"; the API says venue. See the Store Finder guides. |
| Area | An Area is a virtual or physical destination to which orders are placed. Physical areas (such as for Dine-in or Delivery) can include configured tables, or defined geographical delivery zones with settings, defining specifically where the order should be delivered to. For virtual areas (such as for Takeout) orders can be placed directly on the area without requiring additional location information. |
| Serving Times | Defines for days of the week or special date / date ranges when the resource will be available. Used as opening hours for Venues, as availability hours for Products, and more. See Serving Times reference for more information. |
| Menu | The tree a store's offering is organized in: Menu → Category → Product → Product Group → Product. See Menu v2 Concept. |
| Product | Anything a customer can order or add to an item — a main item, a modifier, a combo. The same entity type plays every one of those roles depending on where it sits in the menu. See Menu v2 Concept. |
