StorePolicies

Store policies including terms and conditions, privacy policy, shipping policy, and refund policy. This object type provides structured access to the key policy documents of the store.

Type Definition

type StorePolicies {
  termsAndConditions: Policy
  privacyPolicy: Policy
  shippingPolicy: Policy
  refundPolicy: Policy
}

Fields

Relationships

• Each field in StorePolicies references the Policy type, representing a specific store policy document.
• These relationships allow clients to retrieve detailed policy information such as titles, content, and URLs by querying the nested Policy objects.

Usage Examples

Basic Query

Fetch all available store policies:

{
  policies {
    termsAndConditions {
      title
      content
    }
    privacyPolicy {
      title
      content
    }
    shippingPolicy {
      title
      content
    }
    refundPolicy {
      title
      content
    }
  }
}

Field Selection

Retrieve only the refund and shipping policies with their titles:

{
  policies {
    refundPolicy {
      title
    }
    shippingPolicy {
      title
    }
  }
}

Nested Queries

Access nested fields within the Policy objects, such as the policy content and URL for the terms and conditions:

{
  policies {
    termsAndConditions {
      title
      content
      url
    }
  }
}

Filtering and Sorting

The StorePolicies type itself does not support filtering or sorting, as it represents a singleton set of policies for the store. Filtering and sorting are not applicable here.

Implements

StorePolicies does not implement any interfaces.

Connections

There are no connection fields on StorePolicies as it is a container for policy objects rather than a paginated list.

Related Types

• Policy: Represents an individual policy document with fields such as title, content, and url. Each field in StorePolicies references a Policy object.

Best Practices

• Always check for null on each policy field, as some policies may not be defined for all stores.
• When displaying policy content to end users, consider caching the results to reduce repeated API calls, since policies rarely change frequently.
• Use the url field of the Policy object to link users directly to the full policy page when available.
• Avoid requesting all policy fields if only a subset is needed to minimize response size and improve performance.

Notes

• The API currently requires no authentication to query StorePolicies, but this may change in future versions.
• Since policies are typically static content, responses can be safely cached on the client or CDN to improve performance.
• The StorePolicies object provides a convenient way to access all major store policies in a single query, simplifying client implementations.
• No computed or derived fields are present on StorePolicies; all fields directly reference Policy objects.
• There are no field arguments on StorePolicies fields.