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 Users can add multiple instances of the same select field. Each field instance behaves as an independent single select. Users can add/remove individual select field instances dynamically. Existing single select behavior remains unchanged.

Floris de Vries 24 days ago

💡 Feature Request | Options Calculator

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. Probleem / Huidige beperking Wij verkopen op maat gemaakte producten (bijv. jaloezieën/plissé-gordijnen) waarbij de uiteindelijke klantprijs wordt bepaald door een discrete prijsmatrix: X-as: Breedte (in meters, meestal in stappen van 0,1 m) Y-as: Hoogte (in meters, meestal in stappen van 0,1 m) Celwaarde: Eindbruto prijs (inclusief verzendkosten en btw) 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: tijdrovend om in te stellen foutgevoelig om te onderhouden moeilijk te controleren niet schaalbaar over meerdere categorieën/prijsgroepen Gewenste oplossing Voeg een opzoektabel/prijsmatrixfunctie toe die direct in formules en/of als een type prijsoptie kan worden gebruikt. Kernfuncties 2D-opzoekfunctie Een functie die bruikbaar is in de formulebouwer, bijv. lookup2d(tabelnaam, breedte, hoogte) of een vergelijkbare syntaxis die past bij uw app Geeft de waarde van de matrixcel bij de opgegeven breedte/hoogte terug. Afronding per stap / rastertoewijzing Ingebouwde afrondingsregels vóór het opzoeken (vooral belangrijk voor invoer in mm): Breedte en hoogte worden door klanten in mm ingevoerd. We moeten deze naar het raster toewijzen door altijd naar boven af te ronden naar de volgende stap. Voorbeeldregel: breedte_m = ceil(breedte_mm / 100) / 10 (100 mm → stappen van 0,1 m) height_m = ceil(height_mm / 100) / 10 Soepele afhandeling bij waarden buiten het bereik Configureerbaar gedrag wanneer de invoer buiten de tabel valt: validatiefout weergeven, of begrenzen tot min/max, of standaardwaarde retourneren. Tabelbeheer Meerdere tabellen aanmaken en beheren (we hebben ~10 categorieën × tot 5 prijsgroepen). Importeren/exporteren via CSV (en idealiter bulkupdates). Overzichtelijke gebruikersinterface om het volgende te definiëren: kolomkoppen (breedtes) rijkoppen (hoogtes) numerieke celwaarden (prijzen) Ondersteuning voor vaste eindprijs We willen dat het zoekresultaat bruikbaar is als een vaste eindprijs (niet alleen als een toeslag), en live wordt bijgewerkt terwijl klanten typen. Voorbeeld (wat we willen bouwen) Klant voert in: breedte: 1188 mm hoogte: 742 mm Rastertoewijzing: breedte → 1,2 m (naar boven afronden op 0,1 m) hoogte → 0,8 m (naar boven afronden op 0,1 m) Opzoeken:

Clip & Shade about 2 months ago

2

💡 Feature Request | Options 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. Problem / Current Limitation We sell made-to-measure products (e.g., blinds/pleated shades) where the final customer price is defined by a discrete pricing matrix: X-axis: Width (in meters, typically 0.1 m increments) Y-axis: Height (in meters, typically 0.1 m increments) Cell value: Final gross price (already includes shipping costs and VAT) 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: time-consuming to set up error-prone to maintain hard to audit not scalable across multiple categories/price groups Requested Solution Add a Lookup Table / Pricing Matrix feature that can be used directly in formulas and/or as a pricing option type. Core capabilities 2D lookup function A function usable in the formula builder, e.g. lookup2d(table_name, width, height) or similar syntax consistent with your app Returns the value from the matrix cell at the resolved width/height. Step rounding / grid mapping Built-in rounding rules before lookup (especially important for mm inputs): Width and height are entered in mm by customers. We need to map them to the grid by always rounding up to the next step. Example rule: width_m = ceil(width_mm / 100) / 10 (100 mm → 0.1 m steps) height_m = ceil(height_mm / 100) / 10 Graceful out-of-range handling Configurable behavior when input is outside the table: show validation error, or clamp to min/max, or return default value. Table management Create and manage multiple tables (we have ~10 categories × up to 5 price groups). Import/export via CSV (and ideally bulk update). Clear UI to define: column headers (widths) row headers (heights) numeric cell values (prices) Fixed final price support We need the lookup result to be usable as a fixed final price (not only an add-on), and update live as customers type. Example (What we want to build) Customer enters: width: 1188 mm height: 742 mm Grid mapping: width → 1.2 m (round up to 0.1 m) height → 0.8 m (round up to 0.1 m) Lookup: price = lookup2d(pg0_brutto, 1.2, 0.8) Output: display and charge that exact gross price. Business Impact 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: We can implement

An Anonymous User about 2 months ago

💡 Feature Request | Options Calculator

Currently, the tax notifications/messages shown in the registration form are not translatable within the app. This limits localization support for multilingual stores and users. Requested Improvement Add support for translating all tax-related notifications and messages displayed in the registration form through the app’s translation system. Expected Result Users should be able to: Translate registration form tax notifications into all supported languages Manage these translations from the existing Translate tab/interface Provide a fully localized registration experience for customers Benefits Improved multilingual support Better user experience for international customers Consistent localization across the entire registration flow

Floris de Vries about 2 months ago

💡

Feature request | B2B & Wholesale

There are products we can’t exempt tax from, but no way to exclude them.

An Anonymous User about 2 months ago

💡

Feature request | B2B & Wholesale

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

An Anonymous User 2 months ago

💡 Feature Request | Options Calculator

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:

An Anonymous User 3 months ago

💡 Feature Request | Options Calculator

Summary Add support for additional file formats (TIFF and EPS) within the upload functionality to improve compatibility with professional and design-oriented workflows. Background & 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 Users cannot upload TIFF or EPS files directly Additional conversion steps are required before upload Potential quality degradation due to format conversion Misalignment with common industry standards (design/print workflows) Proposed Solution Extend the upload functionality to accept and correctly process: TIFF (.tif, .tiff) EPS (.eps) This includes validation, preview handling (if applicable), and backend processing/storage compatibility.

Beso 3 months ago

💡 Feature Request | Options Calculator

Currently, the app only works on the frontend. This means the VAT number is only added to the order when the customer creates the order themselves and has entered (or has) a VAT number. However, we would like to request support for backend-created orders as well. Specifically, when an employee creates a draft order in the backend on behalf of a customer who has a VAT number, the VAT number should also be included on the order. This would ensure consistency between frontend and backend order creation and improve workflows for merchants who manually create orders for customers.

An Anonymous User 4 months ago

💡

Feature request | EU Tax Exemption Plus

Currently, B2B orders are created as finalized orders immediately after checkout. This limits the ability to make changes or adjustments before processing the order further. Use case: In B2B scenarios, customers often pay using invoice or “net terms” (e.g. 30 days). In these cases, merchants typically need to review and adjust orders before finalizing them. This may include modifying products, applying custom discounts, or handling specific pricing agreements. Proposed solution: Allow B2B orders to be created as draft orders instead of finalized orders when customers choose payment methods such as invoice or net terms. These draft orders should remain fully editable before being completed. Expected outcome: Merchants gain more control and flexibility in handling B2B orders, enabling accurate order management, smoother invoicing workflows, and better alignment with standard B2B processes.

An Anonymous User 4 months ago

💡

Feature request | B2B & Wholesale

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.

Floris de Vries 4 months ago

💡 Feature Request | Options Calculator

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 uploaded_files_count) 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: price = base_price + (uploaded_files_count * file_fee) Expected outcome: Merchants can dynamically calculate prices or apply logic based on the number of files uploaded, enabling more flexible configuration without custom development.

Floris de Vries 4 months ago

💡 Feature Request | Options Calculator

Currently, the warehouse country is automatically determined. It would be helpful if users could manually select or override their warehouse country. This would improve flexibility for users who operate warehouses in different locations or want more control over their configuration. Goal: Enable users to manually set or adjust their warehouse country within the system. Benefit: Provides greater flexibility and accuracy for users managing warehouses in different regions.

Floris de Vries 4 months ago

💡

Feature request | B2B & Wholesale

Standard VAT rates are taken care off (per country) however most (but not all countries have lower VAT rates for different products like Food . In Shopify you can apply them as products overrides in Shopify settings - taxes and duties - (European Union) - Product overrides Food products like coffee and thee the country lower tax rate (varies per country) We have for shipping protection and giftcards 0% for all countries for which we collect normally VAT

An Anonymous User 4 months ago

💡

Feature request | B2B & Wholesale

Automatically assign tags to customers or orders based on predefined criteria. Scope Define tagging rules (e.g. order value, purchased product, customer type, location) Auto-tag customers based on behavior or attributes Auto-tag orders based on content or thresholds Support multiple rule conditions Ensure tags sync with existing tagging system Outcome Improved automation and segmentation by dynamically organizing customers and orders based on defined logic.

Floris de Vries 5 months ago

💡

Feature request | B2B & Wholesale

Add support for custom fields on orders to capture additional information that is not part of the standard order data. Scope Define custom fields (text, number, dropdown, checkbox, date) Configure which fields are required vs optional Display custom fields before the checkout Store custom field values on the order Outcome More flexible order intake by allowing merchants to collect and manage extra order-specific details.

Floris de Vries 5 months ago

💡

Feature request | B2B & Wholesale

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

Floris de Vries 5 months ago

💡 Feature Request | Options Calculator

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

Floris de Vries 5 months ago

💡 Feature Request | Options Calculator

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

Floris de Vries 5 months ago

💡 Feature Request | Options Calculator

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

Floris de Vries 5 months ago

💡 Feature Request | Options Calculator