LegacyInteroperability

A list of addresses associated with the customer.

The addresses associated with the customer.

The total amount that the customer has spent on orders in their lifetime.

Whether the merchant can delete the customer from their store.

A customer can be deleted from a store only if they haven't yet made an order. After a customer makes an order, they can't be deleted from a store.

A list of the customer's company contact profiles.

The date and time when the customer was added to the store.

Whether the customer has opted out of having their data sold.

The default address associated with the customer.

The customer's default email address.

The customer's default phone number.

The full name of the customer, based on the values for first_name and last_name. If the first_name and last_name are not available, then this falls back to the customer's email address, and if that is not available, the customer's phone number.

A list of events associated with the customer.

The customer's first name.

A globally-unique ID.

The image associated with the customer.

The customer's last name.

The customer's last order.

The ID of the corresponding resource in the REST Admin API.

The amount of time since the customer was first added to the store.

Example: 'about 12 years'.

The customer's locale.

Whether the customer can be merged with another customer.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

A unique identifier for the customer that's used with Multipass login.

A note about the customer.

The number of orders that the customer has made at the store in their lifetime.

A list of the customer's orders.

A list of the customer's payment methods.

Possible subscriber states of a customer defined by their subscription contracts.

The state of the customer's account with the shop.

Please note that this only meaningful when Classic Customer Accounts is active.

The statistics for a given customer.

Returns a list of store credit accounts that belong to the owner resource. A store credit account owner can hold multiple accounts each with a different currency.

A list of the customer's subscription contracts.

A comma separated list of tags that have been added to the customer.

Whether the customer is exempt from being charged taxes on their orders.

The list of tax exemptions applied to the customer.

The date and time when the customer was last updated.

Whether the customer has verified their email address. Defaults to true if the customer is created through the Shopify admin or API.

Whether or not to accept automatic discounts on the draft order during calculation. If false, only discount codes and custom draft order discounts (see appliedDiscount) will be applied. If true, eligible automatic discounts will be applied in addition to discount codes and custom draft order discounts.

Whether discount codes are allowed during checkout of this draft order.

Whether all variant prices have been overridden.

Whether any variant prices have been overridden.

The custom order-level discount applied.

The billing address of the customer.

Whether the billing address matches the shipping address.

The date and time when the draft order was converted to a new order, and had it's status changed to Completed.

The date and time when the draft order was created in Shopify.

The shop currency used for calculation.

The custom information added to the draft order on behalf of the customer.

The customer who will be sent an invoice.

A default cursor that returns the single next record, sorted ascending by ID.

All discount codes applied.

The email address of the customer, which is used to send notifications.

The list of events associated with the draft order.

Whether the merchant has added timeline comments to the draft order.

A globally-unique ID.

The subject defined for the draft invoice email template.

The date and time when the invoice was last emailed to the customer.

The link to the checkout, which is sent to the customer in the invoice email.

The ID of the corresponding resource in the REST Admin API.

The list of the line items in the draft order.

A subtotal of the line items and corresponding discounts, excluding include shipping charges, shipping discounts, taxes, or order discounts.

List of localized fields for the resource.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The identifier for the draft order, which is unique within the store. For example, #D1223.

The text from an optional note attached to the draft order.

The order that was created from the draft order.

The associated payment terms for this draft order.

The assigned phone number.

The list of platform discounts applied.

The purchase order number.

The payment currency used for calculation.

The purchasing entity.

Whether the draft order is ready and can be completed. Draft orders might have asynchronous operations that can take time to finish.

The time after which inventory will automatically be restocked.

The shipping address of the customer.

The line item containing the shipping information and costs.

The status of the draft order.

The subtotal, of the line items and their discounts, excluding shipping charges, shipping discounts, and taxes.

The comma separated list of tags associated with the draft order. Updating tags overwrites any existing tags that were previously added to the draft order. To add new tags without overwriting existing tags, use the tagsAdd mutation.

Whether the line item prices include taxes.

Whether the draft order is tax exempt.

The list of of taxes lines charged for each line item and shipping line.

Total discounts.

Total price of line items.

The total price, includes taxes, shipping charges, and discounts.

The sum of individual line item quantities. If the draft order has bundle items, this is the sum containing the quantities of individual items in the bundle.

The total shipping price.

The total tax.

The total weight in grams of the draft order.

Fingerprint of the current cart. In order to have bundles work, the fingerprint must be passed to each request as it was previously returned, unmodified.

The date and time when the draft order was last changed. The format is YYYY-MM-DD HH:mm:ss. For example, 2016-02-05 17:04:01.

Whether the draft order will be visible to the customer on the self-serve portal.

The list of warnings raised while calculating.

The date and time when the fulfillment was created.

The date that this fulfillment was delivered.

Human readable display status for this fulfillment.

The estimated date that this fulfillment will arrive.

The history of events associated with this fulfillment.

List of the fulfillment's line items.

A paginated list of fulfillment orders for the fulfillment.

A globally-unique ID.

The date and time when the fulfillment went into transit.

The ID of the corresponding resource in the REST Admin API.

The location that the fulfillment was processed at.

Human readable reference identifier for this fulfillment.

The order for which the fulfillment was created.

The address at which the fulfillment occurred. This field is intended for tax purposes, as a full address is required for tax providers to accurately calculate taxes. Typically this is the address of the warehouse or fulfillment center. To retrieve a fulfillment location's address, use the assignedLocation field on the FulfillmentOrder object instead.

Whether any of the line items in the fulfillment require shipping.

Fulfillment service associated with the fulfillment.

The status of the fulfillment.

Sum of all line item quantities for the fulfillment.

Tracking information associated with the fulfillment, such as the tracking company, tracking number, and tracking URL.

The date and time when the fulfillment was last modified.

The ISO 3166-1 alpha-2 country code of where the item originated from.

A list of country specific harmonized system codes.

The date and time when the inventory item was created.

The number of inventory items that share the same SKU with this item.

The harmonized system code of the item. This must be a number between 6 and 13 digits.

A globally-unique ID.

The URL that points to the inventory history for the item.

The inventory item's quantities at the specified location.

A list of the inventory item's quantities for each location that the inventory item can be stocked at.

The ID of the corresponding resource in the REST Admin API.

The number of locations where this inventory item is stocked.

The packaging dimensions of the inventory item.

The ISO 3166-2 alpha-2 province code of where the item originated from.

Whether the inventory item requires shipping.

Inventory item SKU. Case-sensitive string.

Whether inventory levels are tracked for the item.

Whether the value of the tracked field for the inventory item can be changed.

Unit cost associated with the inventory item. Note: the user must have "View product costs" permission granted in order to access this field once product granular permissions are enabled.

The date and time when the inventory item was updated.

The variant that owns this inventory item.

Whether the location can be reactivated. If false, then trying to activate the location with the LocationActivate mutation will return an error that describes why the location can't be activated.

The address of this location.

Whether the location address has been verified.

The date and time (ISO 8601 format) that the location was added to a shop.

Whether this location can be deactivated. If true, then the location can be deactivated by calling the LocationDeactivate mutation. If false, then calling the mutation to deactivate it will return an error that describes why the location can't be deactivated.

The date and time (ISO 8601 format) that the location was deactivated at. For example, 3:30 pm on September 7, 2019 in the time zone of UTC (Universal Time Coordinated) is represented as "2019-09-07T15:50:00Z".

Whether this location can be deleted.

Name of the service provider that fulfills from this location.

Whether this location can fulfill online orders.

Whether this location has active inventory.

Whether this location has orders that need to be fulfilled.

A globally-unique ID.

The quantities of an inventory item at this location.

A list of the quantities of the inventory items that can be stocked at this location.

Whether the location is active. A deactivated location can be activated (change isActive: true) if it has activatable set to true by calling the locationActivate mutation.

Whether this location is a fulfillment service.

The ID of the corresponding resource in the REST Admin API.

Local pickup settings for the location.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The name of the location.

Whether this location is used for calculating shipping rates. In multi-origin shipping mode, this flag is ignored.

List of suggested addresses for this location (empty if none).

The date and time (ISO 8601 format) when the location was last updated.

The app that the marketing event is attributed to.

The unique string identifier of the channel to which this activity belongs. For the correct handle for your channel, contact your partner manager.

A human-readable description of the marketing event.

The date and time when the marketing event ended.

A globally-unique ID.

The ID of the corresponding resource in the REST Admin API.

The URL where the marketing event can be managed.

The medium through which the marketing activity and event reached consumers. This is used for reporting aggregation.

The URL where the marketing event can be previewed.

An optional ID that helps Shopify validate engagement data.

The date and time when the marketing event is scheduled to end.

Where the MarketingEvent occurred and what kind of content was used. Because utmSource and utmMedium are often used interchangeably, this is based on a combination of marketingChannel, referringDomain, and type to provide a consistent representation for any given piece of marketing regardless of the app that created it.

The date and time when the marketing event started.

The marketing event type.

The name of the marketing campaign.

The medium that the marketing campaign is using. Example values: cpc, banner.

The referrer of the marketing event. Example values: google, newsletter.

The data stored in the resource, represented as a digest.

The date and time when the metafield was created.

The metafield definition that the metafield belongs to, if any.

A globally-unique ID.

The data stored in the metafield in JSON format.

The unique identifier for the metafield within its namespace.

The ID of the corresponding resource in the REST Admin API.

The container for a group of metafields that the metafield is associated with.

The resource that the metafield is attached to.

The type of resource that the metafield is attached to.

Returns a reference object if the metafield definition's type is a resource reference.

A list of reference objects if the metafield's type is a resource reference list.

The type of data that is stored in the metafield. Refer to the list of supported types.

The date and time when the metafield was updated.

The data stored in the metafield. Always stored as a string, regardless of the metafield's type.

A list of additional fees applied to an order, such as duties, import fees, or tax lines.

A list of sales agreements associated with the order, such as contracts defining payment terms, or delivery schedules between merchants and customers.

A list of messages that appear on the Orders page in the Shopify admin. These alerts provide merchants with important information about an order's status or required actions.

The application that created the order. For example, "Online Store", "Point of Sale", or a custom app name. Use this to identify the order source for attribution and fulfillment workflows. Learn more about building apps for orders and fulfillment.

The billing address associated with the payment method selected by the customer for an order. Returns null if no billing address was provided during checkout.

Whether the billing address matches the shipping address. Returns true if both addresses are the same, and false if they're different or if an address is missing.

Details of an order's cancellation, if it has been canceled. This includes the reason, date, and any staff notes.

The date and time in ISO 8601 format when an order was canceled. Returns null if the order hasn't been canceled.

The reason provided for an order cancellation. For example, a merchant might cancel an order if there's insufficient inventory. Returns null if the order hasn't been canceled.

Whether an order can be manually marked as paid. Returns false if the order is already paid, is canceled, has pending Shopify Payments transactions, or has a negative payment amount.

Whether order notifications can be sent to the customer. Returns true if the customer has a valid email address.

Whether an authorized payment for an order can be captured. Returns true if an authorized payment exists that hasn't been fully captured yet. Learn more about capturing payments.

The total discount amount applied at the time the order was created, displayed in both shop and presentment currencies, before returns, refunds, order edits, and cancellations. This field only includes discounts applied to the entire order.

Details about the sales channel that created the order, such as the channel app type and channel name, which helps to track order sources.

The IP address of the customer who placed the order. Useful for fraud detection and geographic analysis.

Whether an order is closed. An order is considered closed if all its line items have been fulfilled or canceled, and all financial transactions are complete.

The date and time ISO 8601 format when an order was closed. Shopify automatically records this timestamp when all items have been fulfilled or canceled, and all financial transactions are complete. Returns null if the order isn't closed.

A customer-facing order identifier, often shown instead of the sequential order name. It uses a random alphanumeric format (for example, XPAV284CT) and isn't guaranteed to be unique across orders.

Whether inventory has been reserved for an order. Returns true if inventory quantities for an order's line items have been reserved. Learn more about managing inventory quantities and states.

The date and time in ISO 8601 format when an order was created. This timestamp is set when the customer completes checkout and remains unchanged throughout an order's lifecycle.

The shop currency when the order was placed. For example, "USD" or "CAD".

The current total of all discounts applied to the entire order, after returns, refunds, order edits, and cancellations. This includes discount codes, automatic discounts, and other promotions that affect the whole order rather than individual line items. To get the original discount amount at the time of order creation, use the cartDiscountAmountSet field.

The current shipping price after applying refunds and discounts. If the parent order.taxesIncluded field is true, then this price includes taxes. Otherwise, this field is the pre-tax price.

The current sum of the quantities for all line items that contribute to the order's subtotal price, after returns, refunds, order edits, and cancellations.

The total price of the order, after returns and refunds, in shop and presentment currencies. This includes taxes and discounts.

A list of all tax lines applied to line items on the order, after returns. Tax line prices represent the total price for all tax lines with the same rate and title.

The current total of all additional fees for an order, after any returns or modifications. Modifications include returns, refunds, order edits, and cancellations. Additional fees can include charges such as duties, import fees, and special handling.

The total amount discounted on the order after returns and refunds, in shop and presentment currencies. This includes both order and line level discounts.

The current total duties amount for an order, after any returns or modifications. Modifications include returns, refunds, order edits, and cancellations.

The total price of the order, after returns, in shop and presentment currencies. This includes taxes and discounts.

The sum of the prices of all tax lines applied to line items on the order, after returns and refunds, in shop and presentment currencies.

The total weight of the order after returns and refunds, in grams.

A list of additional information that has been attached to the order. For example, gift message, delivery instructions, or internal notes.

The customer who placed an order. Returns null if an order was created through a checkout without customer authentication, such as a guest checkout. Learn more about customer accounts.

Whether the customer agreed to receive marketing emails at the time of purchase. Use this to ensure compliance with marketing consent laws and to segment customers for email campaigns. Learn more about building customer segments.

The customer's visits and interactions with the online store before placing the order. Use this to understand customer behavior, attribution sources, and marketing effectiveness to optimize your sales funnel.

The customer's language and region preference at the time of purchase. For example, "en" for English, "fr-CA" for French (Canada), or "es-MX" for Spanish (Mexico). Use this to provide localized customer service and targeted marketing in the customer's preferred language.

A list of discounts that are applied to the order, excluding order edits and refunds. Includes discount codes, automatic discounts, and other promotions that reduce the order total.

The discount code used for an order. Returns null if no discount code was applied.

The discount codes used for the order. Multiple codes can be applied to a single order.

The primary address of the customer, prioritizing shipping address over billing address when both are available. Returns null if neither shipping address nor billing address was provided.

An order's financial status for display in the Shopify admin.

The order's fulfillment status that displays in the Shopify admin to merchants. For example, an order might be unfulfilled or scheduled. For detailed processing, use the FulfillmentOrder object.

A list of payment disputes associated with the order, such as chargebacks or payment inquiries. Disputes occur when customers challenge transactions with their bank or payment provider.

Whether duties are included in the subtotal price of the order. Duties are import taxes charged by customs authorities when goods cross international borders.

Whether the order has had any edits applied. For example, adding or removing line items, updating quantities, or changing prices.

The email address associated with the customer for this order. Used for sending order confirmations, shipping notifications, and other order-related communications. Returns null if no email address was provided during checkout.

Whether taxes on the order are estimated. This field returns false when taxes on the order are finalized and aren't subject to any changes.

A list of events associated with the order. Events track significant changes and activities related to the order, such as creation, payment, fulfillment, and cancellation.

Whether there are line items that can be fulfilled. This field returns false when the order has no fulfillable line items. For a more granular view of the fulfillment status, refer to the FulfillmentOrder object.

A list of fulfillment orders for an order. Each fulfillment order groups line items that are fulfilled together, allowing an order to be processed in parts if needed.

A list of shipments for the order. Fulfillments represent the physical shipment of products to customers.

The total number of fulfillments for the order, including canceled ones.

Whether the order has been paid in full. This field returns true when the total amount received equals or exceeds the order total.

Whether the merchant has added a timeline comment to the order.

A globally-unique ID.

The ID of the corresponding resource in the REST Admin API.

A list of the order's line items. Line items represent the individual products and quantities that make up the order.

List of localized fields for the resource.

The legal business structure that the merchant operates under for this order, such as an LLC, corporation, or partnership. Used for tax reporting, legal compliance, and determining which business entity is responsible for the order.

Whether the order can be edited by the merchant. Returns false for orders that can't be modified, such as canceled orders or orders with specific payment statuses.

A list of reasons why the order can't be edited. For example, canceled orders can't be edited.

The application acting as the Merchant of Record for the order. The Merchant of Record is responsible for tax collection and remittance.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The unique identifier for the order that appears on the order page in the Shopify admin and the Order status page. For example, "#1001", "EN1001", or "1001-A". This value isn't unique across multiple stores. Use this field to identify orders in the Shopify admin and for order tracking.

The net payment for the order, based on the total amount received minus the total amount refunded, in shop and presentment currencies.

A list of line items that can't be fulfilled. For example, tips and fully refunded line items can't be fulfilled. For a more granular view of the fulfillment status, refer to the FulfillmentOrder object.

The note associated with the order. Contains additional information or instructions added by merchants or customers during the order process. Commonly used for special delivery instructions, gift messages, or internal processing notes.

The order number used to generate the name using the store's configured order number prefix/suffix. This number isn't guaranteed to follow a consecutive integer sequence (e.g. 1, 2, 3..), nor is it guaranteed to be unique across multiple stores, or even for a single store.

The total amount of all additional fees, such as import fees or taxes, that were applied when an order was created. Returns null if additional fees aren't applicable.

The total amount of duties calculated when an order was created, before any modifications. Modifications include returns, refunds, order edits, and cancellations. Use currentTotalDutiesSet to retrieve the current duties amount after adjustments.

The total price of the order at the time of order creation, in shop and presentment currencies. Use this to compare the original order value against the current total after edits, returns, or refunds.

The payment collection details for the order, including payment status, outstanding amounts, and collection information. Use this to understand when and how payments should be collected, especially for orders with deferred or installment payment terms.

A list of the names of all payment gateways used for the order. For example, "Shopify Payments" and "Cash on Delivery (COD)".

The payment terms associated with the order, such as net payment due dates or early payment discounts. Payment terms define when and how an order should be paid. Returns null if no specific payment terms were set for the order.

The phone number associated with the customer for this order. Useful for contacting customers about shipping updates, delivery notifications, or order issues. Returns null if no phone number was provided during checkout.

The purchase order (PO) number that's associated with an order. This is typically provided by business customers who require a PO number for their procurement.

The currency used by the customer when placing the order. For example, "USD", "EUR", or "CAD". This may differ from the shop's base currency when serving international customers or using multi-currency pricing.

The date and time in ISO 8601 format when the order was processed. This date and time might not match the date and time when the order was created.

The sales channel that the order was created from, such as the Online Store or Shopify POS.

The business entity that placed the order, including company details and purchasing relationships. Used for B2B transactions to track which company or organization is responsible for the purchase and payment terms.

Whether the order can be refunded based on its payment transactions. Returns false for orders with no eligible payment transactions, such as fully refunded orders or orders with non-refundable payment methods.

The difference between the suggested and actual refund amount of all refunds that have been applied to the order. A positive value indicates a difference in the merchant's favor, and a negative value indicates a difference in the customer's favor.

A list of refunds that have been applied to the order. Refunds represent money returned to customers for returned items, cancellations, or adjustments.

The URL of the source that the order originated from, if found in the domain registry. Returns null if the source URL isn't in the domain registry.

Whether the order requires physical shipping to the customer. Returns false for digital-only orders (such as gift cards or downloadable products) and true for orders with physical products that need delivery. Use this to determine shipping workflows and logistics requirements.

Whether any line items on the order can be restocked into inventory. Returns false for digital products, custom items, or items that can't be resold.

The physical location where a retail order is created or completed, except for draft POS orders completed using the "mark as paid" flow in the Shopify admin, which return null. Transactions associated with the order might have been processed at a different location.

The returns associated with the order. Contains information about items that customers have requested to return, including return reasons, status, and refund details. Use this to track and manage the return process for order items.

The order's aggregated return status for display purposes. Indicates the overall state of returns for the order, helping merchants track and manage the return process.

The risk assessment summary for the order. Provides fraud analysis and risk scoring to help you identify potentially fraudulent orders. Use this to make informed decisions about order fulfillment and payment processing.

The shipping address where the order will be delivered. Contains the customer's delivery location for fulfillment and shipping label generation. Returns null for digital orders or orders that don't require shipping.

A summary of all shipping costs on the order. Aggregates shipping charges, discounts, and taxes to provide a single view of delivery costs.

The shipping methods applied to the order. Each shipping line represents a shipping option chosen during checkout, including the carrier, service level, and cost. Use this to understand shipping charges and delivery options for the order.

The Shopify Protect details for the order, including fraud protection status and coverage information. Shopify Protect helps protect eligible orders against fraudulent chargebacks. Returns null if Shopify Protect is disabled for the shop or the order isn't eligible for protection. Learn more about Shopify Protect.

A unique POS or third party order identifier. For example, "1234-12-1000" or "111-98567-54". The receiptNumber field is derived from this value for POS orders.

The name of the source associated with the order, such as "web", "mobile_app", or "pos". Use this field to identify the platform where the order was placed.

The staff member who created or is responsible for the order. Useful for tracking which team member handled phone orders, manual orders, or order modifications. Returns null for orders created directly by customers through the online store.

The URL where customers can check their order's current status, including tracking information and delivery updates. Provides order tracking links in emails, apps, or customer communications.

The sum of quantities for all line items that contribute to the order's subtotal price. This excludes quantities for items like tips, shipping costs, or gift cards that don't affect the subtotal. Use this to quickly understand the total item count for pricing calculations.

The sum of the prices for all line items after discounts and before returns, in shop and presentment currencies. If taxesIncluded is true, then the subtotal also includes tax.

A calculated refund suggestion for the order based on specified line items, shipping, and duties. Use this to preview refund amounts, taxes, and processing fees before creating an actual refund.

A comma separated list of tags associated with the order. Updating tags overwrites any existing tags that were previously added to the order. To add new tags without overwriting existing tags, use the tagsAdd mutation.

Whether taxes are included in the subtotal price of the order. When true, the subtotal and line item prices include tax amounts. When false, taxes are calculated and displayed separately.

Whether taxes are exempt on the order. Returns true for orders where the customer or business has a valid tax exemption, such as non-profit organizations or tax-free purchases. Use this to understand if tax calculations were skipped during checkout.

A list of all tax lines applied to line items on the order, before returns. Tax line prices represent the total price for all tax lines with the same rate and title.

Whether the order is a test. Test orders are made using the Shopify Bogus Gateway or a payment provider with test mode enabled. A test order can't be converted into a real order and vice versa.

The authorized amount that's uncaptured or undercaptured, in shop and presentment currencies. This amount isn't adjusted for returns.

The total rounding adjustment applied to payments or refunds for an order involving cash payments. Applies to some countries where cash transactions are rounded to the nearest currency denomination.

The total amount discounted on the order before returns, in shop and presentment currencies. This includes both order and line level discounts.

The total amount not yet transacted for the order, in shop and presentment currencies. A positive value indicates a difference in the merchant's favor (payment from customer to merchant) and a negative value indicates a difference in the customer's favor (refund from merchant to customer).

The total price of the order, before returns, in shop and presentment currencies. This includes taxes and discounts.

The total amount received from the customer before returns, in shop and presentment currencies.

The total amount that was refunded, in shop and presentment currencies.

The total amount of shipping that was refunded, in shop and presentment currencies.

The total shipping costs returned to the customer, in shop and presentment currencies. This includes fees and any related discounts that were refunded.

The total tax amount before returns, in shop and presentment currencies.

The sum of all tip amounts for the order, in shop and presentment currencies.

The total weight of the order before returns, in grams.

A list of transactions associated with the order.

The number of transactions associated with the order.

Whether no payments have been made for the order.

The date and time in ISO 8601 format when the order was last modified.