Skip to main content
enum

The set of valid sort keys for the Order query.

Sorts by the date and time the order was created.

Sorts by the current total price of an order in the shop currency, including any returns/refunds/removals.

Sorts by the customer's name.

Sort by shipping address to analyze regional sales patterns or plan logistics.

Sorts by the financial status of the order.

Sorts by the order's fulfillment status.

Sort by the id value.

Sorts by the order number.

Sort by the purchase order number to match external procurement systems or track recent orders.

Sorts by the date and time the order was processed.

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.

Sorts by the total sold price of an order in the shop currency, excluding any returns/refunds/removals.

Sorts by the date and time the order was last updated.


Was this section helpful?

•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.


Was this section helpful?