Order Sort Keys
The set of valid sort keys for the Order query.
Anchor to Valid valuesValid values
- Anchor to CREATED_ATCREATED_
AT Sorts by the date and time the order was created.
- Anchor to CURRENT_TOTAL_PRICECURRENT_
TOTAL_ PRICE Sorts by the current total price of an order in the shop currency, including any returns/refunds/removals.
- Anchor to CUSTOMER_NAMECUSTOMER_
NAME Sorts by the customer's name.
- Anchor to DESTINATIONDESTINATION
Sort by shipping address to analyze regional sales patterns or plan logistics.
- Anchor to FINANCIAL_STATUSFINANCIAL_
STATUS Sorts by the financial status of the order.
- Anchor to FULFILLMENT_STATUSFULFILLMENT_
STATUS Sorts by the order's fulfillment status.
Sort by the
id
value.- Anchor to ORDER_NUMBERORDER_
NUMBER Sorts by the order number.
- Anchor to PO_NUMBERPO_
NUMBER Sort by the purchase order number to match external procurement systems or track recent orders.
- Anchor to PROCESSED_ATPROCESSED_
AT Sorts by the date and time the order was processed.
- Anchor to RELEVANCERELEVANCE
Sort by relevance to the search terms when the
query
parameter is specified on the connection. Don't use this sort key when no search query is specified.- Anchor to TOTAL_ITEMS_QUANTITYTOTAL_
ITEMS_ QUANTITY Sort by the total quantity of all line items to identify large purchases or analyze inventory demand patterns.
- Anchor to TOTAL_PRICETOTAL_
PRICE Sorts by the total sold price of an order in the shop currency, excluding any returns/refunds/removals.
- Anchor to UPDATED_ATUPDATED_
AT Sorts by the date and time the order was last updated.
Anchor to FieldsFields
- •ARGUMENT
Represents information about a company which is also a customer of the shop.
- •ARGUMENT
A person that acts on behalf of company associated to a customer.
- •ARGUMENT
A location or branch of a company that's a customer of the shop. Configuration of B2B relationship, for example prices lists and checkout settings, may be done for a location.
- •ARGUMENT
Represents information about a customer of the shop, such as the customer's contact details, their order history, and whether they've agreed to receive marketing material by email.
Caution: Only use this data if it's required for your app's functionality. Shopify will restrict access to scopes for apps that don't have a legitimate use for the associated data.
- •ARGUMENT
The fields that will be kept as part of a customer merge preview.
- •ARGUMENT
Represents a collection of general settings and information about the shop.
- •ARGUMENT
The schema's entry-point for queries. This acts as the public, top-level API from which all queries must start.