Draft Order Sort Keys
The set of valid sort keys for the DraftOrder query.
Anchor to Valid valuesValid values
- CUSTOMER_NAME
- ID
- NUMBER
- RELEVANCE
- STATUS
- TOTAL_PRICE
- UPDATED_AT
- Anchor to CUSTOMER_NAMECUSTOMER_
NAME Sort by the
value.Sort by the
idvalue.- Anchor to NUMBERNUMBER
Sort by the
numbervalue.- 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 STATUSSTATUS
Sort by the
statusvalue.- Anchor to TOTAL_PRICETOTAL_
PRICE Sort by the
value.- Anchor to UPDATED_ATUPDATED_
AT Sort by the
value.
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.- Anchor to CustomerMergePreviewDefaultFields.draftOrders(sortKey)Customer•ARGUMENT
Merge Preview Default Fields.draftOrders(sortKey) The fields that will be kept as part of a customer merge preview.
- •ARGUMENT
The schema's entry-point for queries. This acts as the public, top-level API from which all queries must start.