> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/faq/why-am-i-seeing-a-different-price-than-on-the-app-store.md).

# Why am I seeing a different price than on the app store?

We run with a [**Pay What Feels Good**](/platform/policies/pricing.md) pricing policy.

The Shopify app store isn't designed for a fluid, discussion-driven pricing policy; instead, it's designed for predefined, static pricing tiers. So, we use that tier structure in the app store to present the suggested prices available for each Shopify plan. This has the side-effect of having Shopify present the smallest suggested figure as the "starting at" price for Mechanic, which is not an accurate description of how any of this works. :)

The price you see in-app is a suggestion, per step #1 of [our policy](/platform/policies/pricing.md). To learn what to do with that figure, [read the policy itself](/platform/policies/pricing.md).

If you've got questions, you are always invited to reach out, at <team@usemechanic.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.mechanic.dev/faq/why-am-i-seeing-a-different-price-than-on-the-app-store.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.