Skip to main content
enum

The set of valid sort keys for the DraftOrder query.

Sort by the customer_name value.

Sort by the id value.

Sort by the number value.

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.

Sort by the status value.

Sort by the total_price value.

Sort by the updated_at value.


Was this section helpful?

•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. CompanyLocation objects can have custom pricing through Catalog and PriceList configurations.

•ARGUMENT

A person who acts on behalf of a Company to make B2B purchases. Company contacts are associated with Customer accounts and can place orders on behalf of their company.

Each contact can be assigned to one or more CompanyLocation 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 Company that'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 Catalog objects that determine which products are published and their pricing. The BuyerExperienceConfiguration determines checkout behavior including PaymentTerms, and whether orders require merchant review. B2B customers select which location they're purchasing for, which determines the applicable catalogs, pricing, TaxExemption values, and checkout settings for their Order objects.

•ARGUMENT

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.


Was this section helpful?