SHOXL
RELEASES

We’ve introduced a deeper integration with product master data in Microsoft Dynamics 365 Finance & Operations, making it possible to manage commercial product content directly from F&O—similar to how a PIM system would operate.

This advanced interface allows for:

• Multilingual product category support and full category hierarchy integration via OData endpoints.
• Access to product images and attachments through ReleasedProductDocumentAttachments.
• Retrieval of article-level attributes via ProductAttributeValuesV3, enabling enriched metadata and filtering.

These enhancements bridge the gap between ERP-managed product data and rich e-commerce presentation, supporting localized content, better filtering, and consistent product experiences across markets.

An OData layer has been introduced on top of the Shoxl Webservices used to retrieve order history data from the ERP cache, the cache we use to store ERP data in the background to speed up retrieval and display.

OData (Open Data Protocol) is a standard protocol for querying and updating data using RESTful APIs. It allows clients to request only the data they need, apply filters, sort results, and handle paging—all using a consistent and widely supported format.

With this new layer, it is now possible to access order history data more flexibly and efficiently. The OData implementation supports advanced filtering, field selection, and pagination (such as skipping or limiting results), making it ideal for integrations and reporting tools.

This feature requires the ERP Cache connector to be active and an API key to be configured for secure access.

The article group import functionality has been extended to support multiple classifications, including the ability to specify article group positions per classification path.

Previously, the import format supported a single Position field, which was not sufficient when dealing with multiple classifications or deeper category structures. With this enhancement, the import can now handle multiple classification paths and assign specific positions within each path.

To achieve this, the import format now allows repeated pairs of fields: ClassificationPath_1, Position_1, ClassificationPath_2, Position_2, etc. These fields map to the ClassificationNodePosition and ArticleGroupPosition values in the ClassificationNodeArticleGroup table.

In systems with multiple classifications, an additional level of indexing is used: for example, ClassificationPath_1_1 and Position_1_1. The first number indicates the classification index, while the second indicates the position within that classification structure.

The classification path includes both the path itself and the name of the classification. The import supports the following scenarios:

• Single classification and single category
• Multiple categories within a single classification
• Multiple classifications
• Multiple classifications with multiple categories

After the import, all updated article group positions are automatically synchronized to the shop.

Vendisto supports assigning an article group to multiple classifications when configured accordingly. However, the bulk Excel import function in the PIM encountered an issue when different classifications contained identical node names at the top level of the structure.

This caused the importer to match article groups with the wrong classification, which in turn resulted in incorrect categorization and—in some cases—a generic "Unknown error" during import.

This problem has now been resolved. The import logic has been updated to correctly distinguish between identical node names across multiple classification trees, ensuring accurate classification assignment during bulk import operations.

Shops often receive background traffic from search engines that scan and index product and content pages. In certain cases, this indexing activity caused unnecessary load, which could lead to performance degradation or temporary unresponsiveness.

This issue has been resolved by optimizing the way such traffic is handled. The shop now processes background indexing more efficiently, maintaining stable performance even during periods of intensive crawling by search engines.

In Exact Online, it's possible to assign the same email address to multiple contacts within a single customer account. This can lead to duplicate user creation attempts when ImportContactMode is enabled, as each contact would trigger the creation of a user with the same email and user ID—causing import errors.

To resolve this, a deduplication mechanism has been implemented. When ImportContactMode is not set to None, the system will now create exactly one user per unique email address within a customer, based on the combined set of the main contact and associated contacts.

Email addresses must always be unique within a single customer. This is necessary because email can be used as a login credential in the shop. The Shoxl platform supports login via either debtor number or email address—but email-based login only works correctly when the address is unique within the customer's scope.

An email address may appear in multiple customer accounts. If a user logs in with such an email address, and that address is linked to several customers, the system will prompt the user to select the correct account from a list.

This enhancement ensures a consistent import process, prevents duplicate user errors, and guarantees correct login behavior based on unique user identities.

In the Vendisto platform, users—not companies—log in to the shop. When a customer is imported without any associated contacts, a default user is automatically created to enable login.

Previously, if contact data was imported at a later stage, Vendisto would create a user account for each contact and delete any users not included in the import—based on the assumption that the contact user list was complete. As a result, the initially created default user was removed.

This caused confusion for customers who had already started using the shop with the automatically created default user account. Once contacts were supplied, the default user could suddenly no longer log in, even though the credentials were still familiar to the customer.

This behavior has now been corrected. The system will preserve the default user that was created during the initial import, even if contacts are imported at a later time. This ensures uninterrupted access for users who were already logging in before contact data became available.

Resolved an issue in the quote request flow where the payment method was automatically preselected as "Buy on Credit" if it was available for the customer. If this method had a configured payment discount, the discount was incorrectly applied during the quote process—even though no actual payment was being made at that stage.

This caused unintended pricing behavior and confusion during quoting. The logic has been adjusted so that payment discounts are no longer applied in the quote flow.

As a result, quotes now reflect the correct pricing without prematurely factoring in payment-related discounts.

The Microsoft Navision Batch Interface has been updated to correctly handle non-product order lines, such as shipping costs.

Previously, all order lines—including cost lines—were assigned a LocationCode. However, Navision does not support location codes on non-inventory items, which caused the order to be rejected with an error.

The system now omits the LocationCode for lines that are not linked to physical products, ensuring smooth order processing in Navision.

The PriceList export in the Batch Interface has been updated to correctly support multiple currencies per item. Although the XML format already allowed this, the internal implementation did not fully process prices defined in different currencies.

With this improvement, customer prices can now be exported with multiple currency values—for example, both USD and EUR—within the same export block. Each NettoPricePerItemExclVat and DiscountAmountPerItemExclVat field includes a Currency attribute to clearly indicate the applicable currency.

This enhancement enables better international pricing support and integration with systems that require multi-currency price structures.

A bug has been resolved that affected the interaction between quantity selection and the "Add to Basket" button in order lists (used to manage favorites).

Users could increase or decrease the quantity using the plus/minus buttons, which correctly activated the "Add to Basket" button. However, when entering a quantity manually via keyboard input, the button became inactive—preventing the product from being added to the basket.

This issue has been fixed. Both manual input and use of the plus/minus controls now consistently activate the "Add to Basket" button, ensuring smooth ordering from order lists.

Resolved an issue in the Exact Batch Interface where the Customer Price export incorrectly applied an exchange rate conversion based on the article’s default currency, rather than the currency specified for the actual customer price.

This resulted in prices being exported with unintended currency conversions, leading to incorrect price data being returned to the shop or external systems.

The export logic now correctly uses the currency associated with each price entry, ensuring that no unnecessary or incorrect exchange rate conversions are applied.

Resolved an issue in the shopping basket where the total VAT amount was not recalculated after increasing the quantity of an item.

This caused the displayed VAT to remain incorrect until the page was refreshed or reloaded. The logic has now been corrected to immediately update the VAT total in real-time when quantities are adjusted, ensuring accurate tax display at all times.

Product images in the Shoxl shop can be uploaded and managed directly in Vendisto. Some customers, however, manage product images externally and reference them using image URLs instead of uploading them.

Previously, the synchronization from Vendisto to the Shoxl performance database did not correctly process externally hosted image URLs. As a result, images were sometimes missing on the product overview pages, even though they were visible on the article group page.

This issue has now been resolved. Images provided via external URLs are now properly handled during synchronization and consistently shown in all parts of the shop.

A bug in the Vendisto article import process caused classification nodes to be matched using their title instead of their internal name. This led to the creation of duplicate nodes whenever the displayed title differed from the system name.

This issue has now been fixed. Classification nodes are correctly matched based on their name, preventing unintended duplicates during import.

Resolved an issue where downloadable files could not be saved correctly in Vendisto when the user interface language was set to anything other than Dutch.

This problem was caused by language-dependent handling in the file creation process. The logic has now been corrected to ensure that downloads function properly regardless of the selected UI language.

On both the article group overview page and the article group detail page, articles can be added directly to the shopping cart when the Quick Order functionality is enabled. The presence of elements such as the order button, pricing, product features, and stock information may vary per article group.

To ensure a clean and consistent layout, technical improvements have been made. Article cards now maintain equal height without relying on scripts, regardless of which elements are shown.

On article group overview pages, article groups with only one article can be ordered directly and typically show stock availability. When an article group contains multiple variants, users must first navigate to the detail page to select and order a variant.

In some cases, when both types of article groups were shown together in the same overview, the stock status was not displayed for groups with just one article—despite it being possible to show it there. This has now been corrected: stock information is displayed consistently for article groups with a single article.

Previously, the Exact Online integration included a setting that enforced ordering in the highest packaging unit when multiple units were defined for an article. In the webshop, this could be displayed in two ways: either purchasing in the largest packaging unit with its corresponding price, or purchasing per base unit with a calculated unit price, while requiring a multiple of the packaging quantity.

This approach has now been replaced by a more flexible and transparent setup. In Exact, you can now define a minimum number of base units per order, as well as the increment in which the item must be purchased. Additionally, if multiple packaging units are specified for a single item, each unit is now shown as a separate article in the webshop.

This change eliminates the need for the old ‘PriceUnitType’ setting and simplifies both setup and ordering logic.

In the upcoming release, articles representing different packaging units will automatically be grouped into a new article group. The minimum order quantity setting will continue to apply when ordering per base unit.

Static product lists embedded in content pages can now display the full order interface, including the order button and quantity selector.

This ensures consistent ordering functionality, regardless of where the list is used within the webshop.

The ArticleGroup Excel export has been updated to support both multiple classifications and multiple category assignments per classification.

Instead of using a single 'Classification Path' column with slash-separated values, the export now follows the same structure as the article export. Classification and level data are split into separate columns using a structured naming convention.

This includes:

• Level_[category position]_[n] for single-classification setups with multiple category levels
• Level_[classification position]_[n] for multi-classification setups with one category per classification
• Level_[classification position]_[category position]_[n] for combined cases

The export also includes corresponding Classification_[n] columns to identify classification roots, enabling full import compatibility.

Vendisto now supports the import and display of customer-specific VAT rates.

This allows tailored tax handling per customer, based on external system configuration.

Uploading images in Vendisto would fail when the filename already existed, even if the upload was valid. This blocked users from replacing or updating existing images via the UI.

The issue has been resolved, allowing seamless uploads regardless of whether the filename already exists.

In environments where multiple shops are connected to a central PIM system—each with its own local (slave) PIM—it is now possible to block article data from being imported into the slave system.

This allows shops to import only locally relevant data, such as lifecycle status, while excluding centrally managed product content from the article XML feed.

It is now possible to place orders to Vendisto using the BuyOnCredit payment method in environments with multishop configuration.

This extends compatibility of the BuyOnCredit method with newer order routing logic across shops.

The ShippingCostAPI now correctly falls back to the general shipping cost configuration when no specific rates are defined for a user's linked pricelist.

This fallback already applied to guest accounts and is now consistently applied to all user types.

In certain configurations involving article groups and the article selection wizard, external image URLs were not displayed correctly. This was partly due to invalid characters in the image paths.

The handling of external images has been improved to ensure they are now properly shown in both overview and detail pages, regardless of the component combination used.

Users with full access rights were previously unable to open quote details, despite having the correct permissions.

This has been resolved so that authorized users can now view all quote details as expected.

News categories consisting of multiple words were not filtered correctly in the webshop. As a result, clicking on such a category did not always return the expected articles.

This issue has been resolved. News category filters now work properly, regardless of the number of words in the category name.

When a classification node or product is renamed in Vendisto, the corresponding shop URL changes. The previous URL is then stored as a historic reference, intended to automatically redirect to the updated URL.

A bug in this redirection process has been resolved. Historic URLs now reliably redirect to the correct new location when accessed by users.

When a classification node or product is renamed in Vendisto, the corresponding URL in the shop changes. The system automatically registers the old URL as a historic reference.

If a user accesses the old URL, the shop now correctly redirects to the updated URL.

An XML-based import option for product relations has been added, following the same structure and behavior as the existing Excel import.

This allows external systems to synchronize product relationships in a single step, without leaving outdated data behind.

The Microsoft Navision integration now supports ordering article variants. Previously, variants were not available in the webshop when using this ERP connection.

This enables full support for product variant structures in both browsing and order processing.

Within the Microsoft Navision integration, variant articles managed now support fallback pricing. If no price is defined for a variant, the system will automatically use the base article’s price.

This ensures consistent pricing behavior, even when variant-specific prices are omitted in the data source.

When logged in as a representative, the user dropdown menu now correctly displays 'Choose another customer' instead of 'Sign out'. This matches the behavior already present in the customer portal.

Previously, when a user switched from 'List View' to another display mode (such as 'Tile View'), the setting would revert back to the default view after applying a filter.

This behavior has been corrected. The selected display mode now stays active when filters are used.

In cases where a product had no image of its own, the webshop would automatically use the image from the first variant during synchronization to the performance database.

This mechanism did not trigger when the main product had a PDF document but no image. This has now been corrected: images from variants are once again used as fallback, even if a PDF is present at the main product level.

The view_item event in Google Tag Manager was not triggered in certain cases, causing product views to be missed in tracking.

This has been corrected so the tag now loads reliably across all relevant pages.

Orders that included component articles were incorrectly flagged as failed during the purchase tracking step. This led to confusion in order confirmation reporting.

The logic has been updated to properly recognize and process these types of orders.

When a guest account places an order, the integration between the shop and Exact Online can automatically create a corresponding customer record.

Previously, these records were created without a country setting, causing Exact to apply the default country code 'NL'—even for international customers. The country is now correctly derived from the invoice address.

The article table component could fail to render when the layout included AccumulatedProperties and one or more articles had no properties defined.

This scenario is now handled gracefully, preventing layout errors in such cases.

With the Authorized Contents Template, you can show different content to different users or user groups based on their authorization profiles. Here's how it works:

A content block is linked to a specific authorization profile. Customers or customer groups are also linked to authorization profiles. After logging in, a customer will only see the content for which they have access according to their assigned profile. This allows you to deliver highly personalized content experiences within the webshop.

This mechanism operates in the same way as product authorizations in Shoxl: the system can be configured so that users only see the products linked to their authorization profile. With Shoxl’s authorization features, you can effectively offer every user their own personalized version of the shop.

We also fixed several issues related to the handling of authorized content blocks, ensuring that authorized content is now correctly displayed according to user profiles.

Dynamic content in Vendisto allows you to add product-specific information directly to product pages. It works by defining a layout with content blocks, where each block is linked to an editor in the "Dynamic Content" tab within the Vendisto CMS for that product. This gives you maximum flexibility to enrich product pages with tailored content.

Previously, a bug in the classification module prevented users from adding new subclassifications when dynamic content was active. The save button remained disabled, blocking the addition of new classification nodes. This issue has now been resolved, allowing full use of both classification management and dynamic content editing.

We introduced a new configuration option to tailor how stock information is shown to different user types. In the webshop settings, you can now define separately for anonymous visitors (passers-by) and logged-in users whether they see:

• ColorIcons (stock status through color icons)
• Numbers (exact stock quantity)
• ColorIconsAndNumbers (both status and quantity)

This allows you to offer more detailed stock insights to logged-in customers while keeping information for anonymous visitors more general.

Google Tag Manager (GTM) simplifies managing tracking scripts on websites. Previously, enabling the "MeasureViewBasket" setting could cause crashes in the shopping basket when handling products composed of multiple components.

The GTM tracking code has been updated and now correctly processes these bundled products.

We've introduced the option to set distinct MultiSafePay API keys per country, based on the customer's invoice address. This enhancement provides greater flexibility in managing your payment processing across different regions.

Support for the Polish payment method Przelewy24 has been added to the webshop settings. You can now easily enable and configure this option for your customers during checkout.

The various F&O endpoints now provide timestamps along with their data. This improvement enables our caching layers to selectively import only updated records, making data synchronization faster and more efficient.

Microsoft Dynamics 365 F&O is highly configurable, which can lead to variations in how data is structured between customers. We have now developed a generic mechanism that interacts directly with the oData layer, making it possible to support multiple F&O setups without the need for customer-specific adjustments.

We resolved several issues that occurred when paging through search results after applying a price filter. Previously, the minimum and maximum prices set via the slider or input fields were incorrectly converted to integer values after moving to another page.

Now, the minimum and maximum price values remain accurate throughout navigation, and are correctly based on CustomerPrices or PriceList prices when applicable.

Some webshops use multiple classifications within the Vendisto PIM to manage different storefronts from a single system. Previously, these classifications were stored in a random order, causing the default PIM classification to not always appear first.

We have now introduced a mechanism to position classifications in a logical sequence in the database, ensuring consistent and predictable ordering.

Postmark is a reliable email delivery platform used by Shoxl to ensure smooth and dependable email communication. When placing a pickup order as a guest user, the confirmation email previously showed the customer's invoice address instead of the store's pickup address.

This has now been corrected. Confirmation emails for pickup orders placed by guest users clearly show the correct store pickup address.

A robots.txt file instructs web crawlers (search engine spiders) which pages or files they should or shouldn't access on your website. By default, the Shoxl platform automatically generates this file to ensure essential directives are always included.

We've introduced greater flexibility: You can now manually create your own robots.txt file. When this custom version is present, the platform will no longer overwrite it, giving you full control over specific crawler instructions.

Category pages previously experienced crashes when articles contained properties defined in multiple languages. This issue has been resolved, ensuring category pages remain stable regardless of language-specific attributes.

In Shoxl, article tables are fully configurable: you can define exactly which columns are shown by using our layout language — the same language used to design overall page layouts.

Previously, columns in article tables could get stuck on "loading" when viewed by users who were not logged in. This issue has been resolved. Additionally, a new LogInToView layout setting has been introduced, allowing any column to display a login button instead, redirecting anonymous users to the login page.

In Vendisto, images can be managed at different levels of the product structure: at the product variant, product, or classification node level. The webshop displays these images on the relevant pages and, when a product image is missing, automatically substitutes it with the image from the first product variant.

A bug that sometimes prevented this substitution from occurring has now been fixed. All article groups now correctly display an image in the overview, even when a direct product image is missing.

Delivery schedules can include overrides to block specific dates from being selectable. A bug previously caused some of these overrides to be ignored, allowing blocked dates to appear as available. This issue has now been fixed, and all exceptions are correctly enforced.

Previously, it was not possible to add an article composed of multiple components to the basket together with one of its standalone components. This issue has now been resolved, allowing both the bundled article and its individual components to be added to the basket simultaneously.

In Vendisto, the Batch Upload function for images could crash when uploading more than 100 images at once. This issue has been fixed, ensuring smooth and reliable uploads even for larger batches.

When ordering an article with components, using the back button from the basket did not correctly restore the selected configuration. As a result, the article page failed to load the appropriate price and stock information. This issue has been fixed, and returning to the article page now fully restores all selections and displays accurate data.

We developed a more memory-efficient version of the article export function, reducing server load when exporting articles to Excel. During this update, we also fixed a bug where articles imported from the ERP system without a Title element were unintentionally omitted from the bulk export. All articles are now correctly included in exports, regardless of title presence.

To prevent outdated data from being served, we've introduced an "expire after" setting (in hours) for cached responses from the Product and Product Group APIs. This ensures that order book information remains fresh and up-to-date without requiring manual cache clearing.

We fixed an issue where the Country field on the customer registration form was not always visibly marked as required, even though it was technically mandatory. The form now clearly indicates that the Country field must be completed.

We fixed an issue where products that had a customer-specific net price but no gross price could not be added to the basket. The order button now correctly becomes active as long as a valid customer-specific price is available.

We've optimized the synchronization process for images and other assets between Vendisto and the shop. Updates are now faster and more reliable, ensuring that new and updated product images are reflected in the webshop with minimal delay.

The basket encountered issues where removing a bundle item did not properly remove the associated product due to a flaw in the basket logic.

This behavior has been corrected. When a bundle is removed, the associated product is now correctly deleted from the basket as expected.

In Vendisto, new relation types, such as "replacement" or "complementary," can be defined. These relation types are categorized either as "related" or "component."

Previously, a timing issue in the Vendisto UI made it difficult to add related items correctly. This experience has been improved: the "Add Related Product" button is now more responsive and reliably available when setting up new relations.

This enhancement streamlines the process of linking related products, making it faster and more intuitive for users.

Channable is an online feed management and automation platform that helps companies distribute their product data to marketplaces, comparison websites, and advertising platforms. Within our setup, Channable connects directly to our generic Product API to retrieve product information for feed generation and distribution.

We have enhanced the AutomaticProductImportManager tool by introducing a small parser that supports dynamic placeholders in filenames. The available placeholders are:

• {TIME}
• {DATE}
• {DATETIME}
• {TIMESTAMP}

These placeholders allow greater flexibility: feeds can now have either dynamic filenames (based on the timestamp or date) or static filenames, depending on the configuration.

This improvement simplifies integration with platforms like Channable and provides more control over feed file management.

The article XML file forms a crucial part of the automated data stream between ERP systems and the shop. Imported article data is stored in the Vendisto PIM database, which then synchronizes with the shop.

Within Vendisto PIM, article data can be enriched with additional properties and assets, such as images and documents. Articles can also be activated, suspended, or deleted through the concept of a "lifetime state."

We have enhanced the Article XML import functionality by introducing a new setting: ArticleDefaultLifetimeState. This new feature allows users to define a default lifetime state for newly imported articles if the state is not explicitly set in the XML. Previously, new articles without a specified state were automatically set to 'Active'. Now, administrators can configure whether such articles should default to 'Suspended', offering greater control over article activation workflows.

This functionality was developed in response to customer needs for better control over article visibility immediately after import.

During article imports, merging two article groups while simultaneously updating their group names could incorrectly trigger a validation error. This situation has now been improved to allow both operations to be performed smoothly without errors.

VAT rates are typically determined based on the region to which goods or services are delivered. However, in some business cases, VAT handling needs to be adjusted on a per-customer basis. For example, special VAT agreements may apply to educational institutions, healthcare providers, export customers, or resellers operating under specific tax exemptions.

To address these needs, we are extending the platform to support customer-specific VAT rates. The foundation for this functionality has now been laid: customer-specific VAT percentages can already be stored in the Vendisto database, and the Exact Batch Interface has been extended to import these rates from Exact systems.

This enhancement paves the way for even more flexible and accurate tax handling across different customer groups.

Previously, the free delivery threshold did not consistently account for discounts, which could lead to incorrect eligibility for free delivery. This behavior has been improved: discounts are now correctly factored in when calculating whether an order meets the free delivery conditions. This adjustment ensures a more accurate and fair application of delivery policies for all customers.

Some products were not orderable because the basket button on certain article detail pages contained an incorrect link. This resulted in users being unable to place orders directly from those pages.

The issue has been corrected. The basket button now properly links to the ordering process, ensuring that products can be added to the basket without problems.

Navigating from the sidebasket now correctly points to the selected variant instead of the default product.

Cloudflare's Rocket Loader is a feature that improves website performance by optimizing the loading order of JavaScript. It asynchronously loads scripts and prioritizes page rendering, helping to speed up the initial display of content for users.

However, Rocket Loader can sometimes interfere with custom JavaScript functionality by changing the execution order of scripts. This caused issues with our webshop's scripting behavior.

We have now added support to ensure that the webshop runs correctly alongside Cloudflare’s Rocket Loader optimization, maintaining full functionality without scripting conflicts.

Users were unable to reorder items from their order history due to an error in the Shoxl REST service layer. This issue interrupted the reorder process, preventing customers from quickly duplicating previous orders.

The problem has been corrected, and the reorder functionality now works as expected, allowing users to easily place repeat orders from their history.

The "lists" functionality allows article and article group lists to be displayed at various positions in a Shoxl shop or portal. Depending on the chosen configuration, these tiles can also show article attributes and (gross or customer-specific) prices. If prices are not yet available, a "loading..." placeholder is shown temporarily.

However, if prices could not be retrieved or were not allowed to be displayed, the "loading..." placeholder would remain visible indefinitely, causing confusion.

This behavior has been improved. The placeholder is now properly removed when prices cannot or should not be shown, ensuring a cleaner and clearer user experience.

In earlier setups, images imported from Exact Online required a file extension (such as .jpg or .png) to be included in the asset name. Without this extension, the system could not correctly recognize or handle the imported files.

We have improved this process: the file type is now automatically detected based on the content header of the imported asset. This means that manual addition of extensions is no longer necessary, making the import process more reliable and user-friendly.

This enhancement simplifies asset management and reduces the risk of import errors, improving the overall efficiency of product data handling.

One of the essential principles of the Shoxl platform is that the shop does not duplicate functionality already present in the connected ERP system. This approach ensures consistency, simplifies maintenance, and avoids potential conflicts between systems. It also means that, especially when completing an order, the shop should ask the ERP whether any additional costs or discounts apply. This communication happens via the CalculateOrder request.

An issue had arisen where the CalculateOrder request incorrectly added a null entry to the list of order lines.

This behavior has now been corrected, ensuring clean and accurate communication with the ERP system for a reliable calculation of the final order.

OAuth2 is a widely used standard for secure authorization. It enables users to grant limited access to their resources on one site to another site without exposing their credentials. OAuth2 plays a crucial role in modern authentication flows by ensuring secure and manageable access to protected APIs and applications.

To enhance the configurability and ease of deployment of our OAuth2 server, we have expanded the available logging functionality. This improvement provides better insight into authentication flows and system behavior, making it easier to troubleshoot and fine-tune configurations during deployment and maintenance.

Within the Shoxl platform, several generations of CSV upload processing have been developed. The latest generation significantly improves speed and efficiency. This advanced method has now also been applied to the Order Book functionality.

The Order Book allows customers to download a fully configurable Excel file that lists their personalized product assortment. Customers can easily compile a new order by filling in quantities for the desired products and uploading the file again. The selected items are automatically placed in the shopping basket in the specified quantities.

We have introduced the 'EnableFastCsvUpload' setting for the Excel Order Book, ensuring faster and smoother handling of uploads for even the largest customer catalogs.

The products and product variants in Vendisto are structured within a classification tree that can span multiple levels, depending on the shop configuration. Images can be assigned at different levels: Product, Product Variant, or Classification Node.

When a product lacks an image, the shop previously displayed the image from the first product variant. Similarly, a classification node without an image would inherit the image of the first product classified beneath it. Higher-level nodes would inherit from the first child node.

We have now enhanced this mechanism: product variants' images are properly propagated upwards to ensure products and classifications always display a relevant image when no specific image was assigned.

The structure for products and variants allows assigning images at multiple hierarchy levels. In cases where no image was available for a product, a fallback mechanism ensures an image is still displayed, pulling from associated variants or classifications.

An improvement was made to strengthen this fallback logic, ensuring that images are accurately inherited from lower levels when needed. This change enhances the visual consistency across the storefront, even when direct images are missing.

Vendisto organizes products into a tree structure with classifications. Images can be attached at the product or classification level. If an entity had no assigned image, the system would fetch the first available image from linked articles or classifications.

We refined this inheritance behavior to better handle missing images, ensuring that the first available product variant image is now properly displayed at higher classification levels when necessary.

A Shoxl shop features an article group overview page that lists all article groups. This overview is available in both List View and Tile View. If an article group contains only one article, that article can be purchased directly from the overview page (if configured accordingly). For article groups with multiple variants, the number of available variants is shown, and users must click through to select a variant before purchasing.

When the overview included both single-article groups and multi-variant groups, a problem occurred: no prices were displayed for the articles that could be purchased directly. This happened because the rendering logic was inconsistent depending on whether a row contained an article or an article group. The layout would also misalign columns.

We improved the rendering logic to ensure that prices are now correctly displayed in all cases. The layout has also been harmonized so that all rows contain a consistent number of columns, ensuring a clear and uniform presentation.

In previous versions, optional components linked to articles were not correctly added when users compiled order lists. This led to incomplete orders being created when optional items were expected.

The handling of optional components has now been improved. When articles are added to an order list, any optional components selected by the user are correctly included, ensuring a complete and accurate order list experience.

A bug was fixed where articles could be added to an orderlist without selecting mandatory components. This ensures that all required fields are now properly validated before items are added, preventing incomplete or incorrect entries.

When using the quote functionality, users who were already logged in could sometimes incorrectly see the "log in and order" button. This behavior has been corrected to ensure a smooth flow.

Additionally, the product overview was unable to display the "request quote" button and defaulted to showing the standard order interface. We have improved this behavior: the overview can now correctly show a mix of "request quote" buttons and standard ordering options, depending on the individual article settings. This update has been applied to both the list view and the thumbnail view.

Resolved an issue where the news overview incorrectly included archived news items. This resulted in the display of outdated content, incorrect filter counts, and misleading category options. The filter now exclusively shows active, published news items to maintain content relevance and clarity for users.

We identified and corrected a bug in the handling of delivery dates during the checkout process. Customers were previously able to select a delivery date that would later be rejected when finalizing the order, making it impossible to complete purchases for certain dates. This issue has now been resolved to ensure a seamless and reliable order placement experience.

To optimize pricing data storage and handling, the ErpCache price service has been enhanced. In addition to detailed pricing per customer and product, it now supports customer-specific discounts applied at the product group level, based on the standard price list prices.

This improvement reduces the amount of data needed, particularly in cases where customers are assigned to groups with defined product group discounts, minimizing storage load while maintaining accurate price calculations.

The shop includes a setting that determines which net price is displayed on search result tiles after filtering or searching. For products with multiple quantity discount prices, this setting allows the system to show either:

• The lowest cumulative discount price
• The price of the cumulative discount with the lowest quantity (the unit price)

Previously, the net price filter did not follow this setting, leading to inconsistencies in price display. This has now been corrected—the net price filter will now respect the configured setting, ensuring consistent price representation across the shop.

The shop now supports the Finnish language, allowing users to navigate and interact with the platform in Finnish.

This enhancement improves accessibility for Finnish-speaking customers and ensures a better user experience in their preferred language.

Currently, the Shoxl shop sends various emails, including contact form confirmations, password reset emails, order confirmations, and quote-related messages. These emails are sent through a mix of external mail services and internal mail servers.

To improve efficiency and reliability, a dedicated email microservice is being developed. This new service will centralize all email sending, ensuring better management and consistency.

The initial development has started in this sprint, with full functionality planned for upcoming releases. A key benefit for shop administrators will be the ability to customize all email templates directly.

Previously, gross prices were incorrectly retrieved due to a mix-up in DataareaId values. Price calculations for gross prices also relied on the PriceAgreement entity, which could pull data from multiple divisions. If the system was set to retrieve price agreements from both Division A and B while gross prices were only meant to come from Division A, the final price calculation mistakenly included prices from Division B as well.

This issue has now been fixed by ensuring that only price agreements that match the same Division ID as the gross prices are considered in calculations.

Gross prices were not being exported because of missing permissions on the TaxEntity. This entity is required for gross price calculations, and without proper access, the export process failed.

Another issue was that price currencies were not handled correctly. The exporter only supported a single currency instead of multiple, limiting its functionality.

Solution:

• Permissions to the TaxEntity have now been granted, ensuring proper gross price calculation and export.
• The exporter now correctly supports multiple currencies, resolving the limitation.

These fixes ensure that gross prices are now exported correctly and without restrictions.

The batch interface for F&O relies on OData metadata to determine which entities and fields can be accessed. When a customer modifies the standard entity configuration by adding a new field, the locally cached metadata must be updated by retrieving the latest version from the customer's backend.

To streamline this process, the batch interface now includes a recovery mode. When an OData error is detected, the recovery mode automatically downloads the updated metadata and replaces the outdated cache. This ensures that changes in the customer's entity configuration are handled dynamically without manual intervention.

In the Shoxl cache, pricelists and price agreements result in storing a price for every combination of user, article, and quantity. While this setup ensures very fast response times, it can also lead to extremely large databases when dealing with a high number of users, multiple pricelists, and extensive quantity discounts.

To address this, an initial improvement has been implemented where the cache now utilizes pricelists more efficiently. This approach helps reduce database size while maintaining fast performance. This feature will be GA in the next release.

Sales representatives associated with a customer are now included as Global Access Users in the BatchCustomer export for Microsoft Navision Batch Integration. Additionally, an option has been introduced to configure Global Access settings.

In the customer interface, a salesperson_code is used. The question remains whether NAV can also provide an email address for each salesperson. If not, the system will map salesperson codes to email addresses or names that still need to be retrieved from FACE.

Furthermore, it is now possible to manually assign representatives to each customer. A combination of both automated retrieval from NAV and manual assignment should work seamlessly.

Permissions for sales representatives and regular users can now be managed during shop deployment, with Access Users being identified by their email addresses.

The quote overview was missing when a user had no permissions assigned. This led to confusion, as users without explicit quote-related rights were unable to see any relevant information.

To improve this, the system now ensures that users without specific quote permissions can still access the quote overview if they have general access.

This adjustment enhances transparency and provides a more consistent user experience.

Previously, the order history displayed incorrect VAT amounts due to a miscalculation. The system mistakenly used a percentage range of 0-100 instead of the correct 0-1 range when applying VAT to order totals. As a result, instead of adding 21% VAT, the system multiplied the total amount by 21.

This issue has now been resolved, ensuring that VAT is correctly calculated and displayed in the order history.

A new version of CalculateOrder (/V2/CalculateOrder) has been implemented, which supports decimal quantities. This allows more flexibility when processing orders that require non-integer values.

The system now determines which version to use based on the setting ShoxlRestCallV2CalculateOrderMethod:

• If set to True, /V2/CalculateOrder is used.
• If set to False, the system falls back to /V1/CalculateOrder.

This enhancement ensures better handling of decimal order quantities while maintaining backward compatibility.

A new option has been added to control the loading of price, stock, and order interfaces for items in static lists. This setting allows administrators to enable or disable price calls on these lists.

By disabling price calls, this feature helps reduce the load on slower back-end systems, improving overall performance and responsiveness.

Previously, the customer import process in Vendisto could cause duplicate pricelist records to be created in the database. This led to inconsistencies in price authorizations and potential pricing errors.

This issue has now been resolved, ensuring that the import process correctly checks for existing records before adding new pricelist authorizations.

When using the article selection wizard, the price and order UI did not load when clicking on the main image or link from an article group overview. This caused important product details such as SKU, price, and stock information to be missing from the page.

This has been corrected, ensuring that all relevant product details are properly displayed when navigating from the article group page.

Contact forms were not appearing after the page loaded. This issue was caused by the system failing to use the DefaultForm while, at the same time, attempting to validate custom form fields only on form submission instead of during page load.

The implementation has been adjusted to ensure that form validation occurs correctly during the page load process, allowing contact forms to display as expected.

Certain user pages did not redirect to the login page when accessed by a non-logged-in user. Instead, these pages either displayed an error message or redirected to the homepage, causing confusion.

This behavior has now been corrected. Users who attempt to access restricted pages without being logged in are now properly redirected to the login page.

During Exact Online’s scheduled maintenance window (4:00 - 5:00 AM), the system was generating unnecessary email notifications due to service unavailability.

To prevent this, email notifications in the Exact Batch Interface have been disabled for specific HTTP responses, such as Service Unavailable. This ensures that only relevant alerts are sent, reducing unnecessary notifications.

It is now possible to apply authorization profiles to the OrderBook Excel download. This ensures that every user gets a personalized catalog, containing only the products they are authorized to see.

Since this Excel file can also be used to upload an order, this improvement helps streamline the ordering process while maintaining the correct access restrictions. Additionally, a loading spinner has been added to provide better feedback during the download process.

The search engine now supports exact match searches by using quotation marks (""). Previously, the system automatically added wildcards to every search term, which sometimes led to too many results.

With this update, users can now search for an exact phrase by enclosing it in quotation marks. This provides more precise search results, ensuring that only exact matches are returned.

A bug prevented redirects from functioning correctly if they did not include a classification (e.g., /NL/). This issue has now been resolved, ensuring that such redirects work as expected.

However, redirects for existing pages will not work. This is because the system always checks whether a page exists before looking for a redirect. If the original page is still present, no redirection occurs. This behavior follows best practices to ensure that valid pages remain accessible while only missing pages trigger redirects.

Previously, Vendisto automatically converted all relative URLs in the Visual Page Editor into absolute URLs by prefixing them with the Vendisto domain. This caused issues when copying and pasting links within the editor.

This behavior has now been corrected. Relative URLs will remain unchanged, ensuring that links function as expected without being altered unnecessarily.

The API now allows full management of OAuth2 audiences, providing more control over application access levels. Users can create, read, edit, and delete audiences directly via the API, making it easier to adjust authentication settings as needed.

Additionally, a new overview and search function has been added, enabling users to quickly find and manage existing OAuth2 audiences within the system.

A bug caused classification documents to be overwritten when new menu items were added. Additionally, catalog pages could disappear when synchronizing data from the central PIM to multiple shop instances.

This issue has now been resolved, ensuring that classification documents remain intact and catalog pages are preserved during synchronization.

A bug caused English-language resources to be missing from the asset dropdown in Vendisto, making it difficult for users to select the correct assets in an English-language environment.

This issue has now been resolved, ensuring that all necessary resources are available in the dropdown as expected.

The system now utilizes the ArticleOrderConfiguration entity in Microsoft Dynamics F&O to enforce minimum order quantities and addition quantities per product. This ensures that products can only be ordered in predefined increments, improving consistency and preventing incorrect order quantities.

This update also integrates these settings with the gross price per product, ensuring that pricing calculations align with the configured order quantities in Microsoft Dynamics F&O.

When placing an order, some fields that cannot be modified from outside the system should be changed. As a workaround, users can refresh metadata using one of two methods:

1. Start the batch interface with the --clearMeta parameter.
2. Manually delete the metadata file (Metadata.trimmed.xml) from the system folder and restart the batch interface.

This ensures the correct value is applied without manual intervention.

• Delivery Scheme Overrides Now Applied Correctly
  Webshop users can now successfully apply overrides to the default delivery scheme. Previously, an issue prevented this, but correct delivery settings are now enforced.
• Accurate Delivery Schedule Retrieval
  A date format issue occasionally caused incorrect delivery schedules to be displayed. This has been resolved, ensuring visitors always see the correct schedule.
• Improved Date Validation in Delivery Schedule API
  The delivery schedule API now correctly validates dates, preventing errors caused by format mismatches. This ensures accurate delivery date checks.

• Articles
• Batch Customers
• Batch Gross Prices
• Customers
• Price Lists

The name of the delivery location is determined based on field availability:

• If the Company field is filled, the Company name will be used.
• If any of the Firstname, Middlename, or Lastname fields are available, the location name will be a concatenation of these fields (e.g., Firstname Middlename Lastname).
• If none of these fields are populated, a GUID will be assigned as the location name to ensure uniqueness.

• We now support multi-language nodes and a multi-language sitemap.
• Additional modules, such as news and wiki, have been added to the sitemap.
• An issue where duplicate URLs could be added to the sitemap has been fixed.
• The sitemap will now automatically be split into several separate sitemaps, with a sitemap index, if the maximum size defined by Google is exceeded.
• The rendering of the sitemap has received a performance boost.

When both B2C and B2B customers can make purchases in a shop, B2C customers are sometimes allowed to buy in smaller quantities than B2B customers. Thus a customer may add items to their basket while still anonymous (under B2C rules), and then log in as a B2B customer. After logging in, the smaller quantities they added earlier may no longer meet the minimum quantity requirements for B2B customers. In such instances, the quantities in the basket must be adjusted to comply with the B2B purchasing rules.

Now, a notification popup appears to summarize automatic quantity adjustments when certain conditions are met. These adjustments occur under the following circumstances:

• An anonymous user logs in.
• The user's account is linked to price agreements.
• These price agreements cover products in the user's basket.
• The minimum order quantity is not met and/or the additional quantity is not divisible by the current article quantity.

This feature ensures that quantity requirements are automatically adjusted to meet minimum order thresholds.

The Voucher Customer Excel import phas been extended with several important validations to improve data accuracy:

• Resolved Import Issues: Fixed broken functionality in the Excel import.
• Redemption Limit Validation: Ensured that voucher redemption limits are validated as non-negative numbers.
• Duplicate Entry Detection: Added validation to identify and prevent duplicate customer-voucher links.
• Non-Existent Voucher Validation: Added checks for invalid or non-existent voucher codes.
• Customer Validation: Ensured that non-existent customers (based on debtor number) are identified during import.

• Discount tables
  
• OrderLists
• FavoritesLists
• Basket preview

A powerful new feature now offers granular control over payment costs through customizable filters. This functionality is designed to provide enhanced flexibility and precision in managing payment costs. With this feature, payment costs can now be adjusted based on the specific price list a customer is associated with, as well as the customer's debtor number. This allows for more tailored financial management, ensuring that payment costs are aligned with each customer's unique profile.

Key Features

• Flexible Filtering Criteria
  • Filters can be applied based on PriceList and DebtorNumber.
  • Each criterion supports both WhiteList and BlackList configurations.
• WhiteList and BlackList Options
  • WhiteList: Ensures strict inclusion by requiring a match with the specified PriceList or DebtorNumber.
  • BlackList: Excludes specific entries without requiring a match unless there is a direct conflict.
• Priority Handling
  • When both WhiteList and BlackList are populated, the BlackList takes precedence.
  • This ensures that any conflicting entries are excluded according to the BlackList rules.
• Combined Filtering
  • Filters can be applied simultaneously on both PriceList and DebtorNumber.
  • This allows for complex filtering scenarios, such as requiring a user to be linked to a specific PriceList while also excluding certain DebtorNumbers.

Usage Examples

• No Filters Applied
  • If both WhiteList and BlackList are empty, or if PaymentCostsFilters is null, no filters will be applied.
• Single Filter Applied
  • WhiteList Only: Filters are applied only when there is a match with the specified PriceList or DebtorNumber.
  • BlackList Only: Filters are applied when there is a match with the BlackList. If no match is found, the filter is not applied.
• Combined Filters
  • Both Lists Populated: The BlackList takes precedence over the WhiteList. Entries present in both lists will be excluded.

Example Configuration

{
"PaymentCostsFilters": {
"PriceList": {
"WhiteList": [ "PriceListA" ],
"BlackList": []
},
"DebtorNumber": {
"WhiteList": [],
"BlackList": [ "20021204" ]
}
}

• Users linked to PriceListA are included unless they have DebtorNumber 20021204, in which case they are excluded due to the DebtorNumber BlackList.

Benefits

• Enhanced Control: Provides granular control over which users are subject to payment costs based on their PriceList or DebtorNumber.
• Improved Flexibility: Allows for complex filtering scenarios to be easily implemented and managed.
• Priority Management: Ensures that exclusions are handled effectively with the BlackList taking precedence.

We hope this new feature enhances your experience and provides the flexibility and control needed to manage payment costs effectively. For more details and usage guidelines, please refer to the full documentation.

• Implemented OData for the SapByD Webservice.
• Fixed a bug where suspended articles could not be set to active due to sharing an article group in Vendisto, but not in the exported XML.
• Fixed the duplicate ArticleGroupDefaultTitle bug in the Article XML
• Set Order Origin to Internet when a customer selects the Bank Transfer payment method while placing an order (SapByD Webservice)