Category-specific achievement criteria

Use bundles primitives

Your app must either use the Admin API to create static bundles or use a cartTransform function to create customized bundles.

However, if your app supports a bundles use case that is not yet supported through these APIs — such as selling bundles on unsupported sales channels, selling bundles as a part of a subscription, or editing orders to add or remove bundles after purchase — you may use other methods to create a bundle.

Use subscription primitives and APIs

Your app must use the following subscriptions primitives and APIs:

• Selling plan API to create and manage various ways to sell and buy products
• Subscription contract API to create, manage, and update subscription agreements between a customer and merchant in real time
• Customer payment method API to store payment methods that can be used to pay for future orders without requiring the customer to manually go through checkout

Use theme app block extensions

Your app must add subscriptions on product detail pages by using an App block for themes that is compatible with Online Store 2.0.

Follow subscriptions UX guidelines

Your app must obey the following subscriptions UX guidelines:

• The subscription information — including selling plan name, price, and savings — must be clearly displayed on the product, cart, and order detail pages.
• The subscription option information must automatically match the color palette, font, font-size, and font weight of the store's current theme by default.

Use discount primitives

Your app must either use discount functions to define custom discount types or use the native discount APIs to create discounts.

Do not use draft orders with custom discounts

Your app must not create draft orders to give custom discounts. Drafts with custom discounts are designed for one-off merchant-driven flows rather than automated customer-driven flows and do not have the same reporting tools.

Use a single redeem code per discount

Your app must use the discountRedeemCodeBulkAdd API to create any discounts with multiple redeem codes. Don't use the GraphQL Admin API to create multiple discounts with the same value but different redeem codes.

Create high quality links

All links to your app from the Create discount button on the discounts page must direct to a page in your embedded app where merchants can create the corresponding discount. These pages must follow all relevant App Design Guidelines.

Provide a flow trigger

Your app must provide a Flow trigger that starts a workflow whenever a new review is collected.

Use block extensions

Your app must provide an admin block extension on customer detail pages that allows merchants to see any reviews submitted by the customer.

Actively fulfill orders

Your app must be active and have fulfilled 100 or more fulfillment orders in the last 28 days. If an app is not active, then it's not possible to accurately assess the other criteria for fulfillment services apps.

Complete fulfillment orders

Your app must have completed 99% of the fulfillment orders assigned to it in the last 28 days. New fulfillment orders that were created in the last 7 days are excluded. A fulfillment order is considered incomplete if it is in one of the following states:

• open, submitted
• in_progress, accepted
• in_progress, cancellation_rejected
• in_progress, cancellation_requested

Respond to callback requests

In the last 28 days, your app must have responded successfully to 99% of Shopify callback requests that are sent to it, so merchants are not alerted to failing callback requests.

Wait for merchant requests

Your app must only fulfill fulfillment orders after a merchant requests fulfillment.

Add tracking information

In the last 28 days, your app must have added tracking information to 80% of the fulfillments that it creates within one hour of creation.

In cases where precise tracking information isn't available from a shipping carrier URL, you can provide a custom URL to your app's site under the tracking_url field in order to inform merchants and customers of high level tracking details.

Respond to fulfillment requests

In the last 28 days, your app must have responded to 99% of fulfillment requests within four hours by either accepting or rejecting the fulfillment request.

Respond to cancellation requests

In the last 28 days, your app must have responded to 99% of cancellation requests within 1 hour by either accepting or rejecting the cancellation request.

Respond quickly to rate requests

Over the last 28 days, the carrier rate endpoint provided by your app must respond in fewer than 500 milliseconds for 95% of calls.

Complete rate requests reliably

Over the last 28 days, the carrier rate endpoint provided by your app must successfully respond to 99.9% of requests.

Sync returns information

Your app must use the appropriate APIs to communicate all lifecycle events of a return to Shopify. These include:

• Creating returns
• Shipping creation
• Restocking
• Removing items from a return
• Cancelling a return
• Closing returns
• Providing refunds

Include exchange line items

Your app must create exchange line items on an order when managing exchanges. You must also remove exchange lines from the order if they are no longer needed.

Include shipping and restocking fees

Your app must add shipping fees and restocking fees on an order when applicable.

Enable printing on orders pages

Your app must use an admin print action extension to let merchants print invoices or packing slips for an individual order directly from the orders detail page as well as for any selected orders from the orders index page.