Backlog

Next up

In Progress

Done

Options Price Calculator Roadmap

Add support for conditional field logic to dynamically show or hide fields based on user input.Scope<ul><li>Define conditions (e.g. if option A is selected → show field B)</li><li>Support multiple and nested conditions</li><li>Real-time visibility updates</li><li>Compatible with existing calculation logic</li></ul>Outcome More flexible configurations and a cleaner user experience by only displaying relevant fields.

Conditional Fields Logic

Ticket ontvangen

Floris de Vries

Description Introduce support for allowing multiple select fields of the same type within a single entity, rather than using a single multi-select dropdown. Each field instance should act as an independent selectable value.Business Value This enables more flexible data modeling where multiple discrete selections are needed without forcing them into a combined dropdown structure.Acceptance Criteria<ul><li>Users can add multiple instances of the same select field.</li><li>Each field instance behaves as an independent single select.</li><li>Users can add/remove individual select field instances dynamically.</li><li>Existing single select behavior remains unchanged.</li></ul>

Multi select field

We run a sticker website and would like to show the user a set of prices for varying quantities based on the other options (size, paper type, etc) already selected. We are willing to write custom themeing and frontend code to do this, but the Options Calculator doesn’t have a supported way to provide an arbitrary set of option values and run the calculation on them directly. We are requesting an officially documented way to execute the configured formula for the current product with an arbitrary set of option values so we could call the calculation with different quantity values than currently selected to create a UI element that looks like the following:<img data-width="100%" data-align="left" alt="" data-featurebase-content-key="6967c00ad8724572fdb59ab1/post/69deb93d4b9656b24914ebad/019d8e03-2ca6-716b-99cf-a5efa9af2b99/b64u-aW1hZ2UucG5n.png" src="https://6967c00ad8724572fdb59ab1.featurebase-attachments.com/c/post/69deb93d4b9656b24914ebad/019d8e03-2ca6-716b-99cf-a5efa9af2b99/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260827T060000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260827%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=ff830d258c63075ad94634e28d04e263dc99eaf77165971c30e4222b6764e03f" data-featurebase-content-filename="image.png">

Allow custom frontend javascript to calculate options

An Anonymous User

Currently, it is not possible to reference the number of uploaded files within formulas. It would be useful to introduce a variable that represents the total number of uploaded files, so this value can be used in pricing or calculation formulas.Use case: In situations where pricing or logic depends on how many files a user uploads, merchants should be able to include this value directly in their formula. For example, charging a fee per uploaded file or applying conditional logic based on the file count.Proposed solution: Introduce a variable (for example <code>uploaded_files_count</code>) that represents the total number of files uploaded by the user. This variable should be accessible within the formula builder and usable in calculations.Example: <code>price = base_price + (uploaded_files_count * file_fee)</code>Expected outcome: Merchants can dynamically calculate prices or apply logic based on the number of files uploaded, enabling more flexible configuration without custom development.

Allow formulas to use a variable for the number of uploaded files

Keep entered dimensions (e.g., width/height/length) when a user switches between product variants, instead of resetting the values.Scope<ul><li>Persist dimension inputs across variant changes</li><li>Define rules for when values should be kept vs. reset (e.g., only reset if variant uses different dimension fields/units)</li><li>Ensure price recalculation uses the preserved values immediately</li><li>Consistent behavior across product page, calculator view, and draft order flow (where applicable)</li></ul>Outcome Faster configuration and fewer user errors by preventing unnecessary re-entry of dimension values.

Preserve Dimensions When Switching Variants

Please add native 2D lookup-table (price matrix) support to Options Price Calculator so merchants can calculate a fixed final price from a width × height pricing grid without creating hundreds of conditional rules.<h4>Problem / Current Limitation</h4>We sell made-to-measure products (e.g., blinds/pleated shades) where the final customer price is defined by a discrete pricing matrix:<ul><li>X-axis: Width (in meters, typically 0.1 m increments)</li><li>Y-axis: Height (in meters, typically 0.1 m increments)</li><li>Cell value: Final gross price (already includes shipping costs and VAT)</li></ul>Because the price is not a simple linear function of area, we cannot use a compact mathematical formula reliably. Today the only way to implement exact matrix pricing is to create a very large number of IF/AND conditions (one per cell). This is:<ul><li>time-consuming to set up</li><li>error-prone to maintain</li><li>hard to audit</li><li>not scalable across multiple categories/price groups</li></ul><h4> Requested Solution</h4>Add a Lookup Table / Pricing Matrix feature that can be used directly in formulas and/or as a pricing option type.<h5>Core capabilities</h5><ol><li>2D lookup function<ul><li>A function usable in the formula builder, e.g.<ul><li><code>lookup2d(table_name, width, height)</code></li><li>or similar syntax consistent with your app</li></ul></li><li>Returns the value from the matrix cell at the resolved width/height.</li></ul></li><li>Step rounding / grid mapping<ul><li>Built-in rounding rules before lookup (especially important for mm inputs):<ul><li>Width and height are entered in mm by customers.</li><li>We need to map them to the grid by always rounding up to the next step.</li></ul></li><li>Example rule:<ul><li><code>width_m = ceil(width_mm / 100) / 10</code> (100 mm → 0.1 m steps)</li><li><code>height_m = ceil(height_mm / 100) / 10</code></li></ul></li></ul></li><li>Graceful out-of-range handling<ul><li>Configurable behavior when input is outside the table:<ul><li>show validation error, or</li><li>clamp to min/max, or</li><li>return default value.</li></ul></li></ul></li><li>Table management<ul><li>Create and manage multiple tables (we have ~10 categories × up to 5 price groups).</li><li>Import/export via CSV (and ideally bulk update).</li><li>Clear UI to define:<ul><li>column headers (widths)</li><li>row headers (heights)</li><li>numeric cell values (prices)</li></ul></li></ul></li><li>Fixed final price support<ul><li>We need the lookup result to be usable as a fixed final price (not only an add-on), and update live as customers type.</li></ul></li></ol><h4>Example (What we want to build)</h4><ul><li>Customer enters:<ul><li>width: 1188 mm</li><li>height: 742 mm</li></ul></li><li>Grid mapping:<ul><li>width → 1.2 m (round up to 0.1 m)</li><li>height → 0.8 m (round up to 0.1 m)</li></ul></li><li>Lookup:<ul><li><code>price = lookup2d(pg0_brutto, 1.2, 0.8)</code></li></ul></li><li>Output:<ul><li>display and charge that exact gross price.</li></ul></li></ul><h4>Business Impact</h4>This feature would dramatically reduce setup and maintenance effort and unlock accurate pricing for many industries that rely on matrices (blinds, curtains, wallpaper, stickers, custom panels, etc.).For our store specifically:<ul><li>We can implement exact pricing for ~10 product categories and up to 5 price groups each.</li><li>We can maintain pricing centrally by updating CSV tables instead of editing hundreds of conditions.</li><li>We can ensure pricing is always consistent, auditable, and scalable.</li></ul><h4>Acceptance Criteria</h4><ul><li>A merchant can upload a width×height pricing matrix and retrieve cell values via a formula/lookup.</li><li>Rounding-up-to-grid works with mm inputs.</li><li>The calculated price can be used as the final fixed price and updates live.</li></ul>If helpful, we can provide sample CSV matrices and a list of expected test cases for QA.

Request:  2D Lookup Table / Price Matrix Support for Made-to-Measure Pricing

The option to have Radio buttons appear side by side in a row instead of just in column

Radio Buttons Side by Side

Summary Add support for additional file formats (TIFF and EPS) within the upload functionality to improve compatibility with professional and design-oriented workflows.Background &amp; Context Currently, the platform supports a limited set of file formats for uploads. Users working with high-quality images or design assets often rely on formats such as TIFF and EPS. The lack of support for these formats requires users to convert files before uploading, which adds friction and may result in quality loss or workflow inefficiencies.Problem Statement<ul><li>Users cannot upload TIFF or EPS files directly</li><li>Additional conversion steps are required before upload</li><li>Potential quality degradation due to format conversion</li><li>Misalignment with common industry standards (design/print workflows)</li></ul>Proposed Solution Extend the upload functionality to accept and correctly process:<ul><li>TIFF (.tif, .tiff)</li><li>EPS (.eps)</li></ul>This includes validation, preview handling (if applicable), and backend processing/storage compatibility.

Support for Additional File Formats (TIFF &amp; EPS)

Support for Additional File Formats (TIFF & EPS)

Beso

Create a Shopify Admin product extension that allows assigning and managing a specific calculator configuration per product.Scope<ul><li>Shopify Admin UI extension on the product page</li><li>Select/assign a calculator (or calculator preset) to a product</li><li>Configure key calculator settings specific to that product</li><li>Save and sync the assignment to the app backend</li><li>Basic validation (e.g., prevent publishing without required calculator mapping)</li></ul>Outcome Simplifies setup for merchants by managing calculator-product configuration directly inside Shopify.

Shopify Product Admin Extension for Specific Calculator

Please add native 2D lookup-table (price matrix) support to Options Price Calculator so merchants can calculate a fixed final price from a width × height pricing grid without creating hundreds of conditional rules.<h4>Problem / Current Limitation</h4>We sell made-to-measure products (e.g., blinds/pleated shades) where the final customer price is defined by a discrete pricing matrix:<ul><li>X-axis: Width (in meters, typically 0.1 m increments)</li><li>Y-axis: Height (in meters, typically 0.1 m increments)</li><li>Cell value: Final gross price (already includes shipping costs and VAT)</li></ul>Because the price is not a simple linear function of area, we cannot use a compact mathematical formula reliably. Today the only way to implement exact matrix pricing is to create a very large number of IF/AND conditions (one per cell). This is:<ul><li>time-consuming to set up</li><li>error-prone to maintain</li><li>hard to audit</li><li>not scalable across multiple categories/price groups</li></ul><h4>Requested Solution</h4>Add a Lookup Table / Pricing Matrix feature that can be used directly in formulas and/or as a pricing option type.<h5> Core capabilities</h5><ol><li>2D lookup function<ul><li>A function usable in the formula builder, e.g.<ul><li><code>lookup2d(table_name, width, height)</code></li><li>or similar syntax consistent with your app</li></ul></li><li>Returns the value from the matrix cell at the resolved width/height.</li></ul></li><li>Step rounding / grid mapping<ul><li>Built-in rounding rules before lookup (especially important for mm inputs):<ul><li>Width and height are entered in mm by customers.</li><li>We need to map them to the grid by always rounding up to the next step.</li></ul></li><li>Example rule:<ul><li><code>width_m = ceil(width_mm / 100) / 10</code> (100 mm → 0.1 m steps)</li><li><code>height_m = ceil(height_mm / 100) / 10</code></li></ul></li></ul></li><li>Graceful out-of-range handling<ul><li>Configurable behavior when input is outside the table:<ul><li>show validation error, or</li><li>clamp to min/max, or</li><li>return default value.</li></ul></li></ul></li><li>Table management<ul><li>Create and manage multiple tables (we have ~10 categories × up to 5 price groups).</li><li>Import/export via CSV (and ideally bulk update).</li><li>Clear UI to define:<ul><li>column headers (widths)</li><li>row headers (heights)</li><li>numeric cell values (prices)</li></ul></li></ul></li><li>Fixed final price support<ul><li>We need the lookup result to be usable as a fixed final price (not only an add-on), and update live as customers type.</li></ul></li></ol><h4>Example (What we want to build)</h4><ul><li>Customer enters:<ul><li>width: 1188 mm</li><li>height: 742 mm</li></ul></li><li>Grid mapping:<ul><li>width → 1.2 m (round up to 0.1 m)</li><li>height → 0.8 m (round up to 0.1 m)</li></ul></li><li>Lookup:<ul><li><code>price = lookup2d(pg0_brutto, 1.2, 0.8)</code></li></ul></li><li>Output:<ul><li>display and charge that exact gross price.</li></ul></li></ul><h4>Business Impact</h4>This feature would dramatically reduce setup and maintenance effort and unlock accurate pricing for many industries that rely on matrices (blinds, curtains, wallpaper, stickers, custom panels, etc.).For our store specifically:<ul><li>We can implement exact pricing for ~10 product categories and up to 5 price groups each.</li><li>We can maintain pricing centrally by updating CSV tables instead of editing hundreds of conditions.</li><li>We can ensure pricing is always consistent, auditable, and scalable.</li></ul><h4>Acceptance Criteria</h4><ul><li>A merchant can upload a width×height pricing matrix and retrieve cell values via a formula/lookup.</li><li>Rounding-up-to-grid works with mm inputs.</li><li>The calculated price can be used as the final fixed price and updates live.</li></ul>If helpful, we can provide sample CSV matrices and a list of expected test cases for QA.

Voeg alstublieft native ondersteuning voor 2D-opzoektabellen (prijsmatrix) toe aan de Options Price Calculator, zodat verkopers een vaste eindprijs kunnen berekenen op basis van een prijsraster met breedte × hoogte, zonder dat ze honderden voorwaardelijke regels hoeven aan te maken.<h4>Probleem / Huidige beperking</h4>Wij verkopen op maat gemaakte producten (bijv. jaloezieën/plissé-gordijnen) waarbij de uiteindelijke klantprijs wordt bepaald door een discrete prijsmatrix:<ul><li>X-as: Breedte (in meters, meestal in stappen van 0,1 m)</li><li>Y-as: Hoogte (in meters, meestal in stappen van 0,1 m)</li><li>Celwaarde: Eindbruto prijs (inclusief verzendkosten en btw)</li></ul>Omdat de prijs geen eenvoudige lineaire functie van het oppervlak is, kunnen we geen betrouwbare compacte wiskundige formule gebruiken. Op dit moment is de enige manier om exacte matrixprijzen te implementeren het creëren van een zeer groot aantal IF/AND-voorwaarden (één per cel). Dit is:<ul><li>tijdrovend om in te stellen</li><li>foutgevoelig om te onderhouden</li><li>moeilijk te controleren</li><li>niet schaalbaar over meerdere categorieën/prijsgroepen</li></ul><h4>Gewenste oplossing</h4>Voeg een opzoektabel/prijsmatrixfunctie toe die direct in formules en/of als een type prijsoptie kan worden gebruikt.<h5> Kernfuncties</h5><ol><li>2D-opzoekfunctie<ul><li>Een functie die bruikbaar is in de formulebouwer, bijv.<ul><li><code>lookup2d(tabelnaam, breedte, hoogte)</code></li><li>of een vergelijkbare syntaxis die past bij uw app</li></ul></li><li>Geeft de waarde van de matrixcel bij de opgegeven breedte/hoogte terug.</li></ul></li><li>Afronding per stap / rastertoewijzing<ul><li>Ingebouwde afrondingsregels vóór het opzoeken (vooral belangrijk voor invoer in mm):<ul><li>Breedte en hoogte worden door klanten in mm ingevoerd.</li><li>We moeten deze naar het raster toewijzen door altijd naar boven af te ronden naar de volgende stap.</li></ul></li><li>Voorbeeldregel:<ul><li><code>breedte_m = ceil(breedte_mm / 100) / 10</code> (100 mm → stappen van 0,1 m)</li><li><code>height_m = ceil(height_mm / 100) / 10</code></li></ul></li></ul></li><li>Soepele afhandeling bij waarden buiten het bereik<ul><li>Configureerbaar gedrag wanneer de invoer buiten de tabel valt:<ul><li>validatiefout weergeven, of</li><li>begrenzen tot min/max, of</li><li>standaardwaarde retourneren.</li></ul></li></ul></li><li>Tabelbeheer<ul><li>Meerdere tabellen aanmaken en beheren (we hebben ~10 categorieën × tot 5 prijsgroepen).</li><li>Importeren/exporteren via CSV (en idealiter bulkupdates).</li><li>Overzichtelijke gebruikersinterface om het volgende te definiëren:<ul><li>kolomkoppen (breedtes)</li><li>rijkoppen (hoogtes)</li><li>numerieke celwaarden (prijzen)</li></ul></li></ul></li><li>Ondersteuning voor vaste eindprijs<ul><li>We willen dat het zoekresultaat bruikbaar is als een vaste eindprijs (niet alleen als een toeslag), en live wordt bijgewerkt terwijl klanten typen.</li></ul></li></ol><h4>Voorbeeld (wat we willen bouwen)</h4><ul><li>Klant voert in:<ul><li>breedte: 1188 mm</li><li>hoogte: 742 mm</li></ul></li><li>Rastertoewijzing:<ul><li>breedte → 1,2 m (naar boven afronden op 0,1 m)</li><li>hoogte → 0,8 m (naar boven afronden op 0,1 m)</li></ul></li><li>Opzoeken:<ul><li><code>prijs = lookup2d(pg0_brutto, 1,2, 0,8)</code></li></ul></li><li>Uitvoer:<ul><li>die exacte brutoprijs weergeven en in rekening brengen.</li></ul></li></ul><h4>Zakelijke impact</h4>Deze functie zou de installatie- en onderhoudsinspanning drastisch verminderen en nauwkeurige prijsbepaling mogelijk maken voor veel sectoren die gebruikmaken van matrices (jaloezieën, gordijnen, behang, stickers, panelen op maat, enz.).Specifiek voor onze winkel:<ul><li>kunnen we exacte prijzen implementeren voor ~10 productcategorieën en maximaal 5 prijsgroepen per categorie.</li><li>We kunnen de prijzen centraal beheren door CSV-tabellen bij te werken in plaats van honderden voorwaarden te bewerken.</li><li>We kunnen ervoor zorgen dat de prijsstelling altijd consistent, controleerbaar en schaalbaar is.</li></ul><h4>Acceptatiecriteria</h4><ul><li>Een verkoper kan een prijsmatrix met breedte × hoogte uploaden en celwaarden ophalen via een formule/opzoekfunctie.</li><li>Afronden naar boven werkt met invoer in mm.</li><li>De berekende prijs kan worden gebruikt als de definitieve vaste prijs en wordt live bijgewerkt.</li></ul>Indien nodig kunnen we voorbeeld-CSV-matrices en een lijst met verwachte testcases voor kwaliteitscontrole leveren.

Verzoek: Ondersteuning voor 2D-opzoektabellen / prijsmatrixen voor prijzen op maat

Planned

Clip & Shade

Description: Within the Options Price Calculator, options are currently displayed with text only. For better usability, we would like the ability to display the corresponding variant or option image when a user selects or views an option.Requested functionality: Add the ability to assign and display the variant image (or option-specific image) for each option inside the Options Price Calculator. The image should be shown in the image area when the corresponding option is selected, replacing the default product image.Value: This would provide a clearer visual representation of the selected option and improve the overall user experience, especially for products where visual differences between options are important.

Display option/variant image in Options Price Calculator

Afgerond

Add draft order functionality so orders (including products and configuration details) can be created, saved, and “flattened” into a fixed snapshot.Scope<ul><li>Create draft orders from selected products/configurations</li><li>“Flatten” draft order to lock product data, selections, and calculated prices at that moment</li></ul>Outcome Improved workflow for preparing orders by allowing users to save work-in-progress and preserve an exact order snapshot.

Draft Order Functionality

Allow users to view the price calculation breakdown in either table format or text format within the Options Price Calculator app.Scope<ul><li>Toggle: Table / Text</li><li>Table view: line-by-line breakdown (base price, each option, adjustments, subtotal, total)</li><li>Text view: readable explanation of the same calculation</li><li>Real-time updates when options change</li></ul>Outcome Improved transparency and easier interpretation of the calculated price.

Online Origins

Options Price Calculator Roadmap