> For the complete documentation index, see [llms.txt](https://flicky.gitbook.io/flicky-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flicky.gitbook.io/flicky-docs/resources/changelog.md). # Changelog New features and notable changes to Flicky, newest first. Have a request? Email . ## 1.0.0 — Initial release The first public release of Flicky: B2B Wholesale Pricing. **Added** * **Volume Discounts** — tiered "buy more, save more" pricing with automatic discounts that grow with cart quantity, plus targeting, eligibility, scheduling, and a live storefront preview. * **Pricing Rules** — custom B2B prices (percentage off, amount off, or a fixed price) for specific customers, tags, segments, markets, or companies, with priority resolution when multiple rules match. * **Variant Table** — a multi‑variant ordering table on the product page, with checkout‑enforced quantity rules (minimums, maximums, and pack multiples). * **Storefront app embed** — one‑time per‑theme toggle to display pricing, discounts, and variant tables on your storefront. * **Guided setup** — a first‑run walkthrough and a Dashboard with live rule counts for each feature. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://flicky.gitbook.io/flicky-docs/resources/changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.