SHOXL
RELEASES

With the new Promotion Builder in Vendisto-NG, you design your own promotions, without a developer. Every promotion combines conditions (when does it apply), an action (what does the customer get) and limits (how long it runs and how often it can be used).

Start from one of seven ready-made templates:

• Product discount: a percentage or a fixed amount off selected articles, article groups or categories.
• Buy X, get Y: for example three for the price of two, or a discount on every third item.
• Order discount: a discount on the whole order, including tiered discounts that grow with the order total.
• Fulfillment discount: a discount for a chosen delivery or pickup method.
• Free product: the customer receives or chooses a gift once a threshold is reached, optionally in tiers.
• Cross-sell discount: buying product A gives a discount on product B, or on all related articles such as accessories.
• Loyalty credit: customers build up spendable credit based on what they buy, which is used automatically once it reaches a threshold.

Promotions can be targeted precisely: by price list, customer profile or customer number, by minimum quantity or amount, by delivery method or for a first order. Any condition can be reversed, for example to exclude a clearance category. A promotion applies automatically or with a discount code: single codes, codes generated in bulk or a personal code for every customer, with limits per code and per customer and a CSV export. Start and end dates, usage limits, priorities and stacking rules determine what happens when several promotions apply at the same time.

Before a promotion goes live, the simulator calculates it for a test basket, a customer and a date of your choice, using the same promotion service as the webshop. It shows which promotions apply, the discount per line and why other promotions do not, including tips such as how much more a customer needs to spend. The usage dashboard shows how often each promotion is used, the discount granted, every redemption and the loyalty balances per customer, and reveals active promotions that never apply.

Promotions are set up and tested in Vendisto; customers will see them in the webshop once the webshop integration is released.

Development of Vendisto-NG, the next generation of the Vendisto back office, continued with a strong focus on day-to-day operations:

• Orders: an order overview with status filters, and order details with order lines including variant information.
• Customers: a customer overview with tabs for general information, addresses, authorizations, commercial terms such as payment conditions and buying on credit, and orders. Customers can be created, blocked and activated, and users can be created and managed, including setting a password and changing their status.
• Bulk operations: start imports, exports and synchronizations from one screen, with upload, download and progress feedback, and direct links from the relevant dashboards.
• Dealers: manage dealer locations, with map positions based on OpenStreetMap.
• Product properties: add a property directly from a product or variant.

The highlight of this sprint is the built-in assistant. Users ask questions in plain language, such as what the stock and customer price of an article are, what a customer ordered recently or which products sell best, and get answers based on live data from customers, products, stock, prices and orders. The assistant only uses actions the user is authorized for, and is protected by a monthly usage limit and rate limiting.

Article group pages can combine the article selection wizard, where customers choose a variant step by step, with component selection, where they add matching parts or accessories (setting UseComponentSelection). This sprint makes that combination considerably more dependable:

• The chosen article and all selected components are added to the basket together, with the correct quantities and prices.
• Only components that belong to the selected article end up in the basket, also after switching between articles.
• Component prices take the VAT display switch, the ordered quantity and stock information into account.
• Reloading or sharing a page with a preselected article restores the matching component selection.
• As long as no article has been selected, a clear message asks the customer to choose one, instead of an empty component list.
• Default selections, deselection and the page URL behave consistently in every wizard Mode, and ordering stays disabled until a valid article is selected.

Products that are sold on request show a Request quote button. Logged-in customers still had to fill in the complete request form, including details the webshop already knows about them.

For logged-in customers, the quote request form is now prefilled with their known details, so they no longer have to re-enter information to ask for a price. The quote button also works reliably on the article page, just as on overview pages.

Search is often the fastest route to the right article. Several improvements make the results more dependable:

• Search results follow the sort order the customer selects, such as price or name, while relevance still determines which articles match the search term.
• Searching for a complete article number shows that article, not another product from the same group.
• Moving to the next page of a filtered overview opens the page as expected.

Three improvements make the Exact Online integration more dependable, especially for larger assortments:

• Prices are linked through the item itself rather than through the item code stored on the price line, so prices and price list authorizations stay correct after an item code has changed in Exact Online.
• Article exports with many sales price lists and volume discounts complete without timeouts.
• The initial synchronization of a new environment loads warehouse data first, so items synchronize without errors.

Synchronization has also become faster and more robust: changes are processed in chronological order, and a sync only records its progress once updates and deletions have succeeded.

Webshops depend on complete and consistent data from the ERP. Three improvements close gaps in that exchange:

• Microsoft Dynamics 365 F&O: the synchronization of discount agreements no longer skips records, so the full set of agreements is available in the webshop.
• ERP cache: order history imports no longer stop on unusual date values, so every order appears in the customer's order history.
• Shoxl REST integrations: payment cost lines, such as a cash on delivery fee, include their article number in the order sent to the ERP.

A series of improvements keeps everyday ordering running smoothly:

• In webshops that use the Calculate Order flow (LimitOrderCalculation), discounts calculated by the ERP remain visible in the basket after recalculation.
• When drop shipment is used for alternative delivery addresses, orders with such an address are sent to the ERP as drop shipments again.
• The preferred delivery date in the checkout form is validated correctly.
• In the order history, orders can be expanded and reordered from every page, not only the first.
• The robots.txt file for search engines is always served correctly.

Some accounts have no registered default delivery address, for example accounts that order for a location while the invoices go to another account. For these users, switching between pickup and delivery in the checkout could make the order fail, and orders could end up on the wrong account in the ERP.

Orders from these accounts are now processed correctly and placed for the account that actually ordered. Pickup orders work for users without a delivery address as well, and the order confirmation shows the pickup location, or the address of the merchant, as the delivery address.

Online payments do not always succeed at the first attempt. Customers cancel a payment, switch to another payment method or go back to the basket to change something, while payment providers report the outcome in the background.

The order and payment flow has been reworked to handle these situations reliably:

• One order per checkout: when a payment is cancelled and the customer tries again, the webshop continues with the same order and order number instead of creating a new one. A different payment method and updated totals are applied to that order.
• Payment status in Vendisto: status updates from the payment provider are stored on the order in Vendisto, so each order shows its current payment status.
• ERP after payment: in webshops that only pass paid orders to the ERP (PlaceOrderMode set to PayBeforePlaceOrder), the order is sent to the ERP as soon as the payment succeeds. Orders that have already been passed on are never sent again.
• No duplicate submissions: a basket that has already been ordered can no longer be submitted a second time from another session.
• Payment surcharges: percentage-based payment surcharges are calculated consistently over articles and shipping costs, and the PaymentDiscountExcludeShippingCosts setting is applied correctly.

The result is a cleaner order administration, with fewer orphaned or duplicate orders and payment information that matches what customers actually paid.

A large number of modules came together in Vendisto-NG, the next generation of the Vendisto back office:

• Promotion engine: a management interface for the new promotion engine, with tiered discounts, loyalty credit, cross-sell offers and gift promotions, a simulator to test promotions in advance, and a promotions dashboard.
• Widget-based dashboards: personal dashboards built from widgets that can be added, dragged and resized, multiple dashboards per user, and widgets for content, navigation, knowledge and Google Analytics insights.
• PIM: classification management (structure, properties, media, content and authorizations), and creating and editing products and variants, including related articles and product status.
• Content: a drag-and-drop page tree, and new modules for downloads and notifications.
• Usability: tabs indicate when they contain unsaved changes, and save buttons are disabled instead of hidden.

Warehouses often combine shipments that go to the same address. That only works when orders refer to the same address record in the ERP. Webshop orders sent to Microsoft Dynamics 365 Finance & Operations, however, created a new address record for every order, even when the customer had chosen one of their existing addresses.

Addresses synchronized from F&O now carry their F&O address reference, and webshop orders pass this reference along. F&O links the order to the existing address instead of creating a new one, so shipments to the same address can be consolidated again. Order-specific delivery addresses entered in the checkout are still sent as one-off addresses.

Retrieving large data sets from Microsoft Dynamics 365 Finance & Operations through OData means requesting data page by page over the network, subject to throttling. For large assortments that takes time and puts load on both systems, and every run starts again from the full data set.

The integration can now use the Data Management Framework (DMF) of F&O, with recurring integrations. F&O exports the data in its own batch process, set-based inside the database, and places the result in a queue that the integration picks up. Thanks to change tracking, only changed records are exported.

The benefits:

• Incremental instead of full: only changes are transferred, so synchronizations finish much faster and data in the webshop is more current.
• Scalable: the heavy work happens inside the F&O database instead of over the network, without paging or throttling, also for very large assortments.
• Lighter for F&O: slim, dedicated data entities with only the fields the webshop needs, exported on the own schedule of F&O.
• Reliable: data packages are processed idempotently and only acknowledged after successful processing, so nothing gets lost when a run is interrupted.
• Standard Microsoft technology: DMF is the data framework that F&O partners already know, which makes onboarding new environments straightforward.

The output for Vendisto and the webshop remains the same, so existing processes continue to work. DMF is available for articles, attributes and contacts.

Large Microsoft Dynamics 365 Finance & Operations environments combine several companies, hundreds of thousands of orders and extensive product data. Several synchronization and export steps have been reworked to handle these volumes reliably:

• Gross prices per company: gross prices are synchronized separately for each company (data area). An issue in one company no longer blocks the others, each company appears as its own step in the synchronization overview, and individual companies can be skipped or excluded. The gross price export now also contains each article only once per company.
• Order history: only orders that changed since the previous run are synchronized, now also when the change is in the order lines, and very large initial exports are processed in stable batches.
• Order and related-article exports: large exports use far less memory and no longer time out.
• Product images: image archives are exported with consistent file names, so they are always recognized during import.
• Customers: duplicate users and representatives are filtered out of the customer export.

Product images from Microsoft Dynamics 365 Finance & Operations were stored in the integration database and processed again with every article export. For large assortments, that made exports heavy and memory-intensive.

Images are now exported in a step of their own (ArticleImage) and stored as files instead of in the database. Article exports no longer process every image and run with far less memory. At the same time, the export consistently includes every image marked as a product image in F&O, with the default image first.

Orders shipped directly to an end customer (dropshipment) often follow a different delivery planning than regular deliveries to the customer's own address.

Delivery schedules now support a separate Dropshipment schedule type. When a customer selects an alternative delivery address in the checkout, the webshop automatically applies the dropshipment schedule, so the available delivery dates match the way the order will actually be shipped.

Customers can have their own VAT code in Exact Online. When such a customer-specific VAT code was removed in Exact Online, Vendisto kept the old value.

Removing a customer-specific VAT code in Exact Online now also clears it in Vendisto during the customer import, so VAT is applied according to the customer's current settings.

Product data and customer teams rely on imports to keep large data sets up to date. Several imports have been made more robust:

• Related articles: imported relations are always saved and appear in the shop.
• Customers: large customer imports with many addresses and users are written in smaller batches, supported by additional database indexes, which prevents time-outs.
• Synchronization: article groups no longer receive a URL that belongs to the history of another article group, and price data for article numbers containing a slash is cleaned up correctly.

Product content is prepared as a file before it is processed further, for example into a marketplace feed. When retrieving the content produced an empty file, that file could replace the one already prepared, resulting in an empty feed.

The size and content of retrieved product data are now validated before anything is written. Empty or incomplete content never replaces an existing file, so feeds keep their last valid content.

Spare parts lists can include parts that are not sold as separate products in the webshop. These parts were shown without an image.

Spare parts now use the image references stored with the assembled product, so every part in the list can be recognized at a glance. Paging through long spare parts lists works correctly again as well.

Two emails show more complete information:

• Quote confirmations include the gross price and discount per line again, so customers see the advantage they receive.
• Account registration emails use the invoice address as delivery address when the applicant did not enter a separate delivery address.

A set of improvements helps customers enter their orders correctly:

• The requested delivery date is validated on both the page and the server, invalid or past dates are rejected, and the error message explains what to change.
• When accepting the terms and conditions is required, an order can only be placed after the box has been checked.
• Article names no longer show empty brackets when an article has custom order fields that were left empty.
• Quantities in order lists can be set back to zero, so a line can be left out when the list is added to the basket.

Since the webshop moved to .NET 10, a number of details were found that did not yet work as before. These have been resolved:

• Switching the language keeps the selected language on every page.
• Image galleries show the images of all variants again, and product overview pages load without errors.
• Payment method icons are displayed in the checkout, and payments through Stripe complete normally.
• Selecting a subcategory in the category filter shows the matching products.
• Pages with tabs, the order history layout and the search results for pages, news and knowledge articles display correctly.
• User-specific settings, such as order mode, stock display, delivery cost thresholds and available payment methods, are applied per user again.
• Web service responses for OData queries are returned correctly.

Webshop orders used to reach Vendisto only once they had been sent on to the ERP. In webshops where customers pay online before the order is placed, an order that was started but not (yet) paid was not visible in Vendisto at all, which made it hard to follow up on unfinished payments.

The webshop now creates every order in Vendisto during checkout, before it is sent to the ERP, including orders that are still awaiting payment. Each order shows where it stands: whether payment has been received and whether the ERP has picked it up.

When payment must be completed before the order is placed (setting PlaceOrderMode), recording the order in Vendisto does not send it to the ERP early. Repeated checkout attempts, payment returns or payment notifications never create duplicate orders in Vendisto or the ERP.

Work on Vendisto-NG, the next generation of the Vendisto back office, focused on refining the new product management screens, so product data teams can work faster in the new back office:

• Product information: a redesigned product overview, and new media, properties and variants tabs on the product detail page.
• Design: refreshed layouts for the pages and properties screens and the content builder frame.
• Dashboard: amounts are shown in the correct currency.

Customers who send goods back want to know where their return stands. For webshops connected to Microsoft Dynamics 365 Finance & Operations, return orders were not yet available in the customer portal.

The return orders overview in the customer portal now shows return orders straight from F&O. For each return order, customers see the return order number, their own reference, the status and the return deadline, and per line the item, description, quantity, unit and status.

The overview is available to users with the Returns right and uses a responsive layout that works well on mobile devices.

Organizations with large assortments and multiple companies in Microsoft Dynamics 365 Finance & Operations rely on the integration to keep thousands of articles, prices and customers in sync. This sprint brings a series of improvements to make that synchronization more complete and dependable:

• Complete full synchronizations: large result sets are paged correctly, duplicate rows in article exports are prevented, and article details are synchronized independently of each other.
• Exact discount percentages: discount percentages are stored with up to six decimals, so calculated prices match F&O exactly.
• Real-time prices from the right company: price requests now take the customer's company into account.
• More control: individual entities can be skipped during a synchronization run, and the order language mapping can be configured.

When product variants are bundled on one product page, search engines could still find and index the individual variant pages through the sitemap. Those pages then competed with the main product page in search results.

The sitemap now lists only the main product pages, and variant pages refer to their main product with a canonical URL. Search engines concentrate on one page per product family, while variant links keep working for visitors. When a product has only one active variant, that variant page remains its own canonical page.

Since Sprint 77, customers working with Microsoft Dynamics 365 Finance & Operations can view their quotations in the customer portal. They can now also act on them:

• Confirm a quote directly from the overview or detail page. Confirming asks for a final confirmation first, so a quote is never accepted by accident, and the confirmation is registered in F&O. Expired quotes cannot be confirmed.
• Request a change for quotes that are open for changes. This opens an email with the customer number and quotation number already in the subject line, addressed to the recipient set in RequestChangeEmailAddress.

Each action is only enabled when it applies to the quote. The overview columns Confirm and RequestChange can be added as needed.

Quote requests submitted in the webshop were always emailed to the general shop manager address, while many organizations handle quotations in a separate team.

In the Vendisto email settings, quote request emails can now be sent to a dedicated address, with additional BCC addresses, in the same way as quote emails. Without a dedicated address, the shop manager receives them as before. The settings are vendisto:QuoteRequestShopManagerEmailAddress and vendisto:QuoteRequestShopManagersBCC.

Organizations with a large customer base regularly import thousands of customers and users at once, which could take a long time with the standard customer import.

Vendisto now offers a bulk customer import, comparable to the bulk article import. It processes the file in batches, with faster lookups and password handling, keeps memory use under control and reports its progress per phase. Customers are identified by their debtor number. The bulk import is enabled with vendisto:EnableCustomerDataBulkImport; the existing customer import remains available unchanged.

With very large asset libraries, the article import could time out while linking imported articles to their existing images and documents. This step now uses an efficient lookup, so large article imports run to completion.

The price list export for Exact Online could stop with an error when the same item appeared more than once in the stock positions retrieved from Exact. Duplicate entries are now filtered out, so price lists keep synchronizing.

Webshops can allow businesses and schools to order on account as a guest. When such an order is placed, an account is created in Exact Online automatically. That new account did not receive a payment condition, so the same customer could suddenly no longer order on account after logging in as a regular customer.

With the new setting DefaultB2BPasserByAccountPaymentConditionCode, automatically created business accounts receive the configured payment condition right away. Customers keep the same payment options for every following order, without manual changes in Exact Online.

When a customer adds a product to the basket, the webshop confirms it, for example by opening the side basket. On a phone, that side basket covers the whole screen and has to be closed every time, which slows down customers who order many lines in one session.

The add-to-basket feedback can now be set separately for desktop, tablet and mobile with FeedbackTypeDesktop, FeedbackTypeTablet and FeedbackTypeMobile. When no device-specific value is set, the general FeedbackType applies, so existing configurations keep working.

A new feedback type, ButtonBlink, shows a short confirmation animation with a checkmark inside the order button itself, after which the button returns to normal. Customers get clear confirmation without leaving the page or closing a panel, which makes it a natural choice for fast ordering on mobile.

Product information management arrived in Vendisto-NG, the next generation of the Vendisto back office:

• Products: overviews and edit pages for article groups and their variants, including classification and properties, with saved grid settings.
• Catalogue settings: overviews and edit pages for units, property categories and related article types.
• Properties: create, edit, delete and reorder properties, with multilingual values (including copying from the main language), units, icons, authorizations and dedicated inputs for yes/no and list values.
• Assets: drag and drop assets onto products, and see which assets in the library are already in use.

Many large B2B buyers order through an e-procurement system such as SAP Ariba or Coupa. Their employees start in that system, pick products from supplier catalogues and send the result through the internal approval flow. Shoxl already supported this with OCI PunchOut.

The shop now also supports cXML PunchOut, the standard used by most procurement platforms:

• the procurement system opens a shop session with a PunchOut setup request, and the user is logged in automatically;
• the user shops with their own assortment, prices and conditions;
• at checkout, the basket is returned to the procurement system as a PunchOut order message, ready for internal approval and the purchase order.

Each procurement system is registered as a client with its own identity and a securely hashed shared secret (CxmlPunchOut.Enabled and CxmlPunchOut.Clients). A test tool that simulates the procurement side is available for setting up and testing new connections.

In webshops that calculate orders in Microsoft Dynamics 365 Finance & Operations, the ERP determines customer-specific discounts per order line. Customers saw the resulting net price, but not the discount behind it.

The order calculation now also returns the discount percentage per line, and the new basket layout element DiscountPercentage displays it, for example: Price including 15% discount. Lines without a discount show nothing extra. The text is available in all webshop languages.

A Microsoft Dynamics 365 Finance & Operations environment usually contains many more items than the webshop should offer. Keeping the online assortment exactly in line with the items released for the webshop in F&O required regular manual checks.

The F&O integration now uses the export visibility of articles in F&O as a filter:

• full exports contain only articles that are visible for the webshop, and visible articles that are still missing are synchronized automatically first;
• partial exports remove articles from the webshop as soon as they are no longer visible in F&O;
• the integrity check of the integration cache gives more specific advice when differences are found.

The new integration engine (V2) is now the only version, and it gained an export preview to check what an export will contain before it is sent, a page size per synchronization profile for large F&O queries, a step-by-step mode for diagnosing synchronizations, and delivery address names taken from the address description in F&O.

The webshop assortment follows the choices made in F&O, without manual corrections.

For orders paid online, the reference of the payment provider is the key to matching payments with orders. This reference was not always stored with the order.

The webshop now stores the payment reference for all supported payment providers, including Mollie, Pay., Stripe, MultiSafepay and Rabo OmniKassa, and includes it in the order data. Finance teams can match incoming payments to orders without searching.

Customers use the invoice overview in the customer portal to check and download their invoices. For webshops connected to Exact Online, the invoice history in the portal did not always match Exact.

Invoices are now synchronized through the current Exact Online interface, ahead of Exact retiring its older XML interface, and the PDF of each invoice is included. The invoice history in the portal is complete, matches Exact Online and offers every invoice as a PDF.

In Belgium, many products carry a mandatory environmental contribution, such as Bebat for batteries or Recupel for electrical and electronic equipment. These fees must be shown and charged separately from the product price.

For webshops connected to Microsoft Dynamics NAV, the real-time price calculation now retrieves the environmental fees that apply to each article and returns them as separate cost lines. Customers see the correct fees per product, and the order total matches the ERP.

A quote request is often the first contact with a new business customer. To prepare a quote, sales teams regularly had to ask for basic company details afterwards.

The quote request form now also asks for the Chamber of Commerce number, address, postal code, city, customer number and salutation. These details are included in the quote request email, so the sales team can respond right away.

Vendisto shows per user when they last logged in to the webshop, but this information was not part of the customer export.

The customer Excel export now includes a Last Login column for every user. Account managers can quickly see which customers actively use the webshop and which ones might need a reminder or some help getting started.

As webshops move to the new .NET 10 version of the shop, this sprint resolved a number of follow-up points so that everything keeps working as customers are used to:

• the advanced order history in the customer portal loads and displays correctly;
• static lists placed on content pages are shown again;
• payment status updates from Pay. are processed correctly;
• logged-in users stay logged in when a new version of the webshop is deployed. The location of the security keys involved can be set with shoxlpro:DataProtectionKeysPath.

Several smaller improvements make ordering and browsing more dependable:

• In the order grid, variants that come in a single size can be selected and ordered for every color.
• Sales representatives who log in on behalf of a customer that has never logged in before can browse categories right away.
• News items whose title starts with a language code, such as en or fr, get a correct URL.

Improvements in Vendisto for content and product data management:

• The page overview shows the site structure again, and the display order of pages within a navigation can be changed.
• The Position products dialog for classifications no longer shows deleted products and article groups, so the order of the remaining items is easy to manage.
• The import of assembled products processes its files reliably again.

Translating product data used to mean exporting a separate Excel sheet for every entity type and language, filling them in and importing them again. For a webshop with one source language and five target languages, that quickly adds up to dozens of files per round.

Translato replaces this with one workspace that connects directly to Vendisto:

• Fetch: all translatable content for the configured languages is loaded from Vendisto in one step.
• Auto-translate: empty translations are filled with AI suggestions from DeepL or Claude.
• Review: translations can be filtered by entity, language, field and status (not translated, AI concept, user concept, translated) and approved one by one or in bulk.
• Publish: approved translations are written back to Vendisto.

Translato opens from a new menu entry in Vendisto and uses the Vendisto login. It is enabled per environment with the vendisto:TranslatoUrl setting; the source language is set with vendisto:SourceLanguageId.

Vendisto-NG, the next generation of the Vendisto back office, made big steps this sprint:

• Import/Export module: one place for all import and export tasks, with grouped settings per module, separate steps for import and export, and settings shown according to user rights.
• Translation module: translate content with pluggable translation engines, directly from the back office.
• New look: a new theme in light and dark mode, a redesigned login page, a collapsible side menu with fly-out navigation and a consistent page header on all edit pages.
• Home dashboard: KPI cards with trends, a period selection, an improved sales chart and a bar chart of the most popular products.
• Audit trail: pages show who last edited an item.
• Content builder: a renewed, more spacious interface with ready-made page blocks.
• Bulk actions for news and knowledge items, and quick filters on publication status in overviews.

When online payment is required before an order may be sent to the ERP, an unpaid order never reaches the ERP. Customer service had little to go on: the order overview in Vendisto did not show how an order was paid or whether it had been transferred.

The order overview has been redesigned around the information customer service needs. Next to order number, date, customer and total, it now shows:

• the payment method and payment status, so unpaid online payments stand out;
• the ERP sync status, showing whether the order has reached the ERP;
• the currency, order status and delivery method.

Columns that were no longer relevant have been removed, and the order and order line screens have been tidied up accordingly. Every order now also records its source, the channel it came from. The webshop sends this with each order (setting OrderSourceName, default Shoxl Webshop), and existing orders have been updated retroactively.

Webshops that sell in several currencies need to know in which currency each order was placed, and want sales figures they can compare.

Vendisto now stores the currency of every order and shows it in the order overview and order details. Dashboard figures are converted into one display currency, set with vendisto:DisplayCurrency, using daily reference exchange rates that are refreshed automatically.

The new engine of the Microsoft Dynamics 365 Finance & Operations integration was extended with tools that give administrators more control and keep large environments running smoothly:

• Targeted synchronization and export: synchronize or export specific articles, including their related data, or run several actions at once, without a full cycle.
• Returned orders: return orders are now synchronized from F&O.
• Integrity check: compare the integration cache with F&O and repair differences from a dedicated menu, in several modes.
• Stock: stock is synchronized in a step of its own, separate from article data.
• Stability: memory leaks during long runs have been fixed.

Products sold by weight or length are often ordered in decimal quantities, such as 2.5 kg. Order lists, however, only saved whole numbers.

Order lists now save decimal quantities, and a quantity of zero can be saved as well. Adding a product to an order list also no longer shows an unnecessary second confirmation window.

Customers who chose to pick up their order and paid online, for example with iDEAL, could not complete the order: the payment step failed because the order had not been created yet. Cancelling a payment also switched the delivery method back from pickup to delivery.

Pickup orders can now be paid online without issues, the chosen delivery method is kept when a payment is cancelled, and switching between pickup and delivery in the checkout form works consistently.

Users can be set up without the right to place orders, for example to browse the assortment and view prices only. Product tiles in overviews could still show an order button for these users.

Order buttons on product tiles now follow the same restriction as the rest of the webshop, so users without ordering rights no longer see them.

When the article selection wizard pre-selects a variant, the product image should match that variant. In some cases a broken image could appear, or the image and gallery did not follow the selected variant.

The wizard now updates the main image, the zoom link and the image gallery to the first image of the selected variant, and no longer shows a broken image.

After a sales representative logged out without selecting a customer, the next user to log in on the same device could land on the sales representative overview, even without representative rights.

The representative page is no longer used as a return address after login, so every user lands on the page that belongs to their own account.

In webshops that do not use Google Tag Manager, a script in the payment step could fail because a tracking object had not been initialized. The checkout now runs without script errors, whether or not Tag Manager is configured.

Many B2B customers receive a quotation before they order. For organizations working with Microsoft Dynamics 365 Finance & Operations, those quotations lived in the ERP and in email, separate from the customer portal where customers manage their orders.

The quote overview and quote detail pages in the customer portal now show sales quotations straight from F&O, retrieved in real time. Customers see each quote with its quotation number, description, customer requisition number, dates, status, addresses, lines and totals, right next to their orders.

The overview columns CustomerRequisitionNumber and Description can be added as needed, and IncludeExpiredInOverview determines whether expired quotes are listed.

The connection is built on a generic quote service, so other ERP systems can be connected in the same way. The connector is selected with ShoxlConnectorModuleForQuoteDataService.

The pages module of Vendisto-NG, the next generation of the Vendisto back office, is now in place:

• Pages: an overview of all pages with a grouped view, and an edit page that adapts to the page type, including template selection.
• Navigation: manage the site navigation in a tree structure, including the classification-based parts of the menu.
• Content builder: the drag-and-drop content builder is integrated into page editing, and HTML is wrapped automatically so content can be edited right away.

Since its launch, the Shoxl shop has run on Microsoft .NET Framework. That platform only receives maintenance fixes: no new features, no performance work and a shrinking choice of modern libraries.

The shop has now moved to .NET 10 and ASP.NET Core, Microsoft's current long-term support release. This sprint completed the migration of the web application itself, building on earlier sprints in which all shop libraries were made compatible. Every part of the shop, from the home page and catalogue to the basket, checkout and customer portal, was tested on the new platform.

What this means for webshops:

• Security: .NET 10 receives security updates from Microsoft until November 2028, and the shop now uses the security building blocks of ASP.NET Core, such as its data protection and authentication framework. Vulnerabilities in the platform are fixed quickly through regular updates.
• Performance: the shop benefits from years of performance work in the modern .NET runtime and the ASP.NET Core web server, which handle requests faster and with less memory than the legacy framework.
• Future-proof: current libraries and tools are available again, which speeds up the development of new features.

For users, the shop works exactly as before, on a faster, safer and supported foundation for the years ahead.

The F&O integration synchronizes many entities in a single run, such as articles, prices, discounts and product attachments. When one of them returned an error, the whole synchronization stopped, so unrelated data such as line discounts was not updated either.

A failing entity is now logged and skipped, and the synchronization continues with the rest. In addition, product images are synchronized in a step of their own, separate from article data. This keeps the regular article synchronization lighter and allows images to be refreshed on a separate schedule.

The Microsoft Dynamics 365 Finance & Operations integration now runs on a rebuilt engine (V2), designed for large environments with several companies. It synchronizes faster, recovers better from errors and gives administrators more control. This sprint's improvements include:

• Who ordered: orders are linked to the ordering contact, matched per customer and company, and the email address of the person who placed the order is added to the order header.
• Customers: new customers are created reliably, also when no sales tax group or payment condition is set, and the customer's language is passed on with customers and orders.
• Faster, more stable synchronization: better performance and stability for large data sets, with integrity checks and clearer feedback during a run.
• Safe operation: the integration cannot run twice at the same time, long runs can be stopped cleanly, and it can run unattended in headless mode.

Customers and sales representatives can request a quote from the basket. The quote request form asked them to enter all customer details again, even though these were already known for the logged-in account.

The form is now filled in automatically with the details of the logged-in account. When another user logs in, the stored form is cleared, so the details of a previous user are never shown.

With drop shipment to alternative delivery addresses enabled (DropShipmentOnAlternativeAddress), choosing an alternative address changes the shipping method and its costs. When a customer then went back and chose their primary address after all, the drop shipment costs remained.

The shipping method now follows the address that is actually selected, so customers always see the shipping costs that apply.

The Exact Online integration can select which accounts are exported to the webshop based on their account classifications (WebshopCustomerAccountClassifications). Classification codes were compared case-sensitively, so a small difference in capitalization could leave customers out of the webshop.

Classification codes are now matched regardless of upper or lower case, which makes the configuration less error-prone.

Custom order fields let customers add information such as a reference or an instruction to an order line. When the name of such a field contained a space, the order XML for the ERP could not be created.

Field names are now converted to valid names in the order XML, with spaces replaced by underscores, so these orders are processed normally. Keep this in mind when mapping custom order fields in the ERP.

The order confirmation is often the first document a customer keeps after ordering. The new Postmark template OrderConfirmationWithImage shows a product image next to every order line, so customers can check their order at a glance. It also lists the VAT amount for each VAT rate.

Order emails received further improvements:

• The requested delivery date is now also available in full, including the weekday (for example Monday 1 June 2026), through the new PreferredDeliveryDateFormatted field. Useful for teams that sort incoming orders by delivery day.
• When a dedicated shop manager address is set for order confirmations, the blind copy goes only to that address. Without one, the general shop manager address is used.

Development of Vendisto-NG, the next generation of the Vendisto back office, continued at full pace. This sprint added three modules:

• Static lists: create and edit product lists, with multilingual content and autosuggest for articles, article groups and categories.
• Redirects: create, edit and delete redirects, including redirect types that point to an item rather than a URL.
• Content blocks: manage reusable content blocks, with quick switching between language versions.

Overviews also gained copy buttons and a shared language filter. Behind the scenes, static lists are now stored in SQL first and then synchronized, for more robust data handling.

Spare parts catalogues help customers find the right components for an assembled product. In assortments that work with authorization profiles, spare parts did not yet take those profiles into account.

Assembled products and their spare parts now respect customer authorizations. An assembled product is only shown when the customer is authorized for every part it contains, and the filter options follow the same rule. Customers see exactly the products they are allowed to order.

The Shoxl Scan App lets users order by scanning products, for example in a warehouse or on site. Many professional environments use rugged Zebra devices with a built-in hardware scanner.

The Scan App now integrates with Zebra DataWedge and recognizes scans from the built-in scanner directly. Each scan is handled as a search, so the scanned product appears immediately, ready to be ordered, without typing.

With VIES validation enabled (EnableViesCheck), VAT numbers entered at checkout or registration are checked against the European VIES service. Customers from outside the EU, for example from Switzerland, could get stuck: their valid VAT number was rejected because VIES does not cover their country.

The check now only applies to countries that take part in VIES. Customers from other countries can register and check out with their own VAT number. Northern Ireland (XI) has been added to the list, which can be adjusted per environment with the shoxlpro:ViesCountries setting.

Customers paying online through Pay. were sent to the payment page in a fixed language, regardless of the language they used in the webshop.

The payment page now opens in the language the customer selected in the webshop, so international customers complete their payment in a language they understand.

The availability check (ATP) tells customers when a product that is not in stock is expected. Some Microsoft Dynamics 365 Finance & Operations configurations provide an expected delivery date without available quantities.

With the new setting DateOnlyMode, the F&O availability check works with the date alone. When F&O reports a future date, customers see it as the expected delivery date, for example Expected delivery date: 22-6-2026. When the date is today, no future delivery is shown. The standard behavior remains available for all other configurations.

Order lists can be imported into Vendisto from Excel. When a file contained the same article number twice, the import stopped with an unknown error that did not say what was wrong.

The import now validates the file and reports exactly which rows contain a duplicate article number. Quantities are checked as well: they must be empty or a valid, non-negative number. Errors can be corrected in the file and the import run again right away.

Repeated imports of large order lists no longer stop with an error, and they finish considerably faster.

After checkout, the webshop hands each order over to Vendisto for further processing. When that processing took longer than usual, the webshop could time out, leaving customers with the impression that their order had failed while it had in fact been received.

The webshop now confirms the order as soon as it has been registered, while Vendisto completes the processing in the background. Customers get their confirmation right away.

Bundles combine a main product with its components. In combination with a minimum order quantity, the components could be multiplied twice, for example 8 × 8 = 64 pieces instead of 8, both in the basket and in order lists.

Minimum order quantities are now applied once, so components follow the quantity of the main product. Order lists include the component prices in the bundle total, and bundles can be ordered without issues when HS codes are configured for customs data (HsCodePropertyId).

A series of improvements makes everyday ordering run more smoothly:

• The Next step button in the basket is enabled right after typing a new quantity, not only after using the plus and minus buttons.
• Quantity fields show their default value on page load in all overviews.
• On mobile, adding a complete order list to the basket updates the basket count and totals immediately.
• On mobile, the order history shows its column labels in the customer's language.
• Custom order fields on the article page validate their input correctly, also when the field is required.

Article group pages can combine the article selection wizard, the order grid and selectable product options. When one of these had nothing to show for a product, an empty box could still appear, sometimes together with a basket or login button belonging to the selection wizard.

These elements are now only shown when they contain items. Pages look cleaner, and customers are not distracted by buttons that lead nowhere.

Product properties can be displayed with an icon instead of a text label, with the label appearing on hover. For properties placed in a property category, the icon could be missing, leaving only the text.

Icons now appear for these properties as well, so product specifications look consistent across the page.

Some products should only be ordered in limited quantities: scarce or allocated stock, items reserved for projects, or articles where unusually large orders call for a personal conversation.

Shoxl now supports a maximum order quantity per article, next to the existing minimum order quantity. When a customer enters a higher quantity, the webshop does not accept it and shows a clear message stating the maximum that applies. If the maximum is lowered later, quantities already in baskets are brought back within the new limit automatically.

The maximum is supplied in the new MaximumOrderQuantity field of the gross price import. For webshops connected to Microsoft Dynamics 365 Finance & Operations, it is retrieved directly from the ERP.

Last sprint introduced selectable property values, letting customers choose predefined options such as color, material or finish for configurable products. This sprint adds the controls needed to use them in daily ordering:

• Required options: a property category can be marked as required, so a product can only be added to the basket once a choice has been made.
• Display types: each category can be presented as single-select, multi-select or dropdown.
• Icons managed in Vendisto: option icons, such as color swatches or material symbols, are maintained as documents in Vendisto.
• Flexible placement: a dedicated layout element positions the options wherever they work best on the page.

Options with inconsistent product data are simply left out instead of interrupting the page, so a single import mistake never blocks ordering.

Each property category is configured in the webshop setting SelectorPropertyConfigurations (display type, icon prefix and suffix, required), and placed on the page with the SelectorProperties layout element.

Synchronizing with Microsoft Dynamics 365 Finance & Operations involves large volumes of data and many individual requests. A short timeout or a brief service interruption on the ERP side could make a sync run fail, after which it had to start over.

The F&O integration now retries requests automatically when a temporary issue occurs. The number of attempts is configurable with RequestRetryCount. Additional safeguards prevent conflicts when several integration processes update data at the same time.

Synchronizations are interrupted far less often, and product, price and order data stays current without manual intervention.

Accessories, alternatives and spare parts are often already linked to products in the ERP. Making those relationships visible in the webshop meant maintaining them a second time in Vendisto.

Shoxl now imports product relationships directly from Microsoft Dynamics 365 Finance & Operations, through both full and incremental synchronization. Relationships maintained in F&O appear in the webshop as related articles, without duplicate data entry.

As part of this work, the related article import in Vendisto has been revised to process data in batches, which makes it up to ten times faster for large assortments.

Products sell better with more than one picture, yet the F&O integration only transferred the default product image.

All images marked as product images in Microsoft Dynamics 365 Finance & Operations are now exported to Vendisto and the webshop. The default image always comes first, followed by the additional images in their sequence order where one is set.

Image management stays in the ERP, while customers get a complete visual impression of each product.

With price list authorization, customers only see the products on their own price lists. Those products still have to be imported from Exact Online first, which is normally controlled by the Webshop checkbox on the item.

Organizations that also use this checkbox to decide what appears in their public assortment faced a dilemma: marking customer-specific items for import would also make them visible to everyone else.

With the new setting EnableIsWebshopItem set to false, the Exact Online import ignores the Webshop checkbox. All articles that meet the standard import rules are then imported: active, with a VAT code, and part of the configured article group or assortment. Which customer sees which product is determined entirely by their price lists.

Alongside this sprint's webshop and integration work, a significant part of our development capacity went into Vendisto-NG, the next generation of the Vendisto back office. Built on .NET 10, it brings catalogue, sales, content and integration management together in one modern, consistent interface.

This sprint added:

• Knowledge base module: manage knowledge articles and their categories, including publication dates, starting from a dedicated knowledge home page.
• News home page: an overview of the news module with shortcuts to filtered lists of news items, plus search in the news overview.
• Personal theme: each user chooses a preferred theme in their profile.
• Refreshed look: a new visual style and logo, and a redesigned login page with texts in English and Dutch.
• More paging options in overview grids, for working through large lists faster.

When customers ship to an alternative delivery address, the checkout can ask for contact details for that address. These fields came as one fixed block: name, email address and phone number were either all shown and required, or not shown at all.

Each field can now be configured separately, with its own choice for visible and required. A webshop can, for example, ask for a contact name and phone number for the delivery while leaving the email address optional. The separate initials field has been removed to keep the form short.

The new settings are ShowAlternativeDeliveryAddressName, ShowAlternativeDeliveryAddressEmail and ShowAlternativeDeliveryAddressPhone, each with a matching required setting such as AlternativeDeliveryAddressPhoneRequired. Existing configurations based on ShowPersonalDetailFields keep working as they are.

In webshops that use the Calculate Order flow (setting LimitOrderCalculation), prices and taxes are retrieved from the ERP on request rather than with every basket change. For cross-border B2B orders that qualify for VAT reverse charge, VAT could still be added when the order was placed, even though the ERP calculation had returned zero VAT.

The reverse charge determined by the ERP is now applied all the way through to the placed order. Customers see the correct amount, can pay it directly, and the order is consistent with the VAT treatment in the ERP.

Descriptions of images, icons, documents and media tell customers what they are looking at or downloading. The standard article export did not include them, so teams relied on the advanced export, where document descriptions could also come out empty and had to be restored by hand after every import.

The standard Excel export now contains description columns for all asset types, on both article and article group level. The advanced export once again includes document descriptions in full.

Assets and their descriptions can now be maintained in a single export-and-import round.

Order numbers in the order history were sorted as text, so order 1000 could appear before order 999. For customers with many orders, that made recent or specific orders harder to find.

Numeric order numbers are now sorted by value, both ascending and descending, giving customers and sales representatives an order history that reads the way they expect.

Searching the order history for a specific order number could, in some webshops, load a copy of the webshop inside the results area instead of the matching order.

Order number search now returns the matching orders directly, making it quick to look up an order when following up on a delivery or invoice question.

The order grid on the article group page lists a product's variants, for example per color, so customers can order several at once. The grid is sorted by a configurable property such as a color sequence number. Variants without a value for that property could disappear from the grid, which meant customers could not order them.

Every variant is now shown. Variants without a sort value are placed after the sorted ones, and adding a value in Vendisto determines their exact position. The sorting property is set in OrderGrid.SortingProperty.

When a page in a product overview contained just one product, typically the last page of a category, visitors were taken straight to that product instead of seeing the overview page. For anyone browsing page by page, that was confusing.

Overview pages with a single product are now displayed like every other page, so customers keep their place in the category and continue browsing from there.

Depending on the webshop configuration, a few situations could make ordering less smooth than it should be:

• the quantity field could start at 0 instead of 1;
• quantity fields and order buttons could be missing in certain product lists;
• for products ordered per package, the number of packages could be replaced by the number of pieces per package;
• a sold out message could appear in the basket while all products were available.

Each of these has been resolved, so customers move from product to basket to checkout without unexpected quantities or messages.

Long product descriptions are shortened with a Read more button. When a description ended with an empty paragraph, the button could end up in the hidden part of the text, so customers could not open the full description.

The button now stays visible however the description's formatting ends, keeping the complete text one click away.

Removing a product from an order list did not always take effect, leaving outdated items in lists that customers use for repeat orders.

Products can now be removed from order lists reliably, so every list reflects what the customer actually wants to reorder.

Authorization profiles can be created automatically by both the article import and the customer import. When a profile code ended with a space, the two imports interpreted it differently, which could stop a full customer import with an error.

Both imports now handle authorization profile codes in the same way, so customer imports run to completion, also when codes contain trailing spaces.

Order confirmation emails showed the requested delivery date together with a technical time value. The date is now presented in a clean, readable format, such as 14 May 2026.

Shoxl now supports a new type of product property for configurable and custom-made products: list-based property values.

Previously, product properties in Vendisto were always stored as free-text string values. This worked well for informational attributes, but offered limited control when users needed to actively select a predefined option during product configuration.

With this enhancement, properties can now be configured as a single-select list, allowing users to choose from predefined values directly on the article page.

Examples include:

• Selecting a specific color from an approved list of available colors
• Choosing a material type such as aluminum, stainless steel, or plastic
• Selecting a finish like matte, gloss, or brushed
• Choosing a predefined cable length or diameter for custom assemblies
• Selecting a left/right orientation for configurable components

The selected value is stored as part of the configured product and can be transferred directly to the ERP system as part of the order line information.

This enables ERP-driven production, fulfillment, or customization processes to receive structured and validated configuration input instead of relying on manually entered free-text values.

A new webshop setting, SkipMinimumOrderValueForRepresentatives, has been introduced to provide more flexibility for internal sales representatives and account managers.

When this setting is enabled, representatives can place orders without being restricted by the configured minimum order value in the basket. If disabled, the standard minimum order validation remains active.

This is particularly useful in B2B environments where representatives place orders on behalf of customers and need the flexibility to handle exceptions that would normally not be allowed through the self-service channel.

Typical scenarios include:

• Creating a small replacement or warranty order without requiring the customer to meet the standard order threshold
• Processing urgent backorders for missing items from a previous shipment
• Entering sample or test orders during commercial discussions
• Supporting strategic customers with exceptional service orders

This allows organizations to maintain strict minimum order policies for regular webshop users, while still giving internal sales teams the operational flexibility needed for customer-specific situations.

The Order List module in Shoxl has been extended with support for saving predefined quantities as part of an order list.

Users can already create and manage multiple order lists within the My Account environment and quickly add all or selected products from those lists to the basket. With this enhancement, the configured quantities are now stored together with the products.

Previously, products added from an order list were always inserted with a default quantity of 1, requiring users to manually adjust quantities afterward.

With the new behavior, users can optionally save the exact basket composition, including quantities, and reuse it for future reorders.

This is particularly useful for customers who regularly place recurring replenishment orders with fixed quantities.

For example, a maintenance department may create a monthly replenishment list containing:

• 50 pairs of safety gloves
• 20 cleaning cartridges
• 10 replacement filters
• 5 liters of industrial lubricant

Instead of manually adjusting quantities during every reorder, the complete predefined order can now be added to the basket in a single action.

This streamlines repeat ordering processes and reduces manual input for frequently ordered assortments.

Shoxl supports advanced bundle configuration scenarios through the Article Selection Wizard (ASW) combined with configurable component relationships.

In this setup, users first select the main product variant on the article group page. The selected article then acts as the foundation for a configurable bundle.

Based on configured “is component of” relationships, the platform automatically loads all compatible component products linked to the selected base article.

These component structures support multiple configuration scenarios, including:

• Mandatory components that must always be included
• Optional add-ons that users can choose to include
• Alternative component groups where one option must be selected from multiple compatible products

This makes it possible to configure complex product combinations directly from a single flow.

A typical example is the configuration of an industrial workstation:

• The user first selects the workstation variant based on dimensions and load capacity
• Compatible accessories are then loaded dynamically, such as monitor arms, power modules, cable trays, or drawer units
• Some accessories are mandatory, while others are optional or selectable from multiple alternatives

The configured solution is presented as a single bundle within the basket for a streamlined user experience. Internally, however, the bundle is translated into separate order lines when transmitted to ERP systems that do not support native bundle structures.

As part of this functionality, an issue has been resolved where ASW could add incorrect bundle components when no valid base article had yet been explicitly selected.

The component flow has now been adjusted so that components are only activated and linked after a confirmed ASW article selection is completed.

This ensures that only components compatible with the selected base product become part of the final configuration.

Shoxl supports configurable product bundles where a main product can automatically include linked component articles through configured “is component of” relationships.

These component relationships can be used for mandatory parts, optional add-ons, or selectable alternatives that together form a complete commercial or technical solution.

When required components are configured, their quantities are often directly tied to the quantity of the main product.

For example:

• A workstation may always require one mounting kit per desk
• An industrial machine may require a mandatory safety module for each configured unit
• A configurable lighting system may require one driver per selected fixture

An issue existed where the quantity of required components did not automatically stay aligned with the quantity of the main product after basket quantity changes.

This has been corrected. Required component quantities are now automatically synchronized with the quantity of the primary article in the basket.

This prevents incomplete bundle quantities and ensures the generated order remains technically and commercially consistent.

The Product API now supports token-based authentication for server-to-server product import scenarios.

This enables external tools that do not support OAuth2 to trigger product imports directly by sending a configured Bearer token in the authorization header.

A typical example is an integration with Channable, where product data can be exported from Channable and sent directly to the Product API using a static token-based credential.

The token is configured in the webshop security settings and can be linked to a default webshop user for auditing and logging purposes. An expiration date is required, and regular token rotation is recommended because the token functions as a long-lived shared secret.

If no Bearer token is provided, existing authentication flows continue to work unchanged.

Shoxl supports configurable product relationships that can be used to build advanced product structures, bundles, and configuration flows.

Two commonly used relationship types within these scenarios are Component and Supplement.

These relationship types are used to define how products relate to each other, for example:

• Mandatory or optional bundle components
• Accessories linked to a main product
• Cross-sell or add-on products
• Supplementary products that should be offered together with a primary article

Previously, all available configurable relationship types were always shown within product data management screens, even in environments where certain relationship types were not used at all.

This could lead to unnecessary complexity and confusion for product data administrators when configuring product relationships.

With this improvement, relationship types such as Component and Supplement can now be individually activated or deactivated.

Inactive relationship types are hidden from the interface, allowing organizations to simplify the product management experience and expose only the relationship structures that are actually relevant for their implementation.

The Article XML bulk import has been extended with support for importing and synchronizing DataPool fields.

This allows external product data sources to populate shop content such as product descriptions, titles, specifications, and other enriched article information directly through the XML import flow.

At the same time, Vendisto users can now selectively override imported DataPool content with custom webshop-specific values.

This creates a flexible setup where centralized product information remains synchronized from the external data source, while specific webshop content can still be tailored locally when needed.

A common example is SEO optimization.

An organization may use a centralized DataPool description such as:

• “Industrial cordless drill with lithium-ion battery and ergonomic grip.”

For a specific webshop or market, this description can then be overridden with a more SEO-focused variant such as:

• “Professional cordless drill for construction and installation projects, including high-capacity lithium battery and fast charger.”

This allows organizations to:

• Optimize product titles and descriptions for search engines
• Create market-specific or channel-specific content variations
• Add commercial positioning without changing the central product source
• Maintain centralized product synchronization while preserving local webshop flexibility

In addition to the new import capabilities, an issue affecting the synchronization of DataPool fields has also been resolved.

For Exact Online integrations, Shoxl now validates whether synchronized articles are available in the warehouse that is configured for webshop order processing.

Only articles that exist in the linked webshop warehouse are now made available in Vendisto and the webshop.

This improvement addresses a practical integration constraint within Exact Online. When orders are submitted through the Exact Online API, a warehouse must always be supplied as part of the order creation process.

If an article does not exist within that warehouse, Exact Online rejects the order creation request.

Previously, articles could still become visible in the webshop even when they were not available in the configured webshop warehouse, potentially leading to failed order exports.

With this change, only articles that can actually be processed through the configured operational warehouse are exposed online.

This is particularly relevant in environments where:

• Multiple warehouses are used for different sales channels
• Certain warehouses are reserved for physical stores or internal logistics
• The webshop operates from a dedicated fulfillment warehouse
• Specific assortments are intentionally limited to certain warehouse locations

This prevents invalid webshop orders and keeps the online assortment aligned with the warehouse structure used in Exact Online order processing.

An issue has been resolved in the advanced order history overview where filtering on delivery date did not return the expected results.

Due to an incorrect field mapping, the filter used the wrong underlying data field whenever users searched or filtered by delivery date.

This could lead to incomplete or incorrect order selections within the order history environment.

The filtering logic has been corrected so delivery date filters now properly match the intended delivery date information.

This is particularly relevant for users who rely on delivery date searches to:

• Review upcoming deliveries
• Track delayed or planned shipments
• Verify historical delivery schedules
• Locate orders for operational or customer service follow-up

Shoxl supports quantity rules where products must be ordered in predefined multiples, often referred to as AdditionQuantity rules.

This is commonly used for products that can only be supplied in fixed packaging units, production batches, or transport quantities.

Examples include:

• Ordering cable reels in multiples of 100 meters
• Purchasing tiles per full box instead of per piece
• Supplying industrial fasteners in packaging units of 250
• Ordering liquids per container size

An issue existed where automatic quantity corrections could reduce quantities to a lower valid multiple instead of increasing them to the next allowed quantity.

For example:

• Required order multiple: 300
• User quantity: 576
• Previous behavior: quantity reduced to 300
• New behavior: quantity automatically increased to 600

The adjustment logic has been changed so quantities are now rounded upward to the next valid order multiple instead of downward.

This prevents unintended quantity reductions and keeps basket quantities aligned with the configured commercial ordering rules.

Shoxl supports real-time ERP-based order calculations within the basket, allowing pricing, discounts, stock information, and commercial conditions to be retrieved directly from the ERP system while the basket is being updated.

In some ERP environments, however, real-time calculations may not be sufficiently fast for continuous basket updates.

For these situations, Shoxl supports a separate “Calculate Order” workflow.

Instead of recalculating the basket after every quantity change, users can first compose their basket and then manually trigger the ERP pricing and order validation request using a dedicated calculation button.

This approach is particularly useful in environments with:

• Complex ERP pricing structures
• Large baskets
• Slow ERP response times
• Heavy customer-specific pricing calculations

An issue existed where volume discount pricing was not correctly refreshed in the basket after quantity increases when the manual “Calculate Order” flow was used.

As a result, updated quantity-based discount tiers were not always shown immediately after recalculation.

This has been corrected, ensuring that volume discount prices are now properly recalculated and displayed when basket pricing is refreshed through the Calculate Order process.

Shoxl supports a second image on hover display option, where product images automatically switch to an alternative image when users move the mouse over the product image.

This is commonly used to show an additional product angle, detail view, lifestyle image, or variant-specific image without requiring users to open the product page.

This behavior already worked on article group level, where multiple product variants are presented together.

An issue existed where the same hover behavior did not work correctly on individual article level when variant images were used.

This has been corrected. The DisplaySecondImageOnHover setting now also works for variant images on article pages.

Article exports can now be limited to specific parts of the assortment instead of always exporting the complete article catalog.

A new “Articles to Export” selection has been added to the article export dialog, allowing exports to be generated for:

• All articles
• A selected classification structure

When exporting by classification, users can navigate the full classification hierarchy and optionally include unclassified articles as part of the export.

This improvement is particularly relevant for environments with very large assortments containing hundreds of thousands of articles, where generating a complete export could become unnecessarily time-consuming when only a subset of the catalog was needed.

The new export flow makes it easier to work with targeted subsets for import, maintenance, enrichment, or external processing scenarios.

Free shipping thresholds can now be configured individually per customer instead of using a single global threshold for the entire shop.

A new configuration block has been added to the Vendisto Customer UI, allowing customer-specific franco delivery limits to be maintained directly per customer profile.

This makes it possible to support commercial agreements such as:

• Different free shipping thresholds per customer
• Always-free shipping for selected customers
• Shipping costs only for specific customer groups

The functionality is particularly relevant for B2B environments where delivery conditions are part of negotiated customer agreements.

This extension also aligns Shoxl more closely with ERP-driven commercial models by supporting customer-specific delivery cost structures for ERP environments where this functionality is not available natively.

Orders can now be placed using only a visitation address when no separate delivery or invoice addresses are available in Exact Online.

Previously, the Shoxl Exact integration could automatically generate fallback delivery and invoice addresses for customers that only had a visitation address configured. This could lead to unnecessary or unintended address creation within Exact Online.

The integration behavior has been updated so that fallback addresses are no longer automatically created during synchronization or ordering flows.

When separate invoice or delivery addresses are required, these addresses can be explicitly maintained in Exact Online. Shoxl will automatically recognize and use them once available.

This results in cleaner address synchronization behavior and gives customers more direct control over how address structures are managed inside the ERP environment.

Shops and portals with only a single top-level classification can now automatically skip the initial classification overview screen.

When a visitor logs in to a shop containing only one classification tile, the platform will immediately open the underlying article group overview instead of first showing a classification selection screen.

This is particularly useful for smaller assortments where users primarily want direct access to the available products instead of navigating through an additional intermediate step.

Previously, similar behavior could only be achieved through homepage redirects. The navigation flow is now handled automatically by the platform itself.

GTIN and Type Number information can now be added independently within article page layouts.

Previously, both values were combined into a single layout block. This meant that hiding either the GTIN or the Type Number often required additional CSS customization or template adjustments.

The layout structure has now been split into two separate layout elements, allowing implementations to independently position, display, or omit:

• Article GTIN
• Article Type Number

This provides more flexibility when composing product detail layouts and simplifies implementations where only one of the two values should be shown.

External integrations and browser-based connections to the Vendisto API now work correctly again after restoring CORS support.

A configuration issue could previously block requests originating from external environments or frontend applications due to missing or incorrect CORS handling.

The API configuration has been updated to properly allow supported cross-origin requests again.

Additional improvements have also been made to login feedback handling. Authentication-related error messages are now better differentiated, making it easier to identify issues that are unrelated to invalid credentials.

Article imports from Excel will no longer fail due to GTIN validation errors.

The GTIN validation step has been removed from the article Excel import process after repeated situations where valid import scenarios were blocked by strict GTIN validation behavior.

This change makes it easier to import and maintain article data originating from external systems, supplier files, or ERP exports where GTIN values may be incomplete, differently formatted, or not consistently maintained.

It is also common practice in parts of the B2B market to use internally constructed or customer-specific GTIN values that do not formally pass GTIN checksum validation, despite being operationally valid within the business process.

The import process can now continue without rejecting articles solely because of GTIN validation issues.

Removed assembled product structures are now correctly cleaned up during full ERP cache imports.

Previously, situations could occur where deleted or obsolete assembled product records remained present in the ERP cache after a full import cycle.

The import cleanup logic has been corrected so that removed assembled products and related bill-of-material structures are now properly deleted when they no longer exist in the source data.

This prevents outdated assembled product relationships from remaining active after assortment or product structure changes in the ERP environment.

Article group imports and exports now support a dedicated Article Group ID column.

Previously, article group synchronization depended primarily on the article group title. Renaming an existing article group could therefore lead to duplicate group creation during import scenarios.

With the introduction of the optional Article Group ID field, article groups can now be matched using a stable identifier instead of relying solely on the displayed title.

This makes it possible to:

• Rename existing article groups without creating duplicates
• Maintain stable references during import and export flows
• Manage assortments more safely across repeated synchronization cycles

The new field remains optional to preserve compatibility with existing import structures and legacy assortment files.

Asset descriptions linked to article groups are now correctly imported during article group import processes.

Previously, article group imports could successfully import the related assets while failing to apply the configured asset description metadata.

The import handling has been corrected so that asset descriptions are now properly stored and synchronized together with the imported article group assets.

Several improvements have been made to the handling of product identification data during article group imports and article Excel exports.

SupplierGLN and ManufacturerGLN values are now correctly processed during article group imports. Previously, these fields could be omitted during import, causing supplier and manufacturer identification data to remain unavailable after synchronization.

In addition, the Type Number field is now correctly included in article Excel exports. The column could previously be missing from exported datasets, limiting its use in external processing and product identification workflows.

These changes improve consistency of product identification data across import, export, and synchronization flows.

The representative account overview will now display correctly when the Message Center is enabled in the webshop.

This overview is used by representatives to access and switch between the customer accounts they are authorized to manage, allowing them to log in as a customer and place orders within the webshop on behalf of that customer.

Previously, enabling the Message Center could cause layout and rendering issues within this account selection overview after login, resulting in a visually broken or unstructured page.

The interaction between the Message Center components and the representative account selection flow has now been corrected so that both features function correctly together within the same webshop environment.

The unread message counter in the Message Center is now updated correctly when unread messages are archived or marked as read.

Previously, the unread message indication could remain incorrect after changing the status of a message, causing the displayed unread count to differ from the actual unread messages remaining in the Message Center.

The counter update logic has been corrected so that unread message totals are now refreshed immediately after message status changes.

Article exports to Microsoft Dynamics 365 Finance & Operations can now be limited to a specific set of product properties and attributes.

A new ArticlePropertyAttributes setting has been added to the Shoxl Finance & Operations integration, allowing implementations to define exactly which attributes should be included in the export.

Previously, all available article properties could be included during export, even in scenarios where only a limited subset was required by the ERP integration.

This makes it possible to reduce export payload size and avoid transferring unnecessary attribute data, particularly in environments with large product datasets or extensive property structures.

Newly imported article header labels from the ERP system will now correctly appear in the shop after import.

Under specific import scenarios, newly introduced article headers or property labels could be imported successfully into the platform while remaining unavailable in the webshop presentation layer.

The import and synchronization flow has been corrected so that newly added article header labels are now properly created and made available within the shop environment immediately after import.

We introduced a new Custom Content Blocks module in Vendisto, enabling shop owners to manage reusable content directly from the platform without requiring layout or code changes.

This functionality is designed for content that appears across fixed areas in the shop, such as:

• Footer address information
• Header notifications or maintenance messages
• Reusable informational content
• Temporary promotional or service announcements

Each Custom Content Block contains:

• A unique tag used for placement inside the shop
• Fully translatable content
• Optional publication and archive dates
• Reusable HTML content that can appear in multiple locations simultaneously

Custom Content Blocks can be inserted in two different ways:

• Directly inside HTML content using the new custom tagging mechanism
• As standalone elements within the shop layout configuration

This creates a more flexible content management flow where functional or informational content can be maintained independently from the technical shop implementation.

The module also supports scheduled visibility through publication and archive dates, allowing content to automatically appear or disappear at predefined moments.

Internally, the content blocks are synchronized to the webshop settings structure in RavenDB and rendered language-specific based on the active shop language.

The Spare Parts page now uses a dedicated Spare Parts PreFilter component, replacing the existing generic PreFilter implementation.

The previous component was not sufficiently flexible for Spare Parts scenarios involving dependent filters and accumulated product properties. In some situations, subfilters could be skipped or hidden when a configured property was not immediately available or when filter configurations were processed in a specific order.

The new component removes this dependency on configuration order. Available subfilters are now evaluated independently, ensuring that valid filter options remain accessible whenever matching assembled product data exists.

The implementation also improves handling of conditional subfilters. Filters that are not relevant for the current selection remain hidden until a selected product path makes them applicable.

To support this behavior, a new indexing structure was introduced for filtering on accumulated properties of assembled products.

This improvement is particularly relevant for Spare Parts environments with layered product structures, where multiple dependent properties and variant combinations are used to guide users toward the correct replacement parts.

The search functionality has been improved to better handle searches based on article numbers and manufacturer article numbers, even when formatting differs from the stored value.

Previously, searches could produce inconsistent results when users omitted spaces or special characters that were present in the original article number. This was particularly relevant for technical products and spare parts where article numbers are often entered manually.

Search indexing and result prioritization have been updated so that normalized article numbers are matched consistently across both autocomplete and full search results.

For example, the manufacturer article number 6205/C3 will now correctly return the intended product as the top result for all of the following search inputs:

• 6205/C3
• 6205C3
• 6205 C3

The improvements apply to both autocomplete suggestions and the search results page, ensuring that users can find products regardless of whether separators, spaces, or formatting characters are included in the search query.

The ShoxlRest GetProductInformations endpoint has been extended with support for MinimumOrderQuantity and AdditionQuantity.

This makes it possible to expose customer-specific ordering constraints directly through the product information response. The functionality supports scenarios where different customer groups require different minimum purchase quantities or fixed ordering increments for the same product.

For example, a product can now enforce:

• A minimum order quantity of 12 units
• Ordering only in increments of 6 units
• Different quantity rules depending on the assigned customer group or pricelist

The quantities are returned directly within the product information payload, allowing external integrations and storefront logic to apply the correct ordering behavior during product display, basket validation, and checkout flows.

This functionality is particularly relevant for ERP-driven B2B environments where packaging units, wholesale quantities, or customer-specific agreements determine how products may be ordered.

The basket and checkout totals overview can now display product-level discounts separately from general order discounts and voucher reductions.

A new layout element has been introduced that shows the combined item-level discount amount applied across all order lines in the basket.

This makes it possible to clearly distinguish between:

• Discounts applied directly to products
• Voucher-based discounts
• General order-level discount calculations

The displayed amount is based on the TotalDiscountExclVat value returned by the CalculateOrder response and only includes discounts applied at article level.

This is particularly relevant for B2B pricing scenarios where customer-specific product discounts, net pricing agreements, and line-level discount structures are used alongside separate promotional or order-wide discount mechanisms.

Order-related information can now be transferred to Exact Online order line remarks in multiple configurable ways.

A new setting, OrderLineNotesMode, has been added to the Exact Online Batch Interface. This setting controls how the Notes/Remarks field on Exact Online order lines is populated during order export.

This makes it possible to include additional context directly on individual order lines, even in scenarios where the information originally exists at order level.

The following modes are available:

• None — No mapping is applied to the order line Notes field. Existing integrations remain unchanged.
• Comments — The order header comment is copied to the Notes field of every exported order line.
• CustomOrderFields — All configured Custom OrderFields are added to the Notes field of every order line using a Name: Value structure.

This is particularly useful for integrations where operational information, references, delivery instructions, project identifiers, or custom checkout fields must remain visible at line level inside Exact Online after order synchronization.

Form submissions can now be filtered more accurately based on the calculated reCAPTCHA risk score.

A configurable reCAPTCHA threshold has been added, allowing shops to define when a submission should be accepted or blocked based on the returned Google reCAPTCHA score.

Previously, submissions with low trust scores could still pass validation because no configurable threshold was available within the implementation.

With this improvement, shops can now actively control how strict the validation should be for contact forms and other protected submission flows.

Additional logging has also been added to provide better visibility into:

• The received reCAPTCHA score
• Why a submission was accepted or rejected
• Validation and scoring behavior during troubleshooting

This makes it easier to tune spam protection behavior in environments where automated submissions, bot traffic, or low-confidence form activity must be filtered more aggressively.

The QuoteForm can now be configured to support different field requirements per shop implementation.

This makes it possible to determine exactly which fields are shown in the quote request flow and which of those fields are mandatory for submission.

Previously, the QuoteForm used a fixed structure with limited flexibility around required input fields. With this improvement, shops can tailor the quote request process to their own business requirements and data collection needs.

Examples of configurable behavior include:

• Making phone number fields optional or mandatory
• Showing or hiding company-related fields
• Controlling whether newsletter opt-in is displayed
• Reducing the number of required fields for simpler quote flows

The configuration supports multiple field types including textboxes, checkboxes, radio buttons, and multiline comment fields. Field visibility and validation requirements are configured through the QuoteForm settings structure.

Component options can now be displayed as selectable lists instead of only dropdown menus.

Previously, component selection exclusively used dropdown fields for each component relation type. This worked well for smaller selections, but became less practical in scenarios with many component options or visually distinguishable variants.

The new implementation introduces a list view mode for component selection, aligned with the behavior already available in the Article Selection Wizard.

When enabled, component options can be presented as a visual list where each available value may include:

• An icon or image
• A directly visible option label
• Property information shown through tooltips

This makes it easier to compare and select component variants without repeatedly opening dropdown menus, particularly for configurable products with multiple component dimensions or visually recognizable options.

Outdated price detail information is now automatically removed from the shop’s RavenDB performance database during synchronization.

Cleanup mechanisms already existed for articles, article groups, categories, and assets that were no longer active or available in Vendisto. However, obsolete price detail documents could still remain present in the RavenDB cache in certain scenarios involving frequent assortment or pricing changes.

The synchronization process between the Vendisto SQL database and the RavenDB performance database has now been extended to include automatic cleanup of outdated price detail records as well.

This prevents old or orphaned pricing information from remaining available in the performance database after pricing changes, assortment updates, or article removals in Vendisto.

Products that are temporarily unavailable can now display upcoming availability dates directly from the connected ERP system.

When the Available-to-Promise (ATP) functionality is enabled, the standard “Out of Stock” indication can be replaced with an ATP action that allows users to retrieve future availability information in real time.

After activation, the shop queries the connected ERP system to retrieve the next expected availability moments and quantities for the selected product.

This allows users to:

• See when new stock is expected to become available
• Determine whether waiting for replenishment is worthwhile
• Make purchasing decisions based on planned incoming stock instead of only current inventory

The ATP functionality is implemented as a configurable layout element and can be used with ERP integrations that provide Available-to-Promise information.

Gross prices exported from Microsoft Dynamics 365 Finance & Operations can now be synchronized using multiple currencies instead of always defaulting to EUR.

A new configuration setting has been added to the integration layer, allowing shops to retrieve and process gross prices in the currency configured within the ERP environment.

Previously, gross price exports defaulted to EUR regardless of the original currency context in Finance & Operations.

This improvement is particularly relevant for international B2B environments where different customer groups, regions, or sales organizations operate with multiple currencies within the same ERP landscape.

New shops now automatically receive a complete and up-to-date set of transactional email templates during creation.

The Shopmanager mail service has been extended to automatically generate the required templates in Postmark, reducing manual setup work and ensuring that newly created shops immediately have the correct email infrastructure available.

Additional improvements have also been made to multilingual email support.

Basic template sets are now available to simplify onboarding of new shop environments, while two-factor authentication emails have been extended with support for additional languages.

This ensures that authentication and transactional communication can be delivered in the language expected by the end user, particularly in multi-language shop environments.

Basket merging after login now correctly validates product quantity rules before combining guest and user baskets.

Previously, situations could occur where products added to a guest basket exceeded configured stock or quantity restrictions after the basket was merged into the user’s existing basket during login.

This specifically affected scenarios involving:

• Minimum order quantities
• Fixed quantity increments
• Maximum allowed quantities
• Stock-based quantity validation

The basket merge process now validates and adjusts merged quantities before the final basket is created, preventing invalid combined quantities from triggering basket or checkout errors after login.

This is particularly relevant for B2B shops where products are frequently sold in fixed packaging units, order multiples, or quantity-controlled assortments.

Customers using NetPriceFiltering will no longer see incorrect “Excl. Tax” labels in the product price filters.

In specific situations following a RavenDB database and index upgrade, the price filter configuration could display outdated or incorrect tax-related labeling for customers working with inclusive tax pricing logic.

The filter behavior and related index handling have been corrected so that the displayed price filter labels now correctly align with the active pricing configuration used in the shop.

This prevents confusion in environments where customers filter products based on gross pricing instead of excluding VAT calculations.

Classification pages without a directly assigned image can now automatically display an image originating from their underlying classification structure.

Previously, parent classifications without their own image could remain without visual representation, even when suitable images were available on underlying child classifications.

The synchronization and image resolution logic has been updated so that classification nodes can inherit images from underlying classifications when no direct image is configured on the current level.

This ensures that category structures retain visual consistency even when images are only maintained deeper within the classification hierarchy.

Invalid delivery dates can no longer be selected within order flows that use the delivery scheme extension.

Under specific interaction sequences during checkout, it was previously possible to bypass delivery date restrictions and select a date that was not allowed according to the configured delivery scheme.

The validation flow has been corrected so that delivery date availability rules are consistently enforced throughout the complete ordering process.

This ensures that users can only finalize orders using delivery dates that are actually permitted within the configured delivery planning logic.

The shop sends a wide range of transactional emails, including order confirmations, password resets, account activations, 2FA codes, quote requests, and contact form notifications. Until recently, these messages were handled through different technical routes.

Some emails were sent through Vendisto, many were already delivered through Postmark, and a smaller group still relied on SMTP on internal infrastructure. This made the overall setup harder to manage and less consistent in areas such as monitoring, authentication, logging, and template control.

In this sprint, the full email delivery architecture has been consolidated into one centralized flow.

All outgoing transactional emails now pass through a dedicated Email Service. This service acts as the single gateway for email traffic and provides a more uniform way to handle security, validation, and traceability.

All messages are delivered through Postmark. Vendisto is no longer part of the delivery route, and legacy SMTP-based sending has been removed.

With this change, all email templates are now managed in Postmark. Part of this was already in place, but the setup has now been completed for the full transactional email flow. Each environment uses its own dedicated Postmark server. Depending on the subscription, customers can receive access to that environment and manage the content and layout of their own transactional emails directly.

For more advanced scenarios, the architecture also supports webhook-based integrations. This makes it possible to send structured email data to external platforms that can enrich, generate, or distribute communication through their own flows.

The diagram below illustrates the new setup, in which both the Webshop and the Account API route email requests through the central Email API, after which delivery is handled through Postmark.

The underlying request structure also makes the setup easier to extend for new email types and integrations. A request contains the email type, recipients, language, and the data needed by the template.

{ "Type": "AccountTwoFactor", "Recipients": { "To": [ "user@example.com" ] }, "LanguageId": 2057, "Data": { "Username": "TestAccount", "TwoFactorCode": "461595" } }

This functionality is currently available in beta for a selected test group. General availability is planned for Release 71.

The visible behavior for end users remains largely the same, but the underlying setup is now easier to maintain, easier to extend, and better suited for customer-specific email customization.

Order confirmations and quote-related emails were previously only processed through the internal email delivery flow. This limited the ability to integrate these events with external systems that may need to react to order or quote activity.

The Email API now supports sending requests to external endpoints (webhooks) when order or quote emails are generated.

This allows external systems to receive structured data whenever an order confirmation or quote event occurs. The webhook can then be used to trigger additional workflows such as sending emails through external marketing platforms, synchronizing voucher campaigns, or initiating follow-up processes.

By exposing these events through webhooks, the email architecture becomes more flexible and easier to integrate with external communication and automation tools.

The quote checkout previously required a fixed set of fields, making it difficult to adapt the form to different business processes or customer scenarios. In many situations, only minimal information is needed to submit a quote request.

The Quote Checkout page can now be fully configured through the layout settings. This allows the form to be composed using the same layout structure as other configurable pages in the platform.

All available fields can now be individually configured, making it possible to decide which fields are displayed and whether they are required or optional. This enables businesses to create a much more streamlined quote request flow when only limited information is necessary.

The layout configuration supports a wide range of customer data fields, including personal details, company information, delivery and invoice addresses, and contact information. Custom HTML blocks can also be added to structure the form and provide additional instructions or headings.

The following example shows how a field can be rendered in the Quote Checkout layout configuration:

{ "Element": { "Name": "CustomerData_CustomerDeliveryAddress_City", "Properties": { "RenderLabel": true, "IsEditable": true, "ClassName": "form-group col-xs-12 col-sm-12 col-md-6" } } }

By repeating this structure and changing the Name property, additional fields can be added to the form layout. Each field can be individually configured to control visibility, editability, and styling.

This flexible layout approach allows organizations to tailor the quote checkout form to their specific sales processes while maintaining full control over which information is collected from customers.

Order confirmation emails previously included the voucher label rather than the actual voucher code used during checkout. As a result, the exact code entered by the customer was not available in email templates or in downstream integrations.

The order line data sent to the email template system now also includes the voucher code itself. This makes it possible to show the exact code in transactional emails when needed and gives external systems access to the same value.

This creates clearer communication for customers, especially when the entered code is more recognizable than the voucher description or contains meaningful campaign information. It also enables broader integration scenarios in which voucher campaigns are managed outside the platform.

A common setup is to create vouchers in Vendisto, distribute them through an external marketing platform such as Copernica, and then inform that platform once the voucher has been redeemed in the Shoxl shop. This allows campaign distribution and redemption tracking to remain connected across systems.

The diagram below illustrates this flow.

By including the voucher code directly in the email template data, the platform can support this full cycle more effectively: voucher creation, campaign distribution, customer communication, and redemption feedback all remain aligned.

The following simplified example shows how the voucher code can be included in the order line data made available to the email template:

{ "OrderLines": [ { "ProductCode": "SKU-1001", "Description": "Spring promotion discount", "VoucherLabel": "Spring promotion", "VoucherCode": "SPRING10" } ] }

This makes the exact voucher code available not only for email presentation, but also for integrations that need to forward, register, or validate voucher activity across connected systems.

Property categories rendered on an article group page can show the unique values that exist across the available variants. However, when the Article Selection Wizard resulted in a single matching article, these displayed property values were not always updated to reflect the selected article.

This behavior has been fixed. When UpdatepropertiesOverview is enabled, the property overview now updates correctly after a specific article has been selected, including in layout scenarios where this did not work before.

As part of this behavior, the property value is only shown once the article number is known, in line with the existing behavior for article-specific information.

The following example shows the relevant setting:

{ "UpdatepropertiesOverview": true }

On the article group page, an article table can be displayed to list all articles within the group.

When the EnableMatchingPropertiesTransposition setting is enabled, properties that have the same value across all articles are moved out of the table and displayed in the detail section of the article group instead. This helps keep the article table focused on properties that differentiate the variants.

Due to a bug in the implementation of this setting, these matching properties were not shown in the article group detail section as intended.

This issue has been resolved, and matching properties are now correctly transposed and displayed when the feature is enabled.

{ "EnableMatchingPropertiesTransposition": true } 

The shop can be configured to display article properties on the article detail page. When a large number of properties is available, these can be grouped using Property Categories. Each category can be assigned to an article header, allowing properties to be organized into separate tabs on the article detail page.

Property Categories are managed in Vendisto, where their display order can also be defined.

An issue was identified where the configured sort order of Property Categories was not correctly applied on the article detail page. This behavior has been corrected so that the category order defined in Vendisto is now respected in the shop.

The price filter in the shop previously always used prices excluding VAT. This caused inconsistencies in shops where the “Show prices including VAT” setting was enabled, because the filter values did not match the prices displayed in the product listings.

This behavior has been corrected. The price filter now respects the active VAT display setting used in the shop.

• When prices are displayed including VAT, the price filter values and filtering logic use prices including VAT.
• When prices are displayed excluding VAT, the filter continues to use prices excluding VAT.

This applies to both gross and net price filtering.

Adding custom content in the platform often still requires layout changes in Raven, which means customers depend on support or development help for relatively simple content updates.

In this sprint, the management side for reusable Content Blocks has been introduced in Vendisto. Users can now create and manage HTML-based content blocks with their own name, language, status, and optional start and end date.

This makes it possible to prepare centrally managed content that can later be reused in multiple places, such as content pages, classifications, article groups, articles, news, or wiki-related content.

The content block management includes support for draft, published, and deleted statuses. Visibility is determined by publication status and, where configured, the active date range.

Each content block is stored per language, making multilingual content easier to manage in a structured way. To avoid conflicts, the combination of name and language must be unique.

The rendering of these content blocks in the shop will be added in the next sprint. That next step will make the blocks available through shortcode-based rendering and layout integration, so they can be used directly in storefront content and fixed layout areas.

This sprint therefore delivers the editorial foundation: customers can already start preparing and managing reusable content centrally, while storefront usage will follow in the next release.

Stock information could fail to load for products whose product numbers contain slashes. In these situations, the stock service returned valid data, but the article detail page displayed the status as “Unknown”.

The handling of product numbers containing slashes has been corrected, ensuring that stock information is now retrieved and displayed correctly on the article detail page.

An issue was identified in the Excel Order Upload functionality where the Select all option no longer worked. At the same time, the quantity selector in the upload interface was not activating as expected.

This issue has been resolved, restoring the correct behavior of the selection control and the quantity input in the Excel Order Upload interface.

An issue was identified where component articles with a VAT rate different from 21% could still be calculated using the 21% rate under certain conditions.

This behavior has been corrected so that component articles now use their configured VAT rate when calculating totals.

The meta description filtering introduced in earlier sprints was too strict and removed characters that should normally be preserved in meta descriptions.

The filtering logic has been adjusted to be less aggressive, allowing commonly used punctuation and formatting characters to remain in the generated meta description.

Search could sometimes fail in shops where a separate mobile version of the storefront was also available.

This issue has been resolved, restoring normal search behavior in these environments.

The list of related article types in Vendisto did not show all available relation types. Due to a paging issue, the first item in the list was consistently omitted.

This issue has been resolved, and the overview now displays the complete set of available related article types.

Related articles on the article group page could previously include items with the Component relation type. Because components are intended for product configuration rather than cross-selling, showing them in the general related articles overview created confusion.

This behavior has been corrected by separating the two use cases more clearly.

A dedicated component selection module is now available on the article group page. In this block, only relations with the type Component are shown, and they are rendered as dropdown selections to support the configuration flow.

The Related Articles slider and block now only display relations from other supported relation types. Component relations are excluded from this overview.

An issue occurred in the ERP Cache OrderHistory import where records containing an empty ProductDescription caused the import process to fail.

The import logic has been adjusted to allow empty ProductDescription values.

The ProductDescription element must still be present in the XML structure, even if it does not contain a value.

<OrderLine> <ProductCode>ABC-123</ProductCode> <ProductDescription></ProductDescription> <Quantity>1</Quantity> </OrderLine>

An issue was identified where the import processes for PriceLists and CustomerPrices could incorrectly report a failed import, even when the data had been processed successfully.

The reporting logic has been corrected so that the import status now accurately reflects the actual outcome of the import process.

The first order placed after a period of inactivity could take noticeably longer to process because the Vendisto service was not yet running.

The shop startup process now automatically initializes Vendisto, ensuring that the service is already active when the first order is placed.

To improve in-platform communication, we have introduced a fully integrated Message Center. This feature, demonstrated in the video below, allows users to view and manage notifications without leaving their current page, creating a seamless and non-disruptive experience.

The Message Center is accessible via a notification bell icon in the top-right corner of the header. When unread messages are available, a badge displays the number of new notifications. Clicking the icon opens a side panel that presents messages directly within the interface.

On desktop, the Message Center appears as a right-hand sidebar. On mobile devices, it opens as a full-screen overlay to ensure optimal readability. Messages are sorted from newest to oldest and include:

• A title or short summary
• The time of publication
• An optional icon or avatar
• An action to close or mark the message as read

If additional context is required, a notification can contain a “Read more” link directing the user to a relevant page within the platform. The link opens in the same browser window.

The side panel can be closed in multiple intuitive ways: by clicking outside the panel, clicking the notification icon again, or pressing the Escape key. Unread messages remain marked until the user explicitly closes them. The notification badge automatically updates and disappears when no unread messages remain.

Notifications can be targeted based on authorization profiles. Each message can be linked to one or more existing authorization profiles within the platform. When a user visits the website, the system evaluates their assigned profiles and displays only the relevant notifications.

Non-authenticated visitors receive only messages linked to the public profile. Logged-in users see both general messages and notifications specifically assigned to their authorization profiles. Importantly, when a user closes a message, that action is stored individually. Other users with the same authorization profile will continue to see the notification until they close it themselves.

Message management is handled within Vendisto through a dedicated “Notifications” section. Administrators can create, publish, archive, reactivate, and manage notifications in a structured overview similar to the existing news module. Each notification includes:

• Title (required)
• Message content (with optional link)
• Linked authorization profiles
• Status (draft, published, archived)
• Publication date

For multilingual environments, administrators can define content per language within a single notification entry. This differs from the news module, where separate items are required per language. Optionally, translation services can be leveraged to automatically display messages in the appropriate language, reducing manual effort.

This feature is fully available and operates independently of ERP integrations. It provides a scalable communication layer within the platform, supporting both broad announcements and highly targeted, profile-based messaging.

For products that are temporarily out of stock, customers often want clarity on when new inventory will become available. This release establishes the foundation to display expected delivery dates directly on the product detail page, based on Available-to-Promise (ATP) calculations from the ERP.

In Microsoft Dynamics 365 Finance & Operations (F&O), ATP is calculated as the available inventory plus planned receipts minus quantities already committed to sales orders. When current stock is depleted but inbound inventory is planned, the first date with a positive ATP value represents the expected availability date.

With this enhancement, Shoxl becomes aware of ATP processing in the ERP. When the ATP feature is enabled and a product is unavailable, the standard “Out of Stock” message is replaced by an ATP action. Upon interaction, the platform queries the ERP in real time and retrieves the next date on which quantities become available.

If ATP information is present, the expected delivery date (for example: 19-05-2025) will be shown on the article detail page. This ensures customers receive transparent availability information instead of a generic unavailability message.

This implementation is initially delivered for F&O. Support includes both standard items and so-called KIT articles composed of multiple modules. For KIT products, ATP data is retrieved via the dedicated product availability endpoint, ensuring accurate availability calculations across combined components.

In this sprint, the technical foundation and ERP integration for ATP retrieval have been completed. The functional activation on the storefront is planned for the next release.

The ATP architecture is ERP-agnostic by design. While F&O is the first supported platform, the mechanism supports integration with other ERP systems such as SAP and Exact, which can be enabled based on demand.

This lays the groundwork for a more transparent stock experience, enabling customers to plan purchases based on reliable, ERP-driven availability data.

The video below illustrates how the classification process works within Vendisto. On the homepage, the “Unclassified” list highlights articles that still require classification before they can be properly used within the assortment structure.

In this overview, articles that were in a suspended (inactive) state were also displayed as “To Be Classified.” Although these articles were technically unclassified, suspended items do not require action and should not appear in the operational classification queue.

This created unnecessary noise in the dashboard and could lead to confusion about which articles actually required attention.

The filtering logic has been refined so that only articles with an active status are included in the “Unclassified” list. Suspended or otherwise inactive articles are now excluded from this overview.

The classification dashboard now presents a clean and actionable list, focused exclusively on active articles that genuinely require classification.

Currently, all available payment methods are shown during checkout, regardless of the selected delivery method. The only exception is “On Account,” which is linked to a payment condition retrieved from the ERP system and configured at customer level.

This setup does not allow specific payment methods to be restricted to Pickup only. As a result, payment options such as cash on pickup cannot be selectively displayed based on the chosen delivery method.

With this improvement, payment methods can now be explicitly linked to the Pickup delivery option. When customers select pickup, only the configured payment methods for pickup are shown.

In this case, the following payment methods are supported for pickup:

• CASH_ON_PICKUP
• BUY_ON_CREDIT (if applicable)

The place order request has been extended to include the correct PaymentMethodCode, ensuring the selected pickup payment method is correctly processed downstream.

This enhancement ensures that pickup-specific payment methods such as card and cash are fully supported and correctly handled within the checkout flow.

Rabobank OnlineKassa is the payment solution provided by Rabobank for accepting online payments. It supports commonly used payment methods such as iDEAL/Wero, credit cards, and other local or international options, and is typically used by merchants who want a direct contractual relationship with Rabobank as their acquiring bank.

Within the platform, online payments are usually processed through a broad range of Payment Service Providers (PSPs), including Pay.nl, Stripe, and Mollie. These PSPs act as intermediaries between the shop and the acquiring banks.

In this sprint, a direct integration with Rabobank OnlineKassa has been introduced. This allows merchants who use Rabobank as their primary payment provider to connect their shop directly to Rabobank’s payment environment, without routing transactions through an external PSP.

The integration supports the standard online payment flow, ensuring secure transaction handling, status feedback, and correct order processing within the shop environment.

This enables businesses that prefer or require a direct Rabobank setup to use their existing banking relationship while maintaining a fully integrated checkout experience.

In Exact, articles can be marked for webshop availability using the Webshop checkbox on the article card. Our integration currently exports exactly those articles: everything with the webshop flag enabled is imported into Vendisto.

The limitation is that Exact only provides one webshop flag, while the ERP can serve multiple webshop scenarios (for example a B2C webshop alongside a B2B portal). When the same checkbox is used for multiple channels, the Vendisto export can unintentionally include a much broader assortment than intended.

To support more precise assortment control, an additional export filter has been introduced based on Exact article classifications. This allows the Vendisto assortment to be narrowed down to articles that match one or more configured classification/value combinations (for example, only export articles where a specific classification is set to “Yes”).

If no classification filter is configured, the default behavior remains unchanged: all articles marked with the webshop flag are exported.

The Vendisto product feed can expose a complete set of article data in JSON or XML format for external platforms such as Channable, Amazon, and BOL. The feed may include detailed product information, pricing, and even customer-specific prices where applicable.

Feed generation now leverages the same authorization profiles that are used within the platform to control assortment visibility and content access for specific customer groups or individual customers.

By linking a product feed to an authorization profile, the feed will only contain articles that are assigned to that profile. This ensures that the assortment in the feed aligns exactly with the configured visibility rules.

This makes it possible to define targeted assortments for specific channels—for example, selecting which products should be offered on marketplaces such as BOL—without requiring separate feed logic or manual filtering.

ShoxlSync is the synchronization mechanism that transfers product information from Vendisto PIM to our cache database RavenDB. Within this process, product data is transformed into a read-optimized structure, ensuring that shop environments can retrieve information quickly and efficiently. In essence, ShoxlSync converts PIM-managed product data into a format specifically optimized for high-performance read access.

In environments with very large product collections (for example, more than 100,000 items), the synchronization process could consume substantial memory. In certain cases, this caused the process to time out before completion, resulting in only part of the assortment being synchronized.

Previously, when a synchronization was interrupted, restarting ShoxlSync would initiate the entire process from the beginning. This increased processing time and could lead to repeated timeouts in high-volume environments.

The synchronization mechanism has now been enhanced with resume functionality. If the process is interrupted due to memory constraints or timeouts, it can continue from the last successfully processed point instead of restarting entirely.

This improvement increases stability and ensures that even very large assortments can be synchronized reliably and efficiently.

On the article group overview page, the call-to-action buttons were not always consistent across similar items. In some cases, products that should have shown a quote request action displayed a standard “View” button instead.

This behavior was caused by logic that did not fully align with how certain related items were configured and rendered within the listing.

The button logic has been corrected to ensure consistent behavior. Quote-request items now reliably display the appropriate quote action, while regular items continue to show the standard view button.

For end-of-life articles with limited stock, the quantity validation in the basket was not consistently enforced when users manually entered a number in the quantity field.

When a customer entered a quantity higher than the available stock directly in the input field (for example, 50 units while only 38 were in stock), it was still possible to proceed to the next checkout step. The stock validation worked correctly when using the “+” and “–” buttons, but not when manually editing the quantity.

In addition, the validation state was not properly synchronized:

• The “Next” button remained disabled after a stock overrun, even when the quantity was corrected below the available stock.
• After refreshing the basket containing an over-ordered item, the stock warning disappeared and the order could proceed without proper stock validation.

The stock control logic has been corrected to ensure consistent validation, regardless of how the quantity is adjusted. Manual input, button controls, and basket refresh scenarios now all trigger the same stock validation behavior.

This prevents customers from continuing with quantities above the available stock and ensures clear, reliable feedback within the basket.

Product images shown in the order list were not always updated after changes were made to the article images in the system.

As a result, outdated or previously cached images could remain visible in the order overview, even though the correct and updated image was already available at article level.

The image handling logic for the order list has been adjusted to ensure that updated product images are correctly retrieved and displayed. Image references are now refreshed consistently, preventing outdated visuals from appearing in the order history.

This ensures that the order list accurately reflects the current product imagery across the platform.

The Shoxl shop supports bundled property filters, allowing multiple related product properties to be grouped into a single filter in the webshop. This keeps the filter panel structured and helps customers navigate large assortments more efficiently.

In certain scenarios, the product counts displayed next to filter options were not recalculated correctly after selecting a filter. As a result, the numbers shown did not always reflect the actual remaining product set.

The filter logic has been improved to ensure that product counts are dynamically and accurately updated after each filter selection. The displayed numbers now consistently represent the correct number of matching products.

This ensures a reliable and transparent filtering experience, especially when working with bundled filter configurations.

We are introducing a new spare parts search capability that enables users to find replacement components for assembled products directly from the underlying Bill of Materials (BOM). This feature is designed to support complex, multi-component products and will make spare part ordering significantly more structured and intuitive.

The functionality is inspired by a structured spare parts flow where users:

• Select a product category.
• Refine by product subcategory.
• Choose a specific product variant.
• View all related spare parts based on the configured spare part BOM.

Instead of manually identifying individual components, the system will automatically retrieve spare parts from the ERP based on the active spare part BOM linked to the selected product. Only BOM versions marked as Spare Part = Yes and Active = Yes are considered leading. From there, all relevant BOM lines are extracted and presented as orderable items.

Technically, this is powered by integration with Microsoft Dynamics 365 Finance & Operations (F&O). The implementation retrieves:

• BOM versions that qualify as active spare part lists.
• All associated BOM lines that represent the actual spare parts.

Once a product variant is selected, the spare parts defined in its active spare part BOM become directly visible. These components can be added to the basket from the same interface, enabling a streamlined ordering process for aftersales and service scenarios.

In this release, the technical foundation for this capability has been completed. The underlying architecture, data retrieval logic, and ERP integration for F&O are in place. The functional rollout of the spare parts search interface is expected in the upcoming release.

Although the first implementation is focused on F&O, the design is platform-agnostic. The architecture supports expansion to other ERP platforms such as SAP and Exact, which can be enabled based on demand.

This lays the groundwork for a scalable and ERP-driven spare parts experience, fully aligned with structured product data in the source system.

The product configurator allows users to compose a product by selecting variants and optional components directly from the article group or product detail page. This creates a guided configuration flow where the correct variant is selected first, followed by the relevant components.

The component dropdowns can now optionally display the stock status of each individual component within the selector. This provides immediate insight into availability during configuration, helping users make informed choices before adding the composed product to the basket.

When working with multiple packaging units in Exact, each packaging unit linked to an item is created as a separate article in the portal. This allows customers to order the same product in different units, such as piece, box, or pallet.

If a packaging unit becomes inactive or expires in Exact, it should no longer be available for ordering. However, these inactive units could still be included in exports, potentially resulting in unintended article creation in the portal.

The Exact Online BatchInterface now synchronizes Unit master data. This enables the map-package-units-to-article-numbers flow to exclude inactive units from exports, preventing articles from being created for expired packaging units.

When displaying real-time stock levels in the webshop, negative stock values can appear if the ERP allows backorders. However, showing a negative quantity does not provide meaningful information to end users and may cause confusion.

A new ShowNegativeStock setting has been introduced to control how negative stock is handled in the webshop. This allows you to prevent negative quantities from being displayed, ensuring stock information remains clear and relevant for customers.

Within the optional ArticlesOverview layout, users can filter products by selecting a main category from the dropdown above the filter menu. The right pane then displays all products within that category, optionally including subcategories.

A bug caused the selected category filter to be lost after changing the sort order or navigating to another page in the product list.

This has been resolved. The net price and category filtering now remain active when sorting or switching pages, ensuring consistent and predictable product overviews.

On shops with a dedicated Brand page, users can select a brand image to view all products associated with that brand. This redirects to the search page with the selected brand applied as a filter.

When users subsequently refined the results using additional filters, the brand filter was unintentionally lost, causing all products to be displayed instead of only those belonging to the chosen brand.

This behavior has been corrected. The selected brand filter now remains active when applying additional filters, ensuring consistent and accurate search results.

In certain scenarios, color filter options remained visible even when no products were available in that color. These options were sometimes disabled instead of being fully removed, which could create confusion.

The color filter logic has been adjusted. Unavailable colors are now hidden from the filter, ensuring that only applicable options are shown to the customer.

On the article overview page, a selected filter could unintentionally reappear after resetting the filters and then changing the sort order of the results. This led to inconsistent filtering behavior.

This issue has been resolved. Filters now remain properly cleared after a reset, regardless of subsequent sorting actions.

Property values containing leading or trailing whitespace could result in duplicate or inconsistent filter values within the shop.

Stock levels for article variants were not fully synchronized, which could result in incomplete or incorrect availability information for variant-based products.

Multi-key synchronization has been added to the Microsoft Navision BatchInterface. This allows stock quantities per article variant to be retrieved and synchronized correctly, ensuring accurate availability for products with multiple variants.

When managing relation types in Vendisto, the pagination and search functionality in the overview did not work correctly. This could give the impression that newly created related article types were limited or not fully visible.

The pagination and search behavior has been corrected. The relation type list now displays all available entries correctly and supports proper searching and navigation.

Product configuration has been significantly enhanced by combining the Article Selection Wizard (ASW) with the Components interface.

Previously, the ASW was available on the article group page to select the correct product variant based on properties. Component selection, however, was only available on the individual article page—after a specific article had been selected.

With this improvement, the Components selector is now directly integrated into the article group page. As soon as the ASW results in a single matching article, the component selection is automatically activated and displayed.

This creates a seamless configuration flow: users can first select the correct variant and immediately choose additional components—without navigating to a separate page.

The result is a faster and more intuitive product configuration experience, reducing clicks and streamlining complex product selection.

For configurable products, users can compose an article by selecting options or components on the product page. The chosen configuration is then displayed as a combined item in the basket.

When navigating back to the product page from the basket, the previously selected components were not shown. This meant users had to reconfigure the product from scratch.

The selected options are now correctly restored when returning to the product page. The configuration remains visible and editable, exactly as it was added to the basket.

This improvement makes it easier to review or adjust complex product configurations without losing previous selections, resulting in a smoother and more efficient buying experience.

The components interface allows users to configure a base product by selecting additional options or components. These selected options can influence the final product price.

In certain cases, the total amount for the configured bundle was not displayed correctly. While individual component prices could be selected, the calculated total was not shown in the interface.

The total price calculation is now correctly rendered within the components interface. Users immediately see the combined price of the base product and selected options.

This ensures full price transparency during product configuration and provides clearer insight into the financial impact of selected options.

The article group overview now supports sorting by article number. This provides an additional way to organize product listings, particularly useful when working with structured assortments or internally referenced product codes.

When sorting by article number, individual articles are ordered accordingly. If both articles and article groups are shown in the same overview, the article groups are automatically placed at the bottom of the list to maintain a clear structure.

This enhancement makes it easier to quickly locate specific products and improves efficiency when navigating larger product ranges.

When browsing the classification structure, the shop automatically advances to a lower classification node, article group, or article if only one option is available.

If multiple automatic steps were required, the navigation previously triggered a chain of 302 redirects. Each intermediate level caused an additional redirect before reaching the final destination.

This flow has been optimized to use a single redirect, even when multiple levels are skipped. This reduces the number of HTTP 302 responses generated during navigation.

When exporting account managers through the Exact BatchInterface, the status was not always set correctly upon creation. This required manual activation before the account manager could be used.

The export logic has been adjusted so that account managers are now created with the status set to Active by default.

This ensures that newly exported account managers are immediately available in Exact without additional administrative steps.

Some shops became unresponsive due to intensive indexing by external agents. These automated crawlers generated high resource consumption on the server, affecting overall performance and availability.

An investigation was conducted into blocking specific high-impact agents at IIS level. By configuring URL Rewrite rules in IIS, selected agents can automatically receive a 403 (Forbidden) response. This prevents unnecessary processing of their requests and significantly reduces server load.

The rules can be applied globally at server level or configured per website, depending on the desired scope. This provides flexibility while ensuring that legitimate traffic remains unaffected.

This approach helps safeguard shop performance, improving stability and responsiveness during periods of heavy automated traffic.

The reorder function in the order history did not always provide clear feedback when certain articles were no longer eligible for reorder. As a result, users were left without insight into why a reorder action could not be completed.

The feedback mechanism has been improved. When an article cannot be reordered, the user now receives clear and relevant information about the reason.

This makes the reorder process more transparent and prevents confusion when previously ordered items are no longer available under the same conditions.

The article import supports splitting and merging article groups using the Group ID column in the Excel import file.

During a merge, suspended variants could unintentionally switch to an active status. This occurred when the first article in the merged group previously belonged to a suspended article group.

The merge logic has been corrected. Variant statuses are now retained exactly as defined in the import, so suspended articles remain suspended after merging.

When orders are calculated in real time, integrations rely on consistent field names and complete address details. Small mismatches in the endpoint definition can lead to avoidable mapping work or failed validations.

A new CalculateOrderV3 endpoint definition is now available for implementation. It introduces a DivisionCode, includes invoice and delivery address information, and corrects several field name spellings.

• DivisionCode support for scenarios with multiple divisions or entities.
• More complete invoice and delivery address data in the contract.
• Spelling corrections in field names to improve consistency and reduce mapping issues.

This helps integrations exchange cleaner, more reliable order data and reduces the risk of discrepancies between systems.

The interaction between Mollie webhooks and the order process has been aligned with the PlaceOrderMode configuration. Previously, webhook handling could behave independently of the selected order flow, which made payment processing harder to predict in certain scenarios.

Webhook behavior now follows the configured order placement mode. Whether an order is placed before payment, after payment, or without a PSP redirect, the webhook processing aligns with that selected flow. This ensures consistent handling between payment status updates and ERP order posting.

In addition, extra logging has been added to the webhook component. This provides more detailed insights into payment callbacks and simplifies troubleshooting when investigating payment-related behavior.

This results in a more predictable checkout experience and improved transparency when diagnosing payment or order flow issues.

In release 66, a global setting was introduced to hide all prices across the platform. This allows shops to completely suppress price visibility in scenarios where pricing should not be shown.

In the new basket layout, this setting was not yet fully respected in all configurations. As a result, prices could still appear in certain basket layout variations.

The basket logic has now been aligned with the global hide price setting. When price visibility is disabled, prices are consistently hidden in the basket—regardless of the selected layout.

This ensures the global pricing policy is enforced uniformly, supporting business models where pricing is conditional or restricted.

A new backend service has been implemented for the ImportExport Dashboard. This service processes and stores events generated by various import and export tasks.

All task-related events are logged in a dedicated database. These logs will be surfaced in the upcoming ImportExport Dashboard interface.

This enables structured tracking of completed import and export jobs, including access to detailed error and warning information per task.

When browsing through the article table, some product properties could temporarily disappear after navigating between pages. This made it harder to compare items and review key product details.

The table rendering has been corrected so that properties remain consistently visible when moving between pages.

This ensures a smoother browsing experience and helps users make selections based on complete product information.

The partial export in the Navision Batch Interface periodically retrieves all new or modified records. In high-traffic webshops, the volume of updates could grow significantly, causing export processes to overlap before previous runs were completed.

The export mechanism has been updated to support batched partial exports. Instead of processing all updates in a single run, records are now handled in controlled batches.

This prevents overlapping export jobs, reduces peak load on the integration layer, and ensures more stable processing during busy periods.

When a shop user places an order on behalf of a customer and specifies a different delivery address, Exact Online automatically creates a new delivery address under that shop user’s account. This system behavior cannot be disabled and caused one-time dropshipment addresses to remain permanently linked to the account.

To resolve this, a new Dropshipment flag has been added to the Delivery Methods settings in the webshop. During checkout, users can indicate that an order is a dropshipment and provide an alternative delivery address.

In the Exact BatchInterface, a new setting called DropShipmentAccountNumber has been introduced. When an order is marked as a dropshipment, the delivery address and related contact details are created under a dedicated dropshipment account instead of the ordering user’s account.

This prevents one-time delivery addresses from cluttering regular account data, keeps customer records structured, and improves data quality within Exact Online.

In the Article Selection Wizard (ASW), certain property values are displayed visually—such as colors or other graphical indicators. In some cases, it was not immediately clear what a specific option represented based on the visual alone.

To improve clarity, the corresponding property value is now shown in a tooltip when hovering over these visual options. This applies to colors as well as other visually represented properties.

This enhancement makes variant selection more transparent and reduces uncertainty when choosing between visually similar options.

The Article Selection Wizard (ASW) is designed to help users quickly select the right product variant within an article group. When a product group contains multiple variants with different product properties, the ASW provides an alternative to a traditional article table with filters.

Instead of browsing a table, users can select property values through dropdowns or selectable pills. As selections are made, incompatible property values are automatically disabled. This makes it easy to narrow down to a valid product combination in just a few clicks.

In situations where icons were expected for property values but not available, the wizard did not properly fall back to displaying text values. As a result, certain options were not shown as intended.

The ASW now automatically switches to a text-based display when icons are missing. This guarantees that all product options remain visible and selectable, ensuring a smooth and reliable product selection experience.

Delivery schedules define which delivery dates are available in the shop and until when an order can be placed (cut-off time). A base schedule is configured per day of the week, with optional date-specific overrides such as holidays or custom delivery days. Overrides can apply to all customers or to specific customer selections, offering maximum flexibility in delivery planning.

When a large number of customers was linked to a delivery schedule, the detail screen in Vendisto could become unresponsive. Extensive customer collections caused the interface to freeze for a prolonged period, impacting usability.

The internal handling of customer collections within the delivery schedule component has been optimized. This ensures stable and responsive behavior, regardless of the number of customers associated with the schedule.

As a result, delivery schedules can now be managed smoothly—even for complex setups with large customer groups—supporting efficient campaign planning and reliable delivery management.

Stronger account security can now be managed more consistently across the platform. Two-factor authentication (2FA) behavior is configurable in a clearer and more centralized way.

The default 2FA setup is controlled through the Account API settings. This allows you to enforce two-factor authentication for all users or define the default authentication method through configuration. Changes no longer require adjustments in multiple locations.

• Enforce 2FA platform-wide via configuration.
• Set the default 2FA method centrally.
• Adjust security behavior without custom development.

This approach simplifies security management, reduces configuration ambiguity, and ensures a consistent authentication experience for all users.

Users can now manage their own two-factor authentication (2FA) preference directly from the account environment. A new option has been added under My Account > General > Security, allowing users to enable or disable 2FA themselves.

This gives users greater flexibility in how they secure their accounts, while keeping the experience straightforward and transparent.

If 2FA is enforced at administrator level, the option is automatically disabled. This ensures that centrally defined security policies always take precedence.

The result is a better balance between user autonomy and centralized security control.

Classification node–level authorization has been extended to support multi-shop environments where multiple classifications exist within the same product structure.

Shoxl can now handle multiple classifications linked to different shop instances. During synchronization, product data from Vendisto (PIM) is distributed per classification to the corresponding shop database. This ensures that each shop receives only the data relevant to its assigned classification.

To prevent conflicting authorization behavior, multi-category support cannot be combined with classification node–level authorization. This combination has been disabled to ensure predictable and consistent access control.

This enhancement enables clearer separation between shop environments while maintaining structured and controlled product visibility.

Classification Excel import and export now support AuthorizationProfile columns. When the ClassificationNodeAuthorizations license is enabled and the UseMultiCategory setting is set to false, these columns are fully processed as part of the classification structure.

With this change, authorization configuration at classification level can be managed directly through the Classification import and export workflow.

When the ClassificationNodeAuthorizations license is active, AuthorizationProfiles are no longer handled through the Article import/export process. This ensures a clear separation between product data management and classification-level authorization control.

Automatic vouchers are applied when the basket total exceeds a predefined threshold. In certain scenarios, when the basket total later dropped below that threshold, the voucher handling logic behaved inconsistently.

This could lead to unexpected voucher removal and, in some cases, an error during checkout that prevented the order from being completed.

The threshold validation and voucher handling logic have been corrected. Basket recalculations now behave consistently, ensuring that checkout proceeds smoothly without unexpected errors.

This improvement safeguards promotional campaigns and prevents disruption in the checkout flow when basket totals change.

Within specific Microsoft Finance & Operations integrations, an alternative delivery address must always be handled as a dropshipment. The F&O setup assumes that any deviation from the default delivery address represents a dropshipment scenario.

To support this requirement, the webshop setting DropShipmentOnAlternativeAddress has been introduced. When enabled, the system automatically applies the DROPSHIPMENT delivery method whenever an alternative delivery address is used.

This logic is enforced in both the CalculateOrder and PlaceOrder processes, ensuring consistent behavior throughout the order flow and alignment with the F&O processing model.

The Vendisto Customer Export has been extended to include the Division Code when integrated with Microsoft Finance & Operations.

The DataAreaId from F&O is now exported as the Division Code through the F&O Batch Interface. This ensures that customer data reflects the correct organizational structure when processed externally.

By aligning export data with the division structure in F&O, integrations become more accurate and easier to manage across multiple legal entities or business units.

The Authenticator API has been extended to support the Microsoft Client Credentials flow. This enables the service to request and manage access tokens for Microsoft Finance & Operations.

By handling token retrieval centrally, integrations with F&O can rely on a consistent authentication approach across applications, reducing configuration effort and simplifying ongoing maintenance.

This enhancement strengthens the foundation for secure and scalable ERP connectivity.

In previous releases, authorization behavior had to be configured during deployment, with multiple possible setup options. While flexible, this added unnecessary complexity behind the scenes.

Authorization is now fully managed through a single central service. This ensures a consistent and reliable validation process across the entire platform.

What’s in it for you? A more stable and predictable platform experience. By removing configuration differences between environments, we reduce the risk of unexpected behavior and improve overall reliability—without requiring any action from your team.

The former authorization setting has therefore been removed, as it no longer serves a purpose.

The WebService now supports authentication through the Authenticator API. This introduces token-based authentication as an additional authentication mode for web service requests.

By integrating with the Authenticator API, authentication is handled in a centralized and secure manner. Tokens can be managed consistently, reducing dependency on alternative authentication mechanisms.

This enhancement strengthens security for integrations while simplifying authentication management across connected systems.

The Navision Batch Interface now determines the order line status dynamically based on shipment information received from Microsoft Navision.

The status is calculated by comparing the ordered quantity with the quantity that has been shipped. This ensures that order lines accurately reflect their actual fulfillment state.

• If the full quantity has been shipped, the status is set to Shipped.
• If only part of the quantity has been shipped, the status is set to Backorder.
• If no quantity has been shipped, the status remains Open.

This improvement provides clearer order visibility and ensures that customers and internal users see an accurate fulfillment status at line level.

In certain classification layers, product tiles in the article group overview did not always display the correct prices immediately. This could lead to incomplete information being shown while browsing product categories.

The pricing logic behind the overview has been refined to ensure that all relevant prices are loaded consistently across classification levels.

This improvement provides a more reliable and transparent browsing experience, allowing customers to view accurate pricing information directly within the product overview.

In some cases, static lists displayed in the basket remained stuck on a “loading…” placeholder. The order interface data was not compiled correctly, preventing prices and related order information from being rendered.

The underlying logic responsible for assembling the order interface data has been corrected. Static lists in the basket now receive the required order information, including pricing details.

This ensures that basket contents are displayed completely and accurately, giving users immediate visibility into pricing without delays or confusion during checkout.

Discount calculations in the Exact BatchInterface did not fully align with the logic used in the webshop. Total order discounts were previously calculated by adding discount percentages together, which could lead to differences compared to the basket calculation.

The discount logic has been updated so that discounts are now applied sequentially, matching the calculation method used in the webshop basket.

This ensures that total order amounts are calculated consistently across both systems, preventing discrepancies and improving financial accuracy in order processing.

Webshop users can now place orders even when no prices are shown anywhere in the shop.

With the hide prices setting enabled, all pricing information is fully hidden across product pages, listings, the basket, and checkout. This includes product prices, discounts, taxes, and order totals.

Despite the absence of any visible prices, users can still complete the full ordering process. To avoid exposing amounts during payment, ordering in this scenario is limited to order on account.

This is particularly useful for situations such as internal ordering, sales representatives placing orders on behalf of customers, approval-based purchasing flows, or environments where pricing is agreed offline and should not be displayed in the shop.

Note: In some views, empty placeholders may remain where price elements would normally appear. This does not impact functionality and ensures that shops where prices are visible continue to behave as expected.

Two-factor authentication (2FA) is now available to add an extra layer of security to webshop logins.

2FA can be enabled per company by an administrator, and can also be managed by users in the MyAccount section. Once enabled, users confirm their login with an additional verification step.

For the initial rollout, 2FA uses email verification, which is a widely adopted approach in B2B environments. During login, a one-time verification code is sent to the user’s email address and must be entered to complete the sign-in.

Several settings are available to tailor the 2FA behavior per tenant, including the default 2FA type, whether 2FA is enforced for all users, the code expiration time, and the maximum number of allowed attempts. Integration with an email service is configured via the EmailServiceUrl setting.

Authorizations in the shop determine which products customers are allowed to see. This is controlled through authorization profiles that can be linked to both customers and products, ensuring that customers only see items that match their assigned profiles.

Managing these authorizations was previously limited to the product variant level, which made maintenance time-consuming and fragmented. This update introduces the ability to manage authorization profiles directly at the classification node level.

When an authorization profile is assigned to a classification node, it is automatically applied to all products and variants within that node. If this feature is enabled, an Authorizations block becomes available on the detail screen of the lowest classification nodes, making it easy to manage visibility in one central place.

This enhancement provides a more efficient and scalable way to control product visibility, reducing the need for repetitive configuration on individual products.

New user rights have been added to provide more control over who can place orders or request quotes in the webshop.

You can now hide the order button or the quote button for specific users. This ensures that selected users are unable to place orders or submit quote requests, while still allowing them to browse the shop.

An additional option allows all prices to be hidden for a specific user across the entire shop, including product pages and the basket. Users with this setting can still go through the ordering process, but without seeing any prices. To prevent prices from being exposed, the only available payment method for these users is order on account.

All three rights can be managed either through the import/export module in Vendisto or via the webshop’s user management module.

A new Limited Order Calculation setting has been introduced to reduce load on connected ERP systems.

When this setting is enabled, the shop only performs lightweight price retrieval while users are browsing and updating the basket. Full order calculations—such as totals, vouchers, and additional cost lines—are no longer executed automatically on every change.

Instead, a new Calculate Order button is available directly in the basket. Full calculations are performed only when this button is clicked, or automatically when the user proceeds to checkout.

This approach significantly reduces unnecessary ERP calls while still giving users full control over when a complete order calculation is performed.

The basket has been optimized to reduce unnecessary calls to connected ERP systems and improve overall performance.

Instead of repeatedly requesting separate price data, the basket now relies on calculated order results. This ensures that pricing, totals, and related order data are retrieved in a more consistent and efficient way.

To further improve responsiveness, in-memory caching has been added for both price data and calculated orders in the ERP connectors. Cached responses are reused for a configurable period, reducing latency when ERP responses are slow.

The cache duration for price data and calculated orders can be configured independently, allowing performance to be tuned per environment while keeping pricing information up to date.

To improve reliability when delivering BMECAT data to the 2BA platform, the ProductGroup API has been extended with a new XmlSchemaLocation setting.

When this setting is configured, the exported XML includes a reference to the corresponding XSD schema. This allows the AutomaticProductImportManager to validate the XML against the XSD before it is sent onward.

If the validation fails, an email is automatically sent with the validation errors. This helps resolve issues earlier in the process and ensures that only valid, BMECAT-compliant data is forwarded to 2BA.

Order history data is synchronized from Exact Online to keep order information up to date in the shop.

Previously, adding a Track & Trace code to an existing order did not trigger an incremental update in the order history export. As a result, newly added shipment information was not shown in the shop.

This has been improved so that Track & Trace updates now correctly trigger a partial synchronization. Order history is updated incrementally, ensuring shipment information becomes available as soon as it is added.

When exporting articles through the FO Batchinterface, the classification structure could previously not be adjusted, which limited flexibility in how product data was exported.

This update introduces a new configuration option that allows you to define the maximum classification depth for the FO Article Export. This makes it easier to tailor exports to specific integration or reporting needs.

By controlling the classification depth, exported data becomes more focused and better aligned with downstream systems.

In Vendisto, relationship types allow you to define how articles are connected to each other. These types can be configured freely, for example to indicate related or complementary products, and are used to structure how these relations are shown in the shop.

One specific relationship type is Component. This type is used to define which components should be ordered together with an article, either optionally or as a required part of the purchase.

In some situations, newly created relationship types of the Component type could no longer be selected when linking related articles. This made it impossible to configure component-based product selections.

This issue has been resolved by correcting the underlying user rights handling. Component relationship types can now be selected again as expected, allowing component configurations to be set up and used correctly.

The address book in MyAccount did not fully support all available address formats, which could lead to errors or incomplete address information being shown.

In some cases, opening the address book resulted in rendering errors, even though valid and complete addresses were available. In other situations, the address book loaded without errors but displayed addresses missing key details such as street name or house number.

This update improves how different address formats are handled. The address book now correctly supports both combined and separated street address types, ensuring addresses are displayed consistently and without errors.

As a result, address data is rendered more reliably across the address book, Vendisto, and the ordering flow in the shop.

In some areas of Vendisto, certain icons were not displayed correctly, which could make parts of the interface harder to understand.

This issue was caused by a missing font file that is required to render these icons.

The font file has been restored, ensuring that all icons are displayed consistently and the interface is visually complete again.

When exporting pricelists, prices were previously limited to two decimal places. This could lead to rounding differences, especially for discounted prices with higher precision.

In certain scenarios, these rounding differences added up in the basket when larger quantities were ordered, resulting in totals that did not match the expected amount. This was particularly noticeable for promotional pricing.

The pricelist export has been improved to retain full decimal precision when retrieving prices from the source system. This ensures more accurate pricing calculations and prevents cumulative rounding differences in the basket.

The import/export module in Vendisto allows order lists to be imported from Excel for efficient order management.

Due to an issue in the import logic, importing multiple order lists from a single Excel sheet was no longer possible. This limited the ability to process several order lists in one import action.

The import logic has been improved, restoring support for importing multiple order lists from one Excel file. This makes bulk imports reliable again and helps streamline order list management.

Product detail pages support multiple languages, allowing visitors to switch between available translations using the language selector.

In some situations, using the language switch on a product page did not change the displayed language. Although the page was reloaded, the content remained in the same language.

This behavior has been corrected so that the language switch now loads the selected language properly on product detail pages. As a result, translated product information is shown consistently when switching languages.

In some scenarios, customers are linked to a different debtor using the Invoice-to setting from Exact Online, which defines where invoices should be sent.

This update introduces support for inheriting pricing from the linked invoice-to debtor. When a customer has an invoice-to relationship configured, the shop will now automatically apply the prices and discounts from that associated debtor.

As a result, promotional prices and special price periods defined on the invoice-to price list are shown correctly, even if the customer’s own price list does not contain those articles.

This enhancement makes pricing behavior more consistent with invoice handling and provides greater flexibility for setups where ordering and invoicing are handled by different debtors.

Vendisto supports separate email settings for order confirmations and quote-related communication, allowing each flow to be configured independently.

In some cases, email settings from order confirmations were applied to quote requests and quote confirmations instead of using the dedicated quote email configuration. As a result, configured BCC email addresses were not included in quote emails.

This has been corrected so that quote requests and quote confirmations now use their own email settings as intended. BCC addresses configured for quotes are once again included, ensuring all recipients receive the correct communication.

When using accumulative discounts with tiered pricing, product pages show a starting (“from”) price alongside the discount tier table to help customers understand the pricing structure at a glance.

In certain configurations, the displayed starting price was calculated incorrectly. The “from” price could show the lowest achievable price instead of the price for the lowest quantity tier, even when the UseAccumulativeDiscountsPriceDisplayOverride setting was not enabled.

This has been improved so the “from” price is now aligned with the lowest quantity tier when tier information is shown. The price table continues to reflect the correct tier prices, while the headline price is displayed consistently with the intended configuration.

Vendisto supports customer-specific VAT percentages to handle special tax scenarios without impacting other customers.

In certain cases, setting a customer-specific VAT percentage could unintentionally override the shop’s gross price tax configuration. This caused incorrect prices to be displayed for other customers.

This behavior has been corrected so that customer-specific VAT settings are applied only to the intended customer. Global pricing and VAT configurations for the shop remain unaffected.

Customer contacts are synchronized through the Microsoft F&O Batch Interface to keep contact information consistent across systems.

To prevent duplicate entries, new logic has been added that automatically deduplicates customer contacts during import. Contacts are matched based on first name, middle name, last name, and email address.

This improvement helps keep customer contact data clean and avoids unnecessary duplicates in Vendisto.

Customer availability in Vendisto is synchronized with data from Microsoft Navision through the Batch Interface.

The logic that determines whether a customer is considered active has been updated to better align with NAV data. Customers are now marked as active only when the Blocked field in the CustomerCard endpoint has no value.

This ensures that customer status is interpreted consistently with NAV, providing more reliable control over which customers can access the shop.

The search autocomplete dropdown has been enhanced to provide more detailed product information.

Article numbers are now displayed alongside product names in the autocomplete search results. This makes it easier to quickly identify the correct article, especially when multiple products have similar names.

This improvement helps speed up searching and reduces the chance of selecting the wrong product.

When working with baskets that contain a large number of articles, it was not always clear that prices were being recalculated after changing quantities.

The quantity selector now immediately shows loading feedback as soon as a quantity is changed. This makes it clear that the basket is processing the update, even before price recalculation is completed.

As a result, users receive clearer visual feedback during basket updates, improving the overall experience when managing larger orders.

This update introduces a more flexible and configurable address management system for shops and portals, allowing a clear distinction between addresses managed by the ERP system and those managed locally within the shop.

In systems such as Exact Online, all delivery addresses are fully controlled by the ERP. To prevent duplication or inconsistent data, shops using Exact are now configured with the new AddressManagement setting set to ERP. In this mode, newly entered delivery addresses are not stored locally — they will reappear after synchronization from the ERP. For other ERP systems, the setting can be configured as Local, allowing users to manage their own address book within the shop.

Each address now includes an addressOrigin value (ERP or Local), determining its behavior. ERP addresses are read-only and cannot be edited or removed. Local addresses can be added, modified, or deleted by the user.

In the My Account section, address management has been enhanced to clearly separate billing and delivery addresses. Each section lists centrally managed (ERP) addresses first — marked with “Managed by [shop name]” — followed by locally managed addresses. ERP addresses show only the “Set as default” action (if not already selected), while local addresses support editing, deletion, and default selection. All address edits happen inline, with clear save and cancel options, and deletion requires confirmation.

This enhancement provides better alignment with various ERP behaviors while giving flexibility to manage addresses efficiently within the shop or portal environment.

A new Dealer Locator module has been introduced, allowing shops to display dealers on an interactive map. Dealer data can be imported and managed through Vendisto using the import/export module.

The module can be placed on any shop page by selecting the DealerLocator page type or by inserting it through custom HTML tagging in Vendisto. It includes a dynamic map with dealer pins, a dealer list, and both search and filtering functionality. Clicking a pin opens a popup showing the dealer’s name, address, and website.

The dealer list can be searched independently. When a search is performed, both the list and the map automatically update to show only matching dealers. Visitors can also filter dealers based on specific attributes such as having a showroom, delivering to private customers, or operating a webshop.

Entering a city or address refines the results to show dealers closest to that location. The number of displayed dealers can be configured through the webshop settings.

2BA is a standardized data platform for the construction and installation sector that enables manufacturers, wholesalers, and software suppliers to exchange rich product and pricing information based on the BMEcat ETIM format. Integrating with 2BA allows suppliers to automatically publish their product data — including technical specifications, trade information, and prices — in a format recognized across the industry.

With this release, the ProductGroup API has been extended to support configuration of the BMEcat XML structure used for trade record generation. This enhancement enables customers to automatically deliver complete and structured trade data as zipped archives to the 2BA SFTP server.

From this point, customer implementation specialists can configure and activate the 2BA connection for live environments.

To support the 2BA BMEcat 2005 ETIM export format, several improvements have been introduced to the Product API and ProductGroup API. Both APIs already allow export of product data in XML, Excel, and CSV formats using configuration documents that map internal database fields to standardized output structures.

Key enhancements include:

• Lookup Converter: Enables mapping between input and output values through configurable conversion tables (e.g., converting “pc” to “038”). This is used for translating Unit Codes such as Order Unit and Content Unit.
• Date/Time Fields: New System_Now token and Format property allow exporting the current date and/or time as part of the output file.
• Tax Conversion: A new converter type exports tax percentages (e.g., “21”) as decimal values (“0.21”), improving compliance with BMEcat requirements.
• Language Code Extension: Added support for three-letter ISO language codes (dut, eng, etc.) following ISO 639-2 standards, allowing XML attributes like lang="dut" in exports.
• XML Configuration Improvements: The API definition now supports namespaces, root attributes, and nested settings. A new XmlRootField enables inclusion of import settings sections in XML output and supports exporting localized values using LcidValueFormat (e.g., lang="nl" instead of lang=1043).

Together, these enhancements provide the flexibility and precision required to generate fully compliant BMEcat exports, ensuring seamless synchronization of product and pricing data with the 2BA datapool.

A new feature allows users to save their entire shopping basket as an order list, making it easy to temporarily store an order and place it later.

Users can create multiple order lists, each functioning like a personalized collection of frequently ordered products — similar to a favorites list, but more powerful. Entire order lists can be reloaded into the basket at any time, enabling quick and efficient reordering.

This enhancement offers greater flexibility for users who regularly place similar orders or want to prepare and organize future purchases in advance.

Exact Online supports multiple types of pricelists, each with a distinct purpose and hierarchy. A standard pricelist defines the base customer prices. A discount or promotion pricelist can temporarily override these base prices, while a special offer pricelist (“aanbieding”) applies short-term or campaign-specific prices. Pricelists can be linked to one another, where promotional lists reference the customer’s main standard list to determine the original prices.

When a standard pricelist of the type aanbieding is created, the shop now automatically displays the original (customer-specific) price as the “from” price and the price from the active standard pricelist as the “to” price.

This provides a clear and consistent way to show discounted pricing in the shop. It’s also possible to define a promotion period within a pricelist for a specific product, which produces the same “from/to” pricing effect.

Exact Online performs regular maintenance between 4:00 and 4:45 AM (CET). During this period, the service may be temporarily unavailable, which previously caused issues for customers operating in other time zones where this window overlaps with working hours.

When Exact Online does not respond, the system automatically retries order submissions several times. If these retries fail, the order is moved to the “failed orders” folder. While notifications were being sent, orders remained unavailable in Exact until manual action was taken.

To address this, email notifications in the Exact Batch Interface have been refined: alerts are now suppressed for expected HTTP responses such as Service Unavailable to avoid unnecessary warnings during planned maintenance.

Additionally, a new AppOffline setting has been introduced. This allows configuration of maintenance or downtime windows in the Exact Online Batch Interface, ensuring that retries and notifications behave predictably when Exact is temporarily offline.

This improvement prevents confusion and redundant alerts, particularly for international users affected by time zone differences.

The Vendisto Customer data model has been updated in preparation for upcoming credit limit functionality. These changes lay the groundwork for enforcing and displaying credit limits within the shop in a future release.

Both the Vendisto WebServices and XML import processes now support an extended <BuyOnCredit> structure that includes the following sub-elements:

<Enabled> <Limit> <Remaining> 

This new structure replaces the previous single-node format <BuyOnCredit>Y</BuyOnCredit> and provides a more detailed and standardized way to exchange credit-related data between ERP systems and Vendisto.

The implementation remains backward compatible, supporting both the old and new XML formats depending on version. The CustomersImport model has been upgraded to version 2.3, and the updated structure is now fully documented under that version. No changes have been made to the Excel import or export functionality.

These improvements enable seamless synchronization of customer credit information, paving the way for future enhancements where shops will actively use and monitor credit limits during ordering.

Added native support for a language switch dropdown, which can now be configured through the LanguageSwitchMode setting in Raven.

This enhancement allows shops to easily adjust the visual presentation of the language selector, aligning it with the site’s overall design and improving usability for multilingual users.

The Microsoft Navision stock export now correctly includes article variants by applying the Variant_Filter when retrieving inventory data.

This ensures that stock levels are accurately matched to specific product variants, preventing inconsistencies when multiple versions of the same item exist. The improvement enhances synchronization accuracy between NAV and the shop or portal, especially for environments that rely on detailed variant-level stock control.

In Vendisto, Raven indexing is no longer started or stopped during synchronization with the shop. This behavior, originally required for older Raven 3 implementations, is obsolete in Raven 5 and has been removed. The change reduces the risk of sync-related errors and improves overall stability.

Additionally, index creation and cleanup are now managed through a post-deploy script in Octopus, which triggers the new Raven Index Manager. The legacy Elmah logger and profiler have also been completely removed from the shop environment, further streamlining system performance and maintenance.

Resolved an issue where suspended or deleted articles could leave behind residual access permissions on categories. This caused users to see categories without any active products.

The system now properly removes obsolete authorizations, ensuring that only categories containing visible products are displayed to users. This improves the overall browsing experience and keeps category navigation clean and accurate.

In the My Account section of Shoxl shops and portals, users can access a Downloads area containing customer-specific or general downloadable files. Previously, the pagination in this overview was missing, limiting the visible list to a maximum of 10 items.

This issue has now been resolved. Pagination has been restored, ensuring that all available downloads — whether customer-specific or global — are displayed correctly and accessible to users.

Resolved an issue where external article numbers — defined via webshop settings or SQL mappings — were not included in the PlaceOrder JSON payload. This omission specifically affected shipping cost items, causing incomplete or inconsistent order data in certain integrations.

The external article numbers are now correctly included for all order lines, ensuring accurate synchronization with connected systems and consistent order processing.

Resolved an issue where stock validation did not function correctly when using the article table with checkboxes and the “Add selection to basket” button. This caused items with insufficient or zero stock to be added to the basket, even in shops configured to prevent ordering out-of-stock products.

The stock check logic now applies properly within the article table component, ensuring consistent behavior across all product views and preventing unavailable items from being ordered.

Resolved an issue that prevented orders from being placed when article descriptions contained illegal XML characters. These characters caused errors during order export and blocked processing for affected items.

Article descriptions are now automatically sanitized before being written to XML, ensuring that orders containing such items can be placed successfully without manual correction.

Resolved an issue where searching for partial article numbers could result in incomplete or empty search result pages. The search function now reliably returns all relevant matches when users enter fragments of an article number, ensuring consistent and accurate results across all product searches.

Improved the synchronization and clean-up process for outstanding invoice data. In some cases, outdated records were not being properly removed, which could cause incorrect open amounts to appear alongside invoices.

The enhanced data clean-up now ensures that obsolete invoice details are deleted as intended, resulting in accurate and up-to-date outstanding amounts throughout the invoicing overview.

Authorizations can now be applied to article properties, ensuring that properties are only shown to users who have access rights. When authorizations are defined, these are respected across the entire storefront, including product detail pages, filters, and article or group tiles.

The Vendisto API and database have been extended to support creating, updating, and retrieving properties with authorizations. These authorizations are automatically synchronized with the shop through fast-sync. If no authorization is set, the property remains visible to all users.

Note: This functionality is only available for customers with the Authorizations or AdvancedAuthorizations license modules.

Outcome: Properties in the shop are now shown only to authorized users, improving control and consistency while ensuring that existing functionality remains unaffected through regression testing.

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.

Users often want to reuse a composed basket for future purchases without re-selecting items. To streamline repeat ordering, the basket now supports saving its full contents as an order list.

• A new Save as Order List button appears in the basket header (icon placed before the trash/remove-all icon).
• Clicking the button opens the standard dialog to select an existing order list or create a new one.
• From the basket, all items are added to the chosen list in a single action.
• After saving, you remain on the basket page.

This improves speed and consistency for frequent orders while keeping the familiar order list workflow.

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.

We redesigned the ArticleGroupOverview (both tile and table) to use modular building blocks, giving you precise control over what appears where—without forcing everything into a single price block.

• Separate price elements: display From/BeforeDiscountPrice and To/CurrentPrice as independent items.
• Discount badge: show the discount percentage as its own element in both views.
• Logo placement: logo can be positioned as a separate element (also in list view).
• Article label: label can be rendered as a standalone element (tile and list view).

Alongside the layout flexibility, a series of reliability updates improves behavior and consistency:

• Clickable wrappers fixed: the RenderWrapper: true behavior now applies correctly so elements remain clickable as intended.
• Balanced layout: EqualizeHeights is disabled for the new layout to prevent misalignment.
• Variant icon logic: the fast-forward/variant indicator only shows where it is actually relevant.
• Clean list pricing: no “from” price for items that belong to an article group in list view.
• Column composition: multiple elements can share a single column without each getting an extra table-column wrapper (alignment matches the quantity control behavior).
• Add to basket: works correctly when OrderQuantity and OrderButton are placed as two separate elements.
• Responsive structure: the single quantity button now receives the proper responsive-table-col wrapper and stays within the table layout.

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 webshop now supports supplementary articles based on the component module. These supplements are mandatory and can have a defined quantity. They are currently configured via the RelatedArticle XML import.

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 SEO JSON blob occasionally failed. This caused issues when loading the article overview page. The handling of nullable data has now been improved to ensure reliable SEO output and page stability.

The add_to_cart event for Google Tag Manager (GA4) was being triggered twice due to overlapping implementations. The outdated AddToCart event has now been removed, ensuring accurate event tracking for cart actions.

In the category overview using PagingType 1 (classic pagination), the page indicator incorrectly remained on page 1 regardless of navigation. This issue arose after introducing the new “load more” paging method. The display now correctly reflects the active page when classic paging is used.

In the category overview, the "load more" button was incorrectly shown even when all articles were already visible on the initial page. This has been fixed—if there is only one page of results, the button is now hidden as expected.

The webshop now includes structured data (in JSON-LD format) on all major content types to improve SEO and visibility in search engines.

Structured data helps search engines better understand the content of a page, and allows products and categories to be shown more attractively in search results — including pricing, availability, and navigation context.

The structured data is automatically rendered for:

• Breadcrumb paths (via BreadcrumbList)
• Category overviews (as ItemList of categories)
• Mixed article and article group listings (with schema.org Product and ListItem)
• Product detail pages, including brand, description, price, stock and SKU

This enhancement ensures that all available product information is included in a format that search engines can read and index more effectively, boosting both relevance and click-through rate.

It is now possible to automatically post order messages to a configured external endpoint after an order is placed.

This enables further integration with external tools or automation platforms (e.g., Zapier) that can process the message on the receiving side.

Resolved an issue where customer-specific prices and pricelists were not updated every 15 minutes as expected. This was caused by system crashes during frequent synchronizations with Exact.

More frequent updates are now supported, which is especially useful in sectors with fast-changing prices, such as fresh produce trading.

Implemented synchronization of charge items in the Microsoft Navision Batch Interface. This enables the display of deposit and environmental disposal fees — such as Recupel and Bebat — in the shopping basket.

Recupel and Bebat are environmental programs that manage the collection and recycling of electrical appliances and batteries in Belgium. These fees are legally required and shown transparently during checkout.

The product detail page can now display a "from - to price", using the price from the first pricing tier.

This feature is available when a discount is applied — specifically when PriceWithCurrency and OriginalPriceWithCurrency differ. The setting "ShowFromToPrice" must be enabled to activate this display.

Additionally, it is now possible to show the discount percentage, provided this value is supplied by the ERP system.

Type: Boolean
Default: false

The ShoxlRestService has been upgraded from .NET 6.0 to .NET 8.0, as support for .NET 6 has ended.

In addition to long-term support, .NET 8 offers performance improvements, better memory efficiency, and enhanced APIs that contribute to improved stability and maintainability of the platform.

A significant number of outdated and vulnerable packages were removed from the Vendisto.WebServices project in this sprint, improving security, performance, and maintainability.

This update involved a major quality assurance effort to verify stability across all components and integrations.

The cleanup is part of our ongoing process: we continuously allocate sprint capacity to updating and validating third-party dependencies.

Fixed an issue in the Voucher API where users not linked to a specific voucher were still able to apply it. This was caused by an error in the underlying query logic.

Access control checks now correctly validate whether a user is authorized to use a given voucher.

Fixed several issues in the order list view that affected checkbox functionality, including the "Select all" option.

The bugs also impacted automatic behavior related to quantity input and price calculations. These have now been resolved to ensure consistent selection and accurate totals.

Fixed a rendering issue where the prefilter UI block (e.g., for category filters) would not become active when placed on a page using custom tagging.

This update ensures that stepped or hierarchical filter blocks behave as expected, even in custom-tagged page configurations.

Resolved an issue where graduated (tiered) pricing was no longer shown on the product detail page.

This was caused by a change in the price rendering logic, which inadvertently suppressed the display of quantity-based pricing tiers.

Fixed an issue where valid VAT numbers were being rejected during registration of new customers on the French webshop.

The root cause was a failure in the VIES VAT validation service (EU's VAT Information Exchange System). VIES relies on national systems for validation — in this case, the French VAT backend. That system returned a "quota exceeded" error after reaching its request threshold (rate limit), causing VIES to return an empty or failed response.

This failure has now been handled gracefully to avoid blocking legitimate customer registrations when the French VAT service is temporarily unavailable or throttled.

The email address of the user who placed the order is now included in the order data, alongside the customer-level email address.

This additional information is available to all integrations via the OrderedBy field and can be used for tracking, notifications, or reporting purposes.

The DeliveryAddressName field from the F&O OData interface is now mapped to the internal ShippingName2 field in order headers.

This allows more specific shipping destination names (such as internal departments or delivery locations) to be displayed in the webshop's order history.

In the next release, it will be possible to configure this field via the layout settings so it can be shown as the customer name in the order overview.

Classification pages in the shop have been significantly enhanced with new layout capabilities. It is now possible to show not only subcategories, but also all articles from all underlying classification nodes—directly on the classification page.

Three new layout components have been introduced:

• First-level dropdown: A navigational dropdown that always shows the first level of the current classification. It can be positioned freely on the page.
• Subcategory list: A compact block layout of child categories, each with an image and title. The number of visible blocks can be configured, with a "Show all" button to reveal more.
• All articles list: Displays all articles from the selected classification node and its children. This component can replace the traditional subcategory list and can be combined with it for richer navigation.

In addition, a new paging mode is available:

• Load more paging: Instead of numbered pagination, users can incrementally load articles by clicking a "Load more" button. The control shows how many articles are currently shown and how many remain.

These components are configurable per classification node and allow shop administrators to define whether to show subcategories, products, or both. Shop-wide defaults can also be set to define behavior starting from a specific classification depth.

Vendisto already supports advanced authorization logic that allows you to control product visibility per user group. This capability has now been extended to individual article properties, giving you fine-grained control over which users can see which product details.

Authorizations can be configured manually in the Vendisto interface or programmatically via the API. Any changes—such as adding or removing authorizations—are automatically synced to the shop. This feature requires either the Authorizations or AdvancedAuthorizations module to be active.

Example use cases include:

• Show only high-level product features to unauthenticated users, while showing full technical specifications to logged-in customers.
• Display different price labels (e.g., advisory price) to different user groups based on their profile.

Note: This is the first step of a larger rollout. In an upcoming sprint, the shop will begin enforcing these authorizations during display and filtering.

A new option has been added for shop users to hide product prices both in article overviews and on article detail pages. This feature is intended for use in showroom or demo environments where displaying prices may not be appropriate.

The option is only available to authenticated shop users and can be toggled based on the context in which the shop is used.

Tiles in dynamic lists that display news items can now show additional information. New display options include:

• Category
• Subtitle
• Tags
• Source
• A "read more" link

This makes news overviews more informative and engaging for users.

The ArticleGroup Excel import has been extended to support full classification structures, including:

• Multiple classifications per article group
• Multiple categories (nodes) per classification
• Positioning of article groups within each classification node

The format now aligns with the Article Excel import, using dedicated columns for each classification level and position. Depending on the database structure, column names follow the pattern:

• ClassificationLevel[n] and Position — for a single classification and category
• ClassificationLevel[category]_[n] and Position[category] — for one classification and multiple categories
• ClassificationLevel[classification]_[n] and Position[classification] — for multiple classifications
• ClassificationLevel[classification]_[category]_[n] and Position[classification]_[category] — for multiple classifications with multiple categories

This enhancement ensures greater flexibility when importing structured product hierarchies into Vendisto.

A new option has been added to the ArticleGroup import to define how unknown classification paths should be handled during import:

• Enabled: the importer will automatically create the classification path if it does not yet exist.
• Disabled: the importer will generate a validation error for rows with unknown classification paths.

This enhancement offers more control and flexibility when importing data into environments with incomplete or evolving classification structures.

The ArticleGroup import supports Excel files with multiple classification nodes across multiple classifications. To ensure data consistency, the import process now performs detailed validation on all Classification, ClassificationLevel, and Position columns.

If any inconsistencies are found, the import will be aborted. Instead, the system returns the uploaded Excel file with an additional Error message column. Problematic rows are highlighted in red to help you quickly identify and correct the issues.

After importing articles into Vendisto, the classification structure is synchronized to the shop’s performance database. For large classifications, this process runs in multiple batches.

Previously, the synchronization could fail due to timeouts when handling large data sets. To address this, the batch size used during classification structure synchronization is now configurable. This allows for better handling of large imports and more stable processing.

Although VAT rates should ideally be managed in the ERP system, that’s not always feasible—especially for products with different VAT rates across countries. For example, a product might be taxed at a high rate in one country and at a reduced rate in another. Some ERP systems, noticeably Exact Online, lack the flexibility to handle such variations.

To support multi-country shops more effectively, Vendisto now allows regional VAT rates to be defined per product during article group import. This ensures correct VAT handling without relying solely on the ERP system.

The brand filter is no longer a fixed element in the filter UI. Instead, shops are encouraged to use a product property to represent brand—just like any other product characteristic. This provides much more flexibility, including full control over filter placement, visibility, and behavior.

The former hardcoded brand filter offered limited configuration and always appeared in a fixed position. While it is still technically available for backwards compatibility, it is no longer used by default in new shops or templates.

Authorization profiles control the visibility of products and content based on the customer's access rights. Previously, Vendisto allowed these profiles to be managed on both the product and the product variant level.

To simplify profile management and avoid redundancy, support for product-level authorization profiles has been removed. From now on, only product variant–level authorization is used.

As part of this simplification, the related AuthorizationProfile columns have also been removed from the ArticleGroup Excel import and export.

A bug in the basket logic prevented products with only optional extras—where no selection was required—from being added to the basket unless at least one option was chosen. This has been corrected. Such products can now be ordered without selecting any options.

The article selection wizard includes an option to automatically update the main product image when a specific article is selected. This functionality was unintentionally broken due to a recent change, causing the image not to update correctly.

The issue has been resolved, and the gallery image now updates as expected when using the selection wizard.

When viewing a news detail page, a "back to overview" button is shown to help users return to the news list. In some cases, this button redirected incorrectly—leading to a 404 error or the homepage.

This issue has been resolved. The back button now reliably returns users to the correct news overview page.

Articles imported from Exact Online can now reflect the statuses "Temporarily Not Available" and "End of Life". This allows products to be hidden from the shop when they are temporarily unavailable or no longer offered.

Because Exact Online does not natively support these statuses, a custom free field is used to carry this information. To enable the feature, the setting ArticleAvailabilityStatusFreeFieldNumber must be configured by Shoxl. The designated free field should then contain one of the following exact values:

• TemporaryNotAvailable
• EndOfLife

These values will be interpreted automatically during the import process and applied to the corresponding articles in the shop.

We’ve expanded the D365 Finance & Operations interface to support more complete and localized product data management. These enhancements enable deeper integration and improve data quality across systems.

The following additions are now available via OData endpoints:

• Multilingual product category support, including hierarchy structure via:
  • ProductCategories
  • EcoResCategoryTranslationBiEntities
  • ProductCategoryAssignments
• Product-specific attachments and images via:
  • ReleasedProductDocumentAttachments
• Enriched product metadata through article attributes via:
  • ProductAttributeValuesV3

These changes provide better support for multilingual, media-rich, and attribute-based product data across different operational contexts.

The XML Place Order interface now supports CustomOrderFields, which were previously only available via the REST-based PlaceOrder call.

This extension was introduced to support the batch integration with Dynamics 365 F&O, which relies on the XML interface and require access to custom order metadata.

Vendisto now includes a fallback language system for article descriptions during export. When a language code (LCID) is required but not found, the system will attempt to resolve the LCID based on the language code attached to the entity.

If the language cannot be resolved, the first language defined in the system (as configured in Octopus via the Languages variable) will be used as fallback.

This ensures that exports always include a valid language, even when translation data is incomplete. The supported language codes are: nl, fr, fi, de, en.

The Shoxl platform consists of a set of different web applications and web APIs that we continuously improve and extend with new functionality.

To streamline the management of all upcoming features, user stories, and bug fixes, these work items are organized into sprints as part of the Scrum development methodology.

At the end of each sprint, we create a new release for most of our applications. Although we use high-end tooling to support the release process, some tasks still require manual intervention—such as updating internal references between different Shoxl projects.

To reduce this manual effort and accelerate the process, we have started the development of the Shoxl.ReleaseManager. This tool aims to automate those repetitive steps and further streamline our release pipeline.

To ensure complete product data in all languages, Vendisto uses a fallback mechanism that fills in untranslated content—such as classification nodes, product names, variant labels, and image titles—with text from the default language.

The ShopManager tool, used during new shop rollouts, will now automatically configure this fallback language for all non-default languages. This allows shops to launch with full product structure even before translations are available, and translate later at their own pace.

The shop uses Postmark to send transactional emails, such as order confirmations and password resets. These emails are based on templates that can be customized depending on the shop’s license.

During the rollout of new shops, the ShopManager tool automatically creates a corresponding Postmark mailserver account. A bug was causing this account creation to fail. This issue has now been resolved.

The order overview has been upgraded with an advanced view that helps users quickly locate relevant orders through enhanced search, filter, and sort capabilities.

This new view includes:

• Search functionality by order number, customer reference, article number/name, and order date.
• Filters by order status (e.g. All, Open, Delivered, In progress).
• Sorting options on all order-level columns, both ascending and descending.
• Improved paging and significantly better performance.

The search requires a minimum of one character and displays a clear result set, including a customizable "no results" message when applicable. Long result lists include a “show more” option to reveal additional items in batches of 20. A clear filter icon allows users to quickly reset search and filter inputs.

This functionality is only available when the Shoxl ERP caching layer is active and must be explicitly enabled through the LayoutSettings.

In Exact Online, it's possible to define multiple package units for a single article (e.g., units, boxes, pallets). To represent these in the shop, the Exact Batch Interface can create separate articles for each package unit. Each of these receives a unique name—typically the article description followed by the unit size—since Exact does not assign a unique GTIN/EAN to each packaging variation, but the shop requires unique identifiers.

Until now, each of these generated articles was placed in its own article group, resulting in multiple single-item groups. This approach ensured consistency with the shop's structure (which always expects article groups and their variants), but it also meant that no variant selection page was shown.

A new feature now allows these related articles—each with a different package unit—to be grouped automatically together under a single article group using the MapPackageUnits:GroupArticles setting in the Exact Batch Interface. This results in a true variant experience for visitors when multiple packaging options exist.

The article group page then displays all variants, allowing users to choose between package units through icons, a dropdown menu, or a list format—depending on the shop's configuration.