Order Object
The Online Ordering API stores the information for each online order within a unique order object. Users generate an order object with the Create Order operation, and can then modify the order with other operations that add or remove information from the order object. See below for an example order object and a description of the fields it can contain:
{
"order": {
"contributors": [
{
"time": "20YY-03-14T16:57:41.714Z",
"terminal": {
"terminal_number": "9",
"id": "9"
}
}
],
"creator": {
"time": "20YY-03-14T16:57:41.714Z",
"terminal": {
"terminal_number": "9",
"id": "9"
}
},
"origin": "mobile",
"order_source": "mobile",
"_id": "9999999999999999",
"business_date": "20YY-03-14T00:00:00.000Z",
"company_id": "9999999999999999",
"notification_status": "open",
"order_number": "9999999999999999",
"order_type": "order",
"order_status": {
"status": "pending"
},
"payment_status": "open",
"payment_info": {
"change": 0,
"payments": [],
"tips": 0,
"total": 0,
"change_info": [],
"hash_code": "9999999999999999"
},
"sequential_order_number": "2",
"segments": [],
"site_info": {
"id": "9999999999999999",
"timezone": "America/Los_Angeles",
"store_number": "9999",
"name": "99999",
"apps": [
{
"app_code": "XPOS",
"preferred_version": {
"version": "3.6.X",
"uri": "https://s3.amazonaws.com/com.xenial.shell/99/",
},
"installed_version": {
"version": "3.6.X",
"uri": "https://s3.amazonaws.com/com.xenial.shell/99/",
}
}
]
},
"state": "open",
"time": {
"created": "20YY-03-14T16:57:41.714Z",
"last_modified": "20YY-03-14T16:57:41.720Z",
"first_item_added": "20YY-03-14T16:57:41.717Z"
},
"version": "99",
"guest_count": 1,
"destination": {
"id": "carry-out",
"name": "Carry Out",
"consumption_type": "OffPremises"
},
"customer": {
"id": "9999999999999999",
"first_name": "test",
"last_name": "test",
"phone_cell": "9999999999999999",
"loyalty_customer": false,
"vehicle_type": "Van",
"vehicle_color": "White",
"vehicle_comment": "Nice whip"
},
"additional_properties": {},
"items": [
{
"product_id": "9999999999999999",
"order_item_id": "9999999999999999",
"quantity": 1,
"unit_price_source": "xenial",
"entity_id": "9999999999999999",
"item_type": "standard",
"reporting_category": {
"minor_reporting_category_entity_id": "9999999999999999",
"major_reporting_category_entity_id": "9999999999999999",
"9999999999999999": {
"_id": "9999999999999999",
"name": "Drinks",
"is_major": true,
"minor_reporting_category_entity_ids": [
"9999999999999999",
"9999999999999999",
"9999999999999999",
],
"entity_id": "9999999999999999",
"external_category_id": "",
"transaction_id": "9999999999999999"
},
"9999999999999999": {
"_id": "9999999999999999",
"name": "Americano",
"is_major": false,
"major_reporting_category_entity_id": "9999999999999999",
"entity_id": "9999999999999999"
}
},
"name": "Medium Hot Americano",
"tags": [
"9999999999999999",
"9999999999999999",
"9999999999999999",
],
"tax_group": {
"entity_id": "9999999999999999"
},
"kitchen_routing_categories": [],
"tax_inclusive": false,
"unit_price": 3.25,
"roll_up_price": "do_not_roll_up",
"time": {
"added": "20YY-03-14T16:57:41.717Z",
"last_modified": "20YY-03-14T16:57:41.720Z"
},
"state": "pending",
"payment_status": "open",
"child_items": [],
"hash_code": "9999999999999999",
"rollup_after_tax_amount": 0,
"9999999999999999": 0,
"taxable_price": 3.25,
"price": 3.25,
"tax_info": {
"taxes": [
{
"tax_definition_id": "9999999999999999",
"name": "Sales Tax 8.2%",
"tax_inclusive": true,
"amount_unrounded": 0.2463,
"amount": 0.25,
"marketplace_liable": false
}
],
"total_marketplace_liable_unrounded": 0,
"9999999999999999": 0,
"total_inclusive_unrounded": 0.2463,
"total_inclusive": 0.25,
"total_exclusive_unrounded": 0,
"total_exclusive": 0,
"total_unrounded": 0.2463,
"total": 0.25
},
"tax_inclusive_price": 3.25
}
],
"subtotal": 3.25,
"tax_inclusive_subtotal": 3.25,
"discount_info": {
"discounts": [],
"total": 0,
"total_unrounded": 0,
"discount_map": []
},
"discount_total": 0,
"tax_info": {
"taxes": [
{
"tax_definition_id": "9999999999999999",
"name": "Sales Tax 8.2%",
"tax_inclusive": true,
"amount_unrounded": 0.2463,
"amount": 0.25,
"marketplace_liable": false
}
],
"total_marketplace_liable_unrounded": 0,
"9999999999999999": 0,
"total_inclusive_unrounded": 0.2463,
"total_inclusive": 0.25,
"total_exclusive_unrounded": 0,
"total_exclusive": 0,
"total_unrounded": 0.2463,
"total": 0.25
},
"total": 3.25
},
"extended_info": {}
}The order object can contain the following fields, divided by category or code object:
CompanyInfo fields - Our Portal provides this basic company information.
Contributor fields - This information designates the origin of the order.
Customer fields - These fields comprise all customer-related information, which is either provided by the customers in-store or on third-party client user interfaces (UI) or delivery service applications.
DayPartInfo fields - These fields describe the Day Part during which the order was sent.
DefaultProducts fields - This section of the Order Object lists all default products included in the order.
Destination fields - This information describes the Order Destination, which is the "point of issue" of the order. For example, Drive-thru, Dine-in, and To Go.
Discount fields - This information describes a specific discount that applies to the order.
DiscountInfo fields - This object contains information for all discounts applied to the order.
Employee fields - This object contains employee information, populated in-store.
FeeConfig fields - This information defines the configuration of a fee applied to the order.
FractionalQuantity fields - These fields define a factional modifier quantity.
ItemRule fields - This information defines item-specific rules. For example, availability per destination and default content.
KitchenTime fields - This object contains information regarding a kitchen event connected to the order.
OrderItem fields - This object contains information for an individual item within the order.
OrderItemReportingCategory fields - These fields describe the reporting categories of an order item.
OrderObject fields - These fields comprise the order object itself.
OrderSegment fields - Users can divide orders into segments, defined in these fields.
OrderSourceInfo fields - Order Source fields define the specific source where this order has been created.
Payment fields - These fields store information for an individual payment on an order.
PaymentInfo fields - These fields provide information for all payments on an order.
PrintRecord fields - These fields provide information for an individual print record.
ReasonCode fields - These fields provide context information for a refunded order.
RefundReference fields - These fields provide reference information for a refund.
ReportingCategory fields - These fields describe a reporting category.
SiteInfo fields - These fields contain details for an order site or location.
Tax fields - These fields provide information for an individual tax.
TaxExemptInfo fields - These fields provide information about tax exemptions.
TaxGroup fields - These fields describe a specific tax group.
TaxInclusiveInfo fields - These fields define the inclusive taxes applied to an order, item, or tax.
TaxInfo fields - These fields contain information for all taxes applied to an order, item, or tax.
TaxJurisdiction fields - These fields identify the jurisdiction that imposes a particular tax.
Terminal fields - These fields define the information for the terminal associated with a particular order or event.
TimeInfo fields - These fields record the time at which a particular event occurred.
Data Models
CompanyInfo
The Portal provides this basic company information.
Field Name | Type | Description |
|---|---|---|
| string | The company identifier stored in the Portal |
| string | The company name stored in the Portal |
Contributors
This information designates the origin of the order.
Field Name | Type | Description |
|---|---|---|
| An object containing the information of the employee who created or modified the order | |
| An object containing the information of the terminal at which the order was created or modified | |
| string | The time at which the order was created or modified in ISO8601 format |
| string | The override permission name of the action taken. Example: |
Customer
These fields comprise all customer-related information, which is either provided by the customers in-store or on third-party client user interfaces (UI) or delivery service applications. Users can update some of these fields after an order has already been committed to Online Ordering API.
Field Name | Type | Description |
|---|---|---|
| string | The first address line of the customer |
| string | The second address line of the customer |
| string | The city of the customer |
| string | The country of the customer |
| string | The date and time of the delivery |
| string | The email address of the customer |
| string | The customer's first name |
| string | The customer's last name |
| string | The customer identifier |
| string | The customer's cell phone number |
| string | The customer's home phone number |
| string | The customer's work phone number |
| string | The date and time of the pickup |
| string | The customer's state |
| string | The tent number |
| string | The customer's zip code |
DayPartInfo
These fields describe the Day Part during which the order was sent. Day parts are time periods during the day, each belonging to a particular day part type and assigned to a specific day of the week. Day parts allow users to track orders or restrict menus by time of day.
Field Name | Type | Description |
|---|---|---|
| string | The unique identifier (UID) of the Day Part Type. This field matches the |
| string | The name of the Day Part Type. For example, Morning, Afternoon, or Evening. |
| string | The external identifier used to reference the Day Part Type |
DefaultProducts
This section of the Order Object lists all default products included in the order.
Field Name | Type | Description |
|---|---|---|
| numeric | The default quantity of the product |
| string | The default product identifier |
Destination
This information describes the Order Destination, which is the "point of issue" of the order. For example, Drive-thru, Dine-in, or To Go. The Order Destination can alter what menu content is available and what pricing rules apply to the order.
Field Name | Type | Description |
|---|---|---|
| string | The destination identifier |
| string | Describes whether the order is for "eat-in" or "drive thru" |
| string | The destination's name |
| string[] | The destination's tags |
Discount
This information describes a specific discount that applies to the order. Our system offers many type of discount configurations, including order-level and item-level discounts, manual and automatic, percentage and fixed amount, and quantity-based.
Field Name | Type | Description |
|---|---|---|
| numeric | The amount of discount applied rounded to a number of decimal digits based on the currency setting |
| numeric | The amount of discount applied (to 5-digit decimal precision value) |
| string | How the discount is applied |
| boolean | True - The distributed discount amount. False/Null - The full discount amount. |
| string | The discount identifier |
| boolean | True - Ignore the discount amount in all calculations, such as order total, or discount recalculation. False - Include the discount amount in all calculations. |
| string | The unique identifier (UID) for this instance of the discount |
| numeric | The quantity of the discount applied |
DiscountInfo
This object contains information for all discounts applied to the order.
Field Name | Type | Description |
|---|---|---|
| array of Discount objects | A list of discounts applied to the item or order |
| numeric | The total discount amount applied to the item or order without rounding (5-digit decimal precision value) |
| numeric | The total discount amount rounded to a number of decimal digits based the currency setting |
Employee
This object contains employee information, populated in-store.
Field Name | Type | Description |
|---|---|---|
| string | The employee identifier |
| string | The employee's first and last name |
| string | The employee's job title. For example, cashier or manager. |
| string | The employee's corporate code |
FeeConfig
This information defines the configuration of a fee applied to the order.
Field Name | Type | Description |
|---|---|---|
| numeric | The amount of the fee. For percentage fees, this is the percentage to use when calculating the fee, written as a decimal number. For example, 0.20 for 20%. |
| string | How the "amount" value should be applied to the order. The valid values are as follows:
|
| boolean | When set to true, the fee is calculated on the subtotal, without discounts, before taxes are added. When false, the fee is calculated on the full total (subtotal + taxes - discounts). |
| string | Specifies what type of fee the object represents. The valid values are as follows:
|
| numeric | (Optional) Specifies the decimal precision for the fee calculation. The default value is two (2) decimal places of precision. |
FractionalQuantity
These fields define a factional modifier quantity.
Field Name | Type | Description |
|---|---|---|
| number | The numerator of the fractional quantity |
| number | The denominator of the fractional quantity |
ItemRule
This information defines item-specific rules. For example, availability per destination or default content.
Field Name | Type | Description |
|---|---|---|
| string | The Mongo Database identifier |
| array of strings | A list of destination identifiers |
| string | The component's type: group or item |
| array of DefaultProduct objects | A list of default products |
| numberic | The default quantity |
| string | The item rule identifier |
| boolean | A flag that indicates whether to enable or disable the value for the item rule |
| numeric | The maximum quantity |
| numeric | The minimum quantity |
| string | The component label of the item rule |
| string | Deprecated |
| array of strings | A list of identifiers for available product choices |
| numeric | The position in the tab order |
KitchenTime
This object contains information regarding a kitchen event connected to the order.
Field Name | Type | Description |
|---|---|---|
| string | The kitchen screen name where the event occurred |
| string | The screen entity identifier for the kitchen screen where the event occurred |
| string | The type of action performed by the kitchen. The valid values are as follows:
|
| string | The time when the kitchen event occurred in ISO-8601 format |
| boolean | For bump events only. A flag that indicates the bump type, either "auto" or "manual." |
OrderItem
This object contains information for an individual item within the order.
Field Name | Type | Description |
|---|---|---|
| string | The entity identifier of the bundle |
| array of item objects | An array of child items |
| string | The user comment |
| The item discount information | |
| string | The unique identifier (UID) relating to the product identifier |
| (Optional) Defines the configuration for a "fee" type order item | |
| string | (Optional) The fulfillment status of the item |
| FractionalQuantity | The fractional quantity of the item ordered |
| The fractional quantity of the item ordered before sharing | |
| string | The hash code order |
| string | The type of the item such as product, modifier. |
| string | A list of strings that tells us which kitchen printer an item should be sent to on "send to kitchen" |
| array of KitchenTime objects | A list of KitchenTime objects which hold timing information for kitchen events |
| string | Set to either "gift_card" or "gift_certificate" |
| string | The identifier of the base item, if the current item is a modifier |
| array of OrderItem objects | A list of OrderItem objects for all attached modifiers |
| string | The name of the item |
| string | The unique item instance identifier (differentiates between several instances of one product on the order such as taco1, taco2, taco3). The |
| string | The order reference identifier for the order that is used for sharing |
| string | The payment transaction status type such as paid, refunded |
| numeric | The price of the item |
| numeric | The price remainder of the division after sharing |
| boolean | (Optional) Defines whether to print the order item emphasized on receipts |
| string | The unique product identifier from the menu, uses the same value for multiple instances of one product |
| numeric | The quantity of the item ordered |
| The order item reason code | |
| string | The order item reference identifier that was used for sharing |
| string | (Optional) Defines the employee identifier who removed the order item or approved the removal operation |
| string | (Optional) Defines the employee name who removed the order item or approved the removal operation |
| string | (Optional) Defines the employee corporate code who removed the order item or approved the removal operation |
| The order item reporting category | |
| boolean | Involved in placeholder manipulation |
| array of strings | A reporting field. This should be set from product data. |
| array of ItemRule objects | Defines the rules for bundle components |
| numeric | The order segments are separations in the order such as seats or trays. This is the identifier for the segment associated with the item. |
| numeric | This value provides the ability to manually sort the items in an order |
| string | The state of the item such as open, saved, deleted, or voided |
| array of strings | An array of identifiers or names for the tags that item belongs to |
| The item tax group | |
| The item tax inclusive information | |
| The item tax information | |
| The item time information | |
| numeric | The unit price of the item ordered |
OrderItemReportingCategory
These fields describe the reporting categories of an order item.
Field Name | Type | Description |
|---|---|---|
| The major reporting category information | |
| The minor reporting category information |
OrderObject
These fields comprise the order object itself.
Field Name | Type | Description |
|---|---|---|
| string | The unique order object identifier |
| AdditionalPropertiesType Object | The object which allows additional key-value pairs to be stored on an order. This field is best used to store integrator specific key-value pairs for use with external systems, as shown in the example below: {
"_id": "order-object-id",
"additional_properties": {
"string_key": "string_value",
"some_tokens": {
"web_token": "token",
"secret_token": 99999
}
}
} |
| string | The current business date |
| string | The comment for the order |
| string | The unique identifier (UID) of the company |
| array of Contributors objects | A list of additional employees or terminals involved in this order |
| The creator of the order. Contains the terminal identifier and employee name. | |
| The customer details information | |
| array of OrderItem objects | The deleted items |
| The order destination. The available options are: dine-in, carry-out, drive thru, and delivery. | |
| Order level discount information | |
| numeric | The total of all order and item-level discounts |
| string | The drawer identifier |
| string | An easily spoken representation of the order number. Usually shown on customer receipts. |
| string | Optional. A fulfillment status of the order |
| array of OrderItem objects | The order items |
| array of KitchenTime objects | A list of KitchenTime objects which hold timing information for kitchen events. Currently, |
| string | The lifecycle of order from total, tender, and save |
| string | The order object status. The available options include open, committed, committed-ack, checkedin, checkedin-ack, voided, voided-ack, and bumped. |
| string | The unique number for a particular company and particular site |
| string | The name or other identifier of the specific device that created the order such as "kiosk1", "kiosk2", "register1". |
| string | The device that the order originated from. This value is set by the client ordering application and is specific to customer requirements. It is not used for system-level management of orders. Note
|
| The point that the order originated from | |
| string | The order type. The available options include Order, Refund, or Waste. |
| string | The system that the order or notification originated from. This is set to "mobile" for orders that originate from the cloud. For orders and notifications that originate from the store, this is set to the store number. Our system processes use this internally to manage synchronization of orders and notifications between the cloud and the store. |
| The owner information | |
| The payment information | |
| string | The transaction type. The available options include open, paid, partial, post-adjusted, and refunded. |
| array of PrintRecord objects | A list of when this order receipt was printed and by whom |
| The reason code for a declined order | |
| string | The identifier of the original order in the refunded order |
| array of RefundReference objects | The refunds information. A separate object is created for each refunded item with the reference to the refunded order. |
| array of OrderSegment objects | The segments information |
| string | The unformatted order number. For example, 1004. |
| The site details such as name, phone, address, website, and email | |
| string | The order object state. The available options include open, saved, deleted, voided, overringed, parked, split, suspended, voided-post-payment, committed, checkedin, bumped, and purged. |
| numeric | The subtotal of the order |
| The tax exempt information | |
| The tax inclusive information | |
| The order level tax information | |
| The order dates and times in ISO8601 format | |
| numeric | The total of the order |
| string | The order object version |
| array of OrderItem objects | The voided items information |
OrderSegment
Users can divide orders into segments, defined in these fields. Data Management provides settings for configuring segment names.
Field Name | Type | Description |
|---|---|---|
| string | The name of the segment (Tray1, Tray2 or Seat1, Seat2). This name depends on how it was created as Tray or Seat, which is set on Data Management. |
| numeric | The number of the corresponding segment that is included in the OrderItem to determine which segment the item belongs to |
OrderSourceInfo
The Order Source fields define the specific source where this order has been created. For example, "Delivery." Order sources differ from the Origin field, which is system definable, as opposed to Order Sources which are defined by integrators. For an example of usage of the two entities, "Origin: In store" could be applicable for several order sources like "drive thru" or "dine in." Order Source is heavily used in the our ecosystem to filter/restrict certain items, menus, prices, and time periods for different ordering platforms.
Field Name | Type | Description |
|---|---|---|
| string | The given name of the order source. For example, web or Terminal 47. |
| string | The unique identifier (UID) for a particular order source |
Payment Object
These fields store information for an individual payment on an order. Online orders can contain payment information already or they can be committed as an unpaid order, allowing point of sale (POS) system employees to populate payment information in-store. An order can also might be updated in-store if the order content changes.
Field Name | Type | Description |
|---|---|---|
| string | The account identifier |
| string | The Portico requirement added for certification |
| string | The authorization identifier. For Europay, Mastercard, and Visa (EMV) transactions, this is the application identifier (AID) field. |
| boolean | A flag that indicates whether to allow tips. The POS system does not use this field. |
| numeric | The payment amount rounded to currency decimal precision |
| string | The name of card processing application such as MasterCardCredit and AMEX. For EMV transactions, this is the APL field. |
| string | The EMV Authorization Response Code (ARC) field. |
| string | The cryptogram field |
| string | The authentication code |
| numeric | The balance on the card |
| string | The type of acquisition such as MANUAL, SWIPE, CONTACTLESS, SCANNER, CHIP, and CHIP_FALL_BACK_SWIPE. For EMV transactions, this is the CEM field. |
| string | Card company brand such as Visa, Mastercard, or American Express. |
| string | The payment code. Options include CASH, DEBIT, CREDIT, or GIFT. |
| string | The Suppress Signature line. |
| boolean | The EMV format for Portico |
| string | The customized gift card name |
| string | The unique payment identifier |
| string | The EMV AID field |
| string | An identifier relating to a Store and Forward (SAF) action. It is used to query a payment device to update the status of a transaction after a SAF action. This has been available since OrderObject version 4. |
| boolean | POS does not use this field |
| string | The identifier value relating to pay type enums |
| string | The display name of the pay type used for the payment. It was added in OrderObject version 6. |
| numeric | The number of points left in a customer's house account. For example, a customer could have 30 points left for rewards after the order transaction. |
| string | The transaction processing time in Coordinated Universal Time (UTC) format |
| string | The card name |
| string | The Portico requirement added for certification |
| string | The request identifier by transaction |
| boolean | Any value of this field triggers a print signature line. For more information, see |
| string | The payment status |
| string | A cryptogram field |
| string | The terminal where payment was processed |
| string | The EMV terminal verification results (TVR) field |
| number | The sum total of tips |
| string | The transaction identifier in the batch |
| string | The transaction identifier |
| string | The EMV transaction status indicator (TSI) field |
| string | The available transactions types. For example, SALE or REFUND. |
| string | For EMV transactions, this is the Cardholder Verification Method (CVM) field. |
PaymentInfo
These fields provide information for all payments on an order.
Field Name | Type | Description |
|---|---|---|
| numeric | Only present if a change is due |
| array of Payment objects | A list of payments used to pay the order |
| number | The total of all tips from all payments |
| numeric | The total payment amount rounded to "n" decimal digits based on currency setting |
PrintRecord
These fields provide information for an individual print record.
Field Name | Type | Description |
|---|---|---|
| string | The first and last name of the person who printed the record |
| string | The employee identifier of the person who printed the record |
| string | The time the record was printed in ISO8601 format |
ReasonCode
These fields provide context information for a refunded order.
Field Name | Data Type | Description |
|---|---|---|
| string | The reason code identifier |
| string | One of the following actions:
|
| string | The name of the reason |
| The employee information | |
| string | The entity identifier of the reason code |
| boolean | This field is responsible for showing the prompt reason pop-up |
| The time information |
RefundReference
These fields provide reference information for a refund.
Field Name | Type | Description |
|---|---|---|
| string | The refunded order item identifier |
| number | The refunded item quantity |
| string | The refunded order identifier (reference to created refund order) |
ReportingCategory
These fields describe a reporting category.
Field Name | Type | Description |
|---|---|---|
| string | The reporting category name |
| string | The entity identifier of the reporting category |
SiteInfo
These fields contain details for an order site or location. Typically, Online Ordering orders only populate the bare minimum of site_info in order to identify to which site the order should be sent.
Field Name | Type | Description |
|---|---|---|
| string | The first address line for the site |
| string | The second address line for the site |
| string | The site city |
| The site company information | |
| string | The site email address |
| string | The site identifier |
| string | The site name |
| string | The site phone number |
| string | The United States (US) state or country province string |
| string | The store number defined by the company |
| string | The website for the site |
| string | The site zip code |
Tax
These fields provide information for an individual tax.
Field Name | Type | Description |
|---|---|---|
| string | The tax identifier |
| string | The name of the tax |
| numeric | The amount of the tax applied to the order, item, or tax (5-digit decimal precision value) |
| numeric | The amount of the tax applied to the order, item, or tax rounded to "n" decimal digits based on currency setting |
| The tax applied to the tax (tax on tax) | |
| boolean | A flag that determines if the discount is visible |
| string | Specifies the class of the tax |
| Display the jurisdiction which imposes this tax |
TaxExemptInfo
These fields provide information about tax exemptions.
Field Name | Type | Description |
|---|---|---|
| string | The tax exemption identifier |
| string | The reason text for the tax exemption |
| array of Tax objects | A list of taxes exempted |
| numeric | The total tax exempted rounded to "n" digits based on the currency setting |
TaxGroup
These fields describe a specific tax group.
Field Name | Type | Description |
|---|---|---|
| string | The entity identifier of the tax group |
| string | The tax code / tax group identifier |
| string | The name of the tax group |
TaxInclusiveInfo
These fields define the inclusive taxes applied to an order, item, or tax.
Field Name | Type | Description |
|---|---|---|
| array of Tax objects | A list of taxes applied to the item, order, or tax |
| numeric | A rounded total of inclusive taxes (configured decimal precision) |
| numeric | An unrounded total of inclusive taxes (fixed five (5) decimal places of precision) |
TaxInfo
These fields contain information for all taxes applied to an order, item, or tax.
Field Name | Type | Description |
|---|---|---|
| array of Tax objects | A list of taxes applied to the item, order, or tax |
| array of Tax objects | A list of inclusive taxes applied to the item, order, or tax |
| numeric | The total tax amount applied to the item, order, or tax (5-digit decimal precision) |
| numeric | The total tax applied to the item, order, or tax rounded to "n" digits based on the currency setting |
| numeric | The total inclusive taxes (five (5) decimal points) |
| numeric | The total inclusive taxes rounded to configured decimal points |
TaxJurisdiction
These fields identify the jurisdiction that imposes a particular tax.
Field Name | Type | Description |
|---|---|---|
| string | The jurisdiction identifier |
| string | The jurisdiction name |
| string | The level of the jurisdiction |
| string | The unique external identifier of the jurisdiction object to which the tax is associated |
Terminal
These fields define the information for the terminal associated with a particular order or event.
Field Name | Type | Description |
|---|---|---|
| string | The terminal identifier (previously knows as register ID) |
| string | The terminal number |
| string | The terminal title, such as front counter or drive thru |
TimeInfo
These fields record the time at which a particular event occurred.
Field Name | Type | Description |
|---|---|---|
| string | The time for last addition of an item or reason to the collection |
| string | The created date-time in the ISO8601 format |
| string | The time that the customer of a mobile order has checked in at the restaurant or that the order was sent to kitchen to be prepared |
| string | The closed time for the item or reason |
| string | The first saved (totaled, sent to kitchen) time for order |
| string | The time that an item of any type was first added to order |
| string | The time when the first item from some other order was added during a split operation |
| string | The sent date-time to kitchen in the ISO8601 format |
| string | The time that the order was completed by the kitchen (bumped) |
| string | The last modified date-time in the ISO8601 format |