SHOXL
RELEASES

Previously, logging in with an email address was only possible if that address was unique within the administration. Users with a shared email address could only log in through the representatives module, which required additional manual setup.

We have extended the login system so that email addresses no longer need to be unique. When an email address is linked to multiple customer accounts, the user is presented with a list of accounts they can access. This makes it possible to always log in using an email address instead of a username or debtor number.

In addition, account activation and password resets have been enhanced. For email addresses linked to multiple accounts, these actions can now be completed in one step. This was not previously supported, and required manual activation by administrators.

Outcome: Logging in, activating, and resetting passwords is now simpler and more consistent for all users, even when an email address is associated with multiple accounts.

The webshop search has been optimized to deliver more accurate and relevant results. Search queries now prioritize matches in a logical order: article number, GTIN/EAN, title, description, and finally properties. This ensures that products most closely matching the search terms appear at the top of the results.

Additionally, when multiple keywords are used, the search now applies an AND condition, showing only results where all terms apply. This makes it easier for users to quickly find the exact products they are looking for.

To improve protection against automated abuse, reCAPTCHA V3 has been activated across all front-end pages. This ensures that interactions such as newsletter subscriptions are safeguarded against spam and bot activity, while keeping the user experience seamless.

The order history has been enhanced with an additional option to filter by delivery date. This makes it easier for users to quickly find and review past orders based on when they were delivered.

The basket feedback did not always display the most recently added article due to a bug. This issue has been fixed, ensuring the latest item is always shown to the user. As part of the fix, several performance improvements were made, resulting in faster and smoother handling of basket-related actions.

For admins and representatives with access to thousands of customers, loading the customer list could take a long time, especially when logging in on Safari or iPhone. This has been improved by introducing lazy loading. The list now loads much faster while search functionality remains just as quick and responsive, even with very large datasets.

Previously, when moving a classification node in the tree, users had to manually reload the page before continuing with additional changes. This extra step has been removed. The tree now refreshes automatically after each move and reopens the last active location, making it easier and faster to manage multiple node adjustments in sequence.

The read-more functionality in article descriptions did not work properly when large descriptions contained HTML elements. In those cases, the description was not split correctly, causing the read-more button to appear only at the end of the full text or not at all. This has been corrected so that descriptions are now consistently truncated and expanded as intended.

Authorizations define which customers can access specific products, product properties, and content items. By combining authorization profiles with customer assignments, it becomes possible to shape entirely customer-specific shops where users only see elements they are allowed to access.

With this update, changes to authorizations in Vendisto are now reflected in the shop almost instantly thanks to an improved fast-sync process. This applies to both product-level authorizations and authorizations on product properties. Updates for customer authorizations will be optimized in a future release.

Outcome: Managing customer-specific access is faster and more efficient, ensuring that updates in Vendisto are visible in the shop without delay.

Exporting very large price lists with millions of product, customer, and price combinations could previously cause memory errors and system crashes. The price list XML export has been rewritten to handle memory more efficiently, ensuring greater stability and reliability even with extremely large datasets.

Outcome: Nightly synchronizations with high record counts (such as 1.4 million entries) now complete successfully without memory issues.

Customers reported that not all available color options were shown on product pages. This was caused by an indexing issue in the product data, which prevented the full set of variants from being displayed. The underlying problem has been corrected, ensuring that all color variants are now visible in the catalog.

In some cases, the article overview did not display VAT labels when showing from/to prices. This has been corrected so that VAT information is always visible alongside discounted prices.

Some users were not seeing the full set of categories available to them. This was caused by an error in the logic that generated the first-level dropdown menu when combined with user authorizations. The issue has been fixed, and the category menu now correctly displays all options a user has access to.

Article imports could fail in some environments. The root cause was a missing database stored procedure required during classification merging.

This has been corrected by ensuring the procedure is created and invoked during import. As a result, article imports now complete reliably without errors.

Article imports could fail due to timeouts while retrieving data during synchronization. The root cause was long-running database reads in the sync pipeline.

This has been addressed by optimizing the data retrieval path and improving timeout handling. Imports now complete reliably without timing out.

In the February release, some outdated upgrade scripts were removed to improve database compatibility. During this cleanup, one script required for bulk article imports was unintentionally excluded from new setups. This caused import errors in certain environments.

The issue has been corrected, and all required scripts are now included again, ensuring that article imports work as expected on new installations.

The Shoxl shop supports searching with customer-specific product numbers through the MatchCustomerProducts endpoint. In the SmartLynx integration of this API, two issues were resolved:

• Errors when requesting CustomerProducts.
• A problem that occurred when opening the basket in the shop.

With these fixes, the integration now works reliably without returning server errors.

The article synchronization process between Vendisto and the shop could trigger database timeouts, leading to errors during FastSync. This was caused by inefficient queries that performed excessive scans per row.

The queries have been optimized to reduce database load and improve efficiency. As a result, article synchronization is now faster and more reliable, even with large datasets.

When displaying the basket, the shop previously triggered too many calls to the ERP system. This could lead to slow response times, especially for shops using the real-time REST API with slower ERP systems.

The process has been optimized to deduplicate API calls, greatly reducing the load on the ERP system. As a result, basket performance is now faster and more reliable.

We added full support for Pay.nl, a leading Dutch payment service provider offering a wide range of online payment methods. Pay.nl enables businesses to accept popular options such as iDEAL, credit cards, Bancontact, and many others through a single platform.

Our integration follows the advanced implementation route. This means the shop dynamically displays the payment methods configured in Pay.nl, just like in our Stripe integration. Methods are shown contextually, based on:

• Country-specific availability of payment methods.
• Customer-specific configuration rules.

This approach ensures that customers only see relevant payment options, providing a seamless checkout experience while giving merchants maximum flexibility in managing their payment setup.

Account activation and password reset processes have been fully integrated with the Account API. Previously, these actions were handled directly in Vendisto, but are now centralized within the API for improved consistency and maintainability.

• Account activation requests are processed through the Account API.
• Password reset flows are also routed via the API.
• This ensures a unified approach for authentication-related actions.

The change streamlines account management and provides a more robust foundation for future enhancements.

A new shop setting PaymentDiscountExcludeShippingCosts has been introduced. This resolves discrepancies between the webshop and ERP systems such as Exact Online, where shipping costs are not included in payment discounts.

When the setting is enabled, payment discounts are applied only to the product total, excluding shipping costs. This ensures the calculated totals align perfectly across systems.

• Configurable setting: PaymentDiscountExcludeShippingCosts.
• Discount can be calculated with or without shipping costs included.
• Unit tests cover the exclusion logic for accuracy and stability.
• Fully documented in the SettingsManager for easy reference.

This flexibility accommodates different ERP rules and prevents mismatched totals between webshop orders and ERP invoices.

A new setting, SalesOrderUser, has been added. When a sales order is created, this fixed value is stored in the order header in the CreatedByUser field. This makes it easier to identify and filter orders in Microsoft Navision based on the user who initiated the order.

A dedicated Navision connector has been implemented that leverages the Nav cache to provide price information. Unlike the generic ErpCache connector, which calculated prices using normalized data and did not meet the discount requirements, this connector ensures that discounts are applied correctly. This guarantees that discounts are not included when line discounts are disabled.

A new setting has been introduced that allows customer numbers to be automatically prefixed with their corresponding DataAreaId. This ensures consistency in environments where multiple business units are active.

When orders are placed, the prefix is automatically stripped so that requests are processed correctly, while all customer-specific integrations such as price retrieval and order history continue to function seamlessly.

• Customer numbers can be stored with a DataAreaId prefix.
• Prefixes are removed automatically during order submission.
• Price requests, order history, and other customer-specific processes remain unaffected.

This update reduces the risk of errors and guarantees smooth handling of customer data across different processes.

An issue in the article selection wizard has been resolved. Previously, when adding additional items to the basket, the system repeatedly added the first selected variant instead of the chosen items. The fix ensures that the correct items are now added as intended.

An issue in the article overview has been corrected. When switching between list and tile views, a custom page size was previously ignored and reset to the default value. The fix ensures that the webshop settings are now preserved when changing the view.

A problem in the shop has been fixed where the email address was missing when activating a user. The activation message now clearly displays the address to which the activation email was sent.

The Logo column in the ArticleGroup Excel import and export tasks was not being processed correctly. This functionality has now been fixed. Please note that an ArticleGroup can contain multiple Images, Icons, and Documents, but only one Logo.

The ManualTokenRequester—the tool that generates the initial token to access Exact—has been extended with additional checks on token rights. It now verifies whether the token has sufficient permissions for the endpoints used by the Exact Batch Interface.

We improved the user experience on product detail pages by adding a more user-friendly loading message while prices are being retrieved. This makes it clearer to customers that pricing information is on the way, instead of showing a blank or confusing placeholder.

An issue affecting order synchronization with Exact Online has been resolved. Illegal characters in order references previously caused XML generation to fail. These characters are now sanitized in advance, ensuring smooth and consistent order syncing.

A problem in the article overview has been fixed where the Add to Orderlist button was only active for the first item. As a result, other items could not be added to the order list. The fix ensures that the button now works correctly for all items in tile view.

An issue in the basket has been fixed where cost lines were not calculated correctly when tax was set to 0. This caused Recupel and Bebat totals to remain at zero. The fix ensures that these totals are now calculated accurately.

A problem was resolved where importing non-existent .min.css files triggered unnecessary URL parsing, leading to a fallback to the default language. Static files are now excluded from this process, preventing unwanted redirects and ensuring the correct language is maintained.

The Exact Online Batch Interface, which synchronizes data from Exact to the shop, has been optimized. In rare cases, the synchronization process stalled due to database timeouts when retrieving customer data. The efficiency of the related SQL queries has been improved, preventing these timeouts and ensuring smoother synchronization.

An issue has been fixed where representatives with full access but without specific rights could not view the quote representatives overview. The overview is now accessible to all representatives with the appropriate access level.

Customers can now be linked to multiple vouchers. An issue in the database interaction limited each customer to a single voucher association, which has been resolved.

• Customer import correctly assigns multiple vouchers to the same customer.
• Voucher API supports creating and updating multiple voucher links.
• Duplicate associations are prevented and validations are consistent.

This improvement gives more flexibility in promotions and ensures reliable voucher assignments during bulk imports and API operations.

An outdated feature in Vendisto caused an extra, unstyled order confirmation email to be sent alongside the correct one. This redundant email has been removed.

• Only the properly formatted order confirmation email is now sent.
• Prevents confusion caused by duplicate messages.
• Fix improves consistency and customer communication.

This ensures customers receive a single, clear, and professional confirmation after placing an order.

We introduced a new pricing service within Vendisto’s FO connector that replicates the price calculation logic of Dynamics 365 Finance & Operations. This ensures that the shop can display accurate prices, including all applicable line discounts, before an order is created.

With this update, customers immediately see their final discounted price in the shop, instead of only at checkout. The service works independently of the standard F&O e-commerce module, making it broadly applicable.

• Replicates F&O’s complex price calculation engine in Vendisto.
• Shows correct discount prices directly in the shop.
• Works even without the F&O e-commerce module.

This improvement enhances transparency for customers and creates a smoother ordering experience.

VAT numbers for new registrations were sometimes rejected due to recurring overloads at the EU VIES service for certain member states, even when the number was valid. This led to confusing feedback in the form.

We improved the validation flow and messaging to handle these situations gracefully and keep onboarding moving.

• Clear status feedback: The form now distinguishes between an invalid VAT number, a VAT number already registered in our system, and a temporarily unavailable VIES check.
• VIES fallback: When VIES returns a concurrency/overload response (e.g., MS_MAX_CONCURRENT_REQ), the submission proceeds and the VAT field is marked as “not validated”.
• Notification continuity: Registration emails are still sent with an explicit “VAT not validated” note so follow-up can occur without blocking the customer.
• Better error handling: The form shows an informative message instead of a generic error, guiding the user to continue or try again later.

These changes prevent false rejections, reduce friction during registration, and provide transparent next steps when external VAT validation is temporarily unavailable.

The platform now supports mapping custom order fields directly to the order line level in Microsoft Dynamics 365 F&O. This allows additional product-specific details entered during the ordering process to be stored and processed accurately within F&O.

• Custom fields entered in the shop are linked to order lines.
• Improves accuracy of order processing with customer-specific details.
• Provides more flexibility for handling unique product or delivery requirements.

This enhancement ensures that all relevant information is seamlessly transferred to F&O, supporting both operational efficiency and customer satisfaction.

Stock visibility can now be controlled with the MaxStockToShow setting. When the actual stock exceeds this configured maximum, the system displays the limit followed by a plus sign. This helps avoid exposing unnecessarily large inventory numbers while still showing availability clearly.

• Type: Number
• Example: Setting = 25 → shown as “25+” when stock is higher
• Default: null (full stock is shown)

Hovering over an asset used to always show the asset name in a popup, which could clutter the interface. This behavior is now optional and can be controlled via the new ShowAssetTitle setting.

• Type: Boolean
• Default: false (title hidden)
• Enable the setting to show asset names on hover when needed.

This provides cleaner visuals by default, while still allowing flexibility for cases where asset titles are useful.

The Caribbean guilder (XCG) was not recognized in the Microsoft .NET environment, as its globalization libraries do not yet include this new ISO 4217 code. This could cause missing or incorrect symbols when formatting amounts in XCG.

We addressed this by refactoring the currency handling and introducing an internal ISO 4217 fallback. This ensures XCG is displayed correctly across the application, regardless of .NET’s current limitations.

• Correct display and formatting for XCG amounts.
• Fallback mechanism for other unsupported ISO codes.
• Cleaner and more reliable currency handling logic.

Product and article group descriptions can now be limited to a maximum number of visible characters. When this limit is reached, the text is truncated neatly—at the end of a sentence if possible, or at the nearest space rather than mid-word.

A “Read more” button is automatically added below truncated content, allowing users to expand the full description and collapse it again with “Read less.”

• Configurable maximum character count per layout.
• Clean truncation for a natural reading flow.
• Expandable and collapsible descriptions for a smoother user experience.

The “Read more” control on product pages has been rebuilt to handle description content safely and predictably. The new logic keeps HTML tags intact, only shows the control when extra content actually exists, and maintains a clean toggle state between expand and collapse.

• No tag-splitting: the expander never breaks HTML elements.
• Control appears only when text extends beyond the collapsed limit.
• Stable toggle behavior—content doesn’t shuffle or duplicate on repeated clicks.
• CSS refined to prevent layout jumps during expand/collapse.

The result is a smoother reading experience and accurate visibility of the “Read more/less” link across product pages.

We refactored the YouTube thumbnail generator to read the play-overlay image from the embedded resource registry instead of the file system. This is an internal change—videos and thumbnails continue to appear as before.

• Eliminates file path dependency for youtube-play.png.
• More reliable thumbnail rendering across environments.
• No impact on end-user behavior or layout.

In Belgium, Recupel and Bebat are environmental contribution fees: Recupel applies to electronic devices for recycling purposes, while Bebat covers the collection and recycling of batteries. These supplements are mandatory and added on top of the product price.

The basket now clearly lists these supplements as separate cost lines for applicable items. This makes the environmental fees transparent and ensures the total basket value accurately reflects all obligations.

• Recupel and Bebat shown directly in the basket.
• Supplements no longer hidden in the product price.
• Clearer cost breakdown for customers.

What was missing

In the product detail view, the pricing information always appeared as a combined “From–To” range. This made it less clear compared to the product overview, where the values are shown separately.

What we improved

The product detail page now supports showing the From and To prices as distinct elements. This ensures consistency with the overview display and makes it easier for customers to understand the pricing structure at a glance.

• Clearer presentation of minimum and maximum prices.
• Consistent layout across product overview and detail pages.
• Better transparency for users comparing price ranges.

It was previously only possible to display discounts within the product detail page. This meant that customers browsing through the article list could not immediately see which items had a discount applied.

We’ve added the option to show the discount percentage directly in the article overview, both in the table view and in the tile view. This makes promotions more visible and helps customers quickly spot discounted products while browsing.

• Discount label visible in both ArticleListTable and ArticleListTile.
• Improved visibility of promotions at a glance.
• Consistent display across product list and detail views.

A change in the price display logic unintentionally caused tiered discounts to appear, even when the configuration setting to hide them was turned off. This created confusion for users who did not expect to see quantity-based pricing.

The logic has been corrected so that tiered prices are only displayed when explicitly enabled. This ensures consistent behavior between the configuration and what is shown to end users.

• No more unexpected display of tiered discounts.
• Clear alignment with the configured settings.
• Improved reliability of the price presentation.

What was happening

In release 2025.7, creating a new page in Vendisto could fail with the message “This name is already in use for another page in this language.” A generic “An error has occurred” notice also appeared.

What we changed

We corrected the page-title validation and restored a missing search component so that the unique-name check runs reliably. Creating a new page now works as expected when the title is available.

• Accurate validation of page titles (no false “already in use” messages).
• Stable behavior when saving a new page.
• Clear error reporting if a real conflict exists.

Notes for admins

The failure was linked to a missing dependency in the indexing layer, which caused the validation endpoint to throw an exception. This has been resolved.

Resetting selected filters could occasionally break the overview page due to a bug in query-string handling, resulting in an “undefined” state.

We updated the reset logic to sanitize and rebuild query parameters safely, restoring default filter states without errors.

• No more “undefined” results after reset.
• Consistent page load and accurate defaults.
• Cleaner URLs with valid parameters only.

Submitting the newsletter form could fail due to changes on the Mailchimp side, resulting in an error on submit. The integration has been updated and made more resilient, so sign-ups go through as expected.

• Updated Mailchimp API handling to align with current requirements.
• Graceful error paths and input validation to avoid false failures.
• Concise error logging in the Mailchimp interface for faster diagnosis.

When navigating to the final pages of a product list, the pagination controls could shift and display an inconsistent number of page links. This behavior has been corrected.

• Stable pagination display across the entire list.
• Same number of visible page links on first, middle, and last pages.
• Smoother navigation for users browsing large catalogs.

We migrated the Basket/Order List codebase from JavaScript to TypeScript to improve stability, maintainability, and developer productivity. The migration adds strong typing and clearer interfaces without changing how users work with the feature.

• Predictable behavior through compile-time checks and better error handling.
• Cleaner, more modular code for faster future enhancements.
• New styled message dialog replaces the old browser confirm(), allowing consistent branding.
• Minor UX polish applied across the Order List interactions.

No functional breaking changes are expected; the Order List continues to work as before, with a smoother and more consistent experience.

The RelatedArticle XML import now supports a Quantity attribute. This makes it possible to define how many units of a related component or supplement are included in the relationship, enabling more accurate data transfer from NAV.

The Navision Batch Interface has been extended to support supplementary articles in the PlaceOrder request. This ensures that required components linked to a main product are correctly transmitted during order submission.

A new Category attribute was added to the ItemCharge element in the XML structure. This makes it possible to show environmental charges like Recupel or Bebat separately in the basket, under their own translatable label as defined in the resource file.

Environmental charges such as Recupel or Bebat can now be applied based on the customer’s billing country. This is configured by matching the ISO 3166-1 alpha-2 country code in the ItemCharge to the debtor’s country code.

If no country is specified, the charge applies to all customers by default.

The article group overview page has been migrated to the new layout system. Both list and tile views now benefit from more granular layout options, providing improved control over presentation and structure.

To ensure accurate data for temporary price lists, the Exact Batch Interface now performs a full daily sync of both price list headers and periods. This replaces the previous partial update and improves consistency of pricing information.

Increasing the quantity of a composite article—an item with selected components—in the order list did not trigger a price recalculation. This has now been fixed to ensure that the total price updates correctly whenever the quantity of such an article is adjusted.

In the order list view, using the "Select all" button did not automatically set the quantity fields, requiring manual input per item. This has been fixed: after selection, each item’s quantity is now prefilled with its minimum order quantity as expected.

When loading related articles, authorization settings were not properly enforced. This allowed users to see items they were not authorized to view. The logic now correctly filters related items based on the user’s access rights.

In the new classification layout, the first-level category dropdown above the filter column did not respect user authorization settings or the configured category order. This has now been corrected—only permitted categories are shown, and they appear in the intended sequence.

The new category overview did not apply the correct article sorting, causing items to appear in an unexpected order. This has now been fixed, and articles are once again displayed in the intended sequence.

Due to unexpected null values in the underlying data, the generation of the