# Preorders API Before diving into the API reference, it's important to understand the key term we use - Selling Plans ### What are Selling Plans? Selling Plans in the context of preorders are configurations that define how a preorder product is sold, billed, and delivered to customers. ### Core Purpose: * Enable merchants to sell products before they're in stock or available for immediate shipping * Define payment schedules, delivery timelines, and inventory management for preordered items * Provide customization options for how preorders appear and function in the storefront ### What data is present in a Selling Plan? * **Basic Information**: Name, internal reference name, enabled status * **Billing Configuration**: When and how much to charge (at checkout or later), charge types (percentage or fixed amount) * **Delivery Settings**: When products will be delivered (exact date or interval after purchase) * **Inventory Management**: How inventory is reserved and which system manages it * **Pricing Options**: Discount amounts or percentages for preordered items * **UI Customization**: Button text, badge styling, shipping information text ### Variant Association: * Selling plans can be associated with product variants in three ways: * All products in the store * Products in a specific collection * Custom selection of individual variants * Each variant can have custom settings like shipping text and maximum preorder quantity ### Multi-Market Support: * Selling plans can be configured for specific markets in multi-market stores * Different markets may have different preorder terms or availability --- # Agent Instructions: 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: ``` GET https://docs.stoqapp.com/preorders-api.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.