Does it play by the rules to redirect a user from the checkout page to an external app?

Extensions
,
1

Basically what the client needs is to give the user the option to finish the purchase on their own app. This mean that in the checkout (or some other page in the storefront) there should be a redirect button. This button, before redirecting, would grab the current cart data and send this to the client backend, then using this data to build a sort of cart.

Once that’s done the user would complete the purchase using other provider (such as Stripe) and create, through the API, the corresponding orders in Shopify to indicate the merchant what products were purchased.

Is this a feasible mechanism? Would Shopify allow this?

2

This is bypassing the checkout still so it would not be allowed.

4 Likes
3

Thanks for the response. My following question is, if said button is somewhere else, i.e. the navigation or just floating across all pages, NOT in the checkout, would this be allowed?

4

For custom use cases hitting general api restrictions have the merchant contact shopify support directly to seek authorization.

The stricter worded bypass rule that generally gets referenced applies to app store apps that are public/low-vis. Experience will vary.

1 Like
5

Are custom apps, ie: required by/made specifically for the merchant, tied to the same set of requirements?

6

Yes, Custom Apps aren’t exempt to these T&Cs. They used to be, this was changed in I believe 2021.

2 Likes
7

Specifically I think in what you describe the issue is the “cart” isn’t being sent back to shopify checkout/payment.
So even if you generate an order in the admin I think the issue becomes if it’s marked paid that counts as a bypass.
afaik based on other posts and staff replies; for stuff as simple as free gift item no purchase scenarios.
Get’s vague if you make the order but don’t mark it paid; even for a custom app.