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
idvalue.- 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
queryparameter 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
A business entity that purchases from the shop as part of B2B commerce. Companies organize multiple locations and contacts who can place orders on behalf of the organization.
objects can have custom pricing throughCatalogandconfigurations.- •ARGUMENT
A person who acts on behalf of a
Companyto make B2B purchases. Company contacts are associated withCustomeraccounts and can place orders on behalf of their company.Each contact can be assigned to one or more
objects with specific roles that determine their permissions and access to catalogs, pricing, and payment terms configured for those locations.- •ARGUMENT
A location or branch of a
Companythat's a customer of the shop. Company locations enable B2B customers to manage multiple branches with distinct billing and shipping addresses, tax settings, and checkout configurations.Each location can have its own
Catalogobjects that determine which products are published and their pricing. Thedetermines checkout behavior including, and whether orders require merchant review. B2B customers select which location they're purchasing for, which determines the applicable catalogs, pricing,values, and checkout settings for theirOrderobjects.- •ARGUMENT
Information about a customer of the shop, such as the customer's contact details, purchase history, and marketing preferences.
Tracks the customer's total spending through the
field and provides access to associated data such as payment methods and subscription contracts.CautionOnly 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.
- Anchor to CustomerMergePreviewDefaultFields.orders(sortKey)Customer•ARGUMENT
Merge Preview Default Fields.orders(sortKey) The fields that will be kept as part of a customer merge preview.
- •ARGUMENT
The central configuration and settings hub for a Shopify store. Access business information, operational preferences, feature availability, and store-wide settings that control how the shop operates.
Includes core business details like the shop name, contact emails, billing address, and currency settings. The shop configuration determines customer account requirements, available sales channels, enabled features, payment settings, and policy documents. Also provides access to shop-level resources such as staff members, fulfillment services, navigation settings, and storefront access tokens.
- •ARGUMENT
The schema's entry-point for queries. This acts as the public, top-level API from which all queries must start.
- •ARGUMENT