Options Price Calculator in Shopify Admin Draft Orders
We use Options Price Calculator extensively for made-to-measure rugs in our Shopify store. We also create a large number of orders manually through Shopify Admin → Draft Orders. We would like to be able to use the same OPC calculator that is already configured for each product directly when creating a Draft Order in Shopify Admin. Ideally, when adding an OPC product to a Draft Order, we could enter the same options as in the storefront (for example Width and Length), and OPC would calculate the final price using the existing product configuration and formulas. It would be very important that the calculator uses the same configuration as the storefront, so that we do not need to maintain a separate calculator or duplicate formulas/pricing. Our main use case is made-to-measure rugs priced per square metre: Width × Length × price/m² = final line item price This would make OPC significantly more useful for merchants who handle B2B, telephone, email and other manually entered orders.
Multi select field
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.
Verzoek: Ondersteuning voor 2D-opzoektabellen / prijsmatrixen voor prijzen op maat
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:
Make Registration Form Tax Notifications Translatable
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
Exclude some products from tax exemption
There are products we can’t exempt tax from, but no way to exclude them.
Radio Buttons Side by Side
The option to have Radio buttons appear side by side in a row instead of just in column
Allow custom frontend javascript to calculate options
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:
Support for Additional File Formats (TIFF & EPS)
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.
Feature Request: Support VAT Number functionality for Backend Draft Orders
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.
Make B2B orders as draft orders first
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.
Display option/variant image in Options Price Calculator
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.
Allow formulas to use a variable for the number of uploaded files
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.
Allow Users to Set Their Own Warehouse Country for tax exemption
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.
Different VAT rates removal for EU cross border B2B:
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
Auto Tags
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.
Orders Custom Fields
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.
Preserve Dimensions When Switching Variants
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.
Shopify Product Admin Extension for Specific 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.
Draft Order Functionality
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.
Conditional Fields Logic
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.