Skip to content
This repository was archived by the owner on Apr 23, 2021. It is now read-only.

Latest commit

 

History

History
39 lines (32 loc) · 6.72 KB

Order.md

File metadata and controls

39 lines (32 loc) · 6.72 KB

Order

Description

Contains all information related to a single order to process with Square, including line items that specify the products to purchase. Order objects also include information on any associated tenders, refunds, and returns. All Connect V2 Transactions have all been converted to Orders including all associated itemization data.

Properties

Name Type Description Notes
id String The order's unique ID. [optional]
locationId String The ID of the merchant location this order is associated with.
referenceId String A client specified identifier to associate an entity in another system with this order. [optional]
source OrderSource The origination details of the order. [optional]
customerId String The `Customer` ID of the customer associated with the order. [optional] [beta]
lineItems List<OrderLineItem> The line items included in the order. [optional]
taxes List<OrderLineItemTax> The list of all taxes associated with the order. Taxes can be scoped to either `ORDER` or `LINE_ITEM`. For taxes with `LINE_ITEM` scope, an `OrderLineItemAppliedTax` must be added to each line item that the tax applies to. For taxes with `ORDER` scope, the server will generate an `OrderLineItemAppliedTax` for every line item. On reads, each tax in the list will include the total amount of that tax applied to the order. IMPORTANT: If `LINE_ITEM` scope is set on any taxes in this field, usage of the deprecated `line_items.taxes` field will result in an error. Please use `line_items.applied_taxes` instead. [optional]
discounts List<OrderLineItemDiscount> The list of all discounts associated with the order. Discounts can be scoped to either `ORDER` or `LINE_ITEM`. For discounts scoped to `LINE_ITEM`, an `OrderLineItemAppliedDiscount` must be added to each line item that the discount applies to. For discounts with `ORDER` scope, the server will generate an `OrderLineItemAppliedDiscount` for every line item. IMPORTANT: If `LINE_ITEM` scope is set on any discounts in this field, usage of the deprecated `line_items.discounts` field will result in an error. Please use `line_items.applied_discounts` instead. [optional]
serviceCharges List<OrderServiceCharge> A list of service charges applied to the order. [optional]
fulfillments List<OrderFulfillment> Details on order fulfillment. Orders can only be created with at most one fulfillment. However, orders returned by the API may contain multiple fulfillments. [optional]
returns List<OrderReturn> Collection of items from sale Orders being returned in this one. Normally part of an Itemized Return or Exchange. There will be exactly one `Return` object per sale Order being referenced. [optional] [beta]
returnAmounts OrderMoneyAmounts Rollup of returned money amounts. [optional]
netAmounts OrderMoneyAmounts Net money amounts (sale money - return money). [optional]
roundingAdjustment OrderRoundingAdjustment A positive or negative rounding adjustment to the total of the order, commonly used to apply Cash Rounding when the minimum unit of account is smaller than the lowest physical denomination of currency. [optional]
tenders List<Tender> The Tenders which were used to pay for the Order. [optional] [beta]
refunds List<Refund> The Refunds that are part of this Order. [optional] [beta]
metadata Map<String, String> Application-defined data attached to this order. Metadata fields are intended to store descriptive references or associations with an entity in another system or store brief information about the object. Square does not process this field; it only stores and returns it in relevant API calls. Do not use metadata to store any sensitive information (personally identifiable information, card details, etc.). Keys written by applications must be 60 characters or less and must be in the character set `[a-zA-Z0-9_-]`. Entries may also include metadata generated by Square. These keys are prefixed with a namespace, separated from the key with a ':' character. Values have a max length of 255 characters. An application may have up to 10 entries per metadata field. Entries written by applications are private and can only be read or modified by the same application. See Metadata for more information. [optional] [beta]
createdAt String Timestamp for when the order was created. In RFC 3339 format, e.g., &quot;2016-09-04T23:59:33.123Z&quot;. [optional]
updatedAt String Timestamp for when the order was last updated. In RFC 3339 format, e.g., &quot;2016-09-04T23:59:33.123Z&quot;. [optional]
closedAt String Timestamp for when the order was closed. In RFC 3339 format, e.g., &quot;2016-09-04T23:59:33.123Z&quot;. [optional]
state String The current state of the order. `OPEN`,`COMPLETED`,`CANCELED` See OrderState for possible values [optional]
version Integer Version number which is incremented each time an update is committed to the order. Orders that were not created through the API will not include a version and thus cannot be updated. Read more about working with versions. [optional] [beta]
totalMoney Money The total amount of money to collect for the order. [optional]
totalTaxMoney Money The total tax amount of money to collect for the order. [optional]
totalDiscountMoney Money The total discount amount of money to collect for the order. [optional]
totalServiceChargeMoney Money The total amount of money collected in service charges for the order. Note: `total_service_charge_money` is the sum of `applied_money` fields for each individual service charge. Therefore, `total_service_charge_money` will only include inclusive tax amounts, not additive tax amounts. [optional]