Kryptronic eCommerce version 9.5 has been released. A new MenuBuilder and a Modern NavMenu were added, plus even more SEO enhancements, and we added GooglePay using PayPal Commerce Platform. We also have new plugins for ShipStation and Unishippers. Lots of system updates were done, too!
This software upgrade features many, many changes and enhancements: A new MenuBuilder and a Modern NavMenu were added, even more SEO, GooglePay, ShipStation, Unishippers and more. We also did a bunch of architectural updates to make plugins easier to build and package and to speed up the release process. The platform continues to move forward towards ensuring all clients are up-to-date, and get updates quickly.
Current Clients: Click here for upgrade and update instructions
Items Added/Changed In This Version
New MenuBuilder and Modern Nav Menu
A new Menu Builder function was added which allow multiple complex menus to be built using simple admin tools. Choose from 25+ different types of menu and page options, settings to contorl look and feel, and more.
MenuBuilder functions were added to consolidate menu building for site navigation. The following skin/theme widgets were updated to build menus using new MenuBuilder functions: Account, Store, Pages, Recent Articles, Article Categories, Store Categories, and Navigation.
New icons were added to support the new menu system. The sprite used by the skin/theme system was updated to include new menu icons in place of the icon slots previously designated custom06 through custom10.
The Navigation Bar skin widget, which was added in version 9.3, has been replaced with a new Nav Menu widget. This new widget provides full control over the site’s Nav Menu using new settings and the new Menu Builder function.
Search Engine Optimization
A new recommended robots.txt configuration is available which is tuned for Google and other SEs to ensure crawl budget is optimized. When running an update to the new version, you will be provided the optimal configuration for your site.
All URLs presented on the Cookie Information page were updated to use ‘https’ instead of ‘http’. Some PCI scans now check content for http URLs in web page content which makes this update necessary when scanning using certain PCI vendors.
The Google Analytics (GA4) integration was updated to provide full support for Consent Mode. Consent for Mode Google Analytics (GA4) should be turned on using Search Engine Optimization Settings for stores operating in the EU and UK that use GA4. Use in conjunction with the Cookie Info Banner (configured using Privacy Settings) to set the default Consent Mode for the site (denied), and to allow users to provide consent (allowed).
The Google Tag Manager (GTM) integration was updated to provide full support for Consent Mode. Consent Mode for Google Tag Manager (GTM) should be turned on using Search Engine Optimization Settings for stores operating in the EU and UK that use GTM. Use in conjunction with the Cookie Info Banner (configured using Privacy Settings) to set the default Consent Mode for the site (denied), and to allow users to provide consent (allowed).
The Bing Ads integration was updated to provide full support for Consent Mode. Consent Mode for Bing Ads should be turned on using Search Engine Optimization Settings for stores operating in the EU and UK that use Bing Ads. Use in conjunction with the Cookie Info Banner (configured using Privacy Settings) to set the default Consent Mode for the site (denied), and to allow users to provide consent (allowed).
Added comment tags (googleoff/googleon) to product list and option displays on product detail pages to stop Google from indexing auxiliary images in place of the main images for the product offer displayed.
Social media integrations were updated to include X (formerly Twitter) and TikTok, and to remove Twitter and GooglePlus (NLA). The icon sprite was updated to include newer icons for these sites.
Checkout
A new setting was added to Checkout that Requires Delivery Address Confirmation. Customers newly entering checkout are prompted to confirm the selected delivery address for their order is correct when this new setting is turned on. The default for this setting is off. Use is recommended for stores with repeat business where customers ship to multiple addresses or frequently change addresses. Turning this setting on in such cases will decrease customer service tasks due to incorrect delivery address selections/entries by customers.
A new setting was added to Store Checkout settings which provides a minimum order amount specifically for wholesale customers placing orders with stores with the wholesale system active. This new setting overrides the regular minimum order amount setting just for wholesale customers.
PayPal Commerce Platform and Google Pay
The PayPal Commerce Platform integration was updated to use the seller access token for onboarding status checks. PayPal has changed from using parnter to seller access tokens for these requests in the sandbox and will be migrating the change to production at some point in the future.
The PayPal Commerce Platform integration was updated to allow customers to view and pay for orders using the currency they have selected to view the site and place orders. The currency conversion system must be active and there was a new setting added for PayPal Commerce Platform (Allow User-Selected Currency Orders) to allow you to turn this functionality on or off.
The onboarding confirmation logic for PayPal Commerce Platform was refined in order to provided a seamless transition back to the platform from PPCP after onboarding is completed. Previously an auxiliary window was used and that’s been moved to the main window to reduce the need to close the auxiliary window after setup.
Added support for Google Pay payments to the PayPal Commerce Platform integration. Turn on Google Pay payments by turning them on in your PayPal account and using PayPal Commerce Platform Settings to adjust your payment settings to accept Google Pay.
Shipping
The UPS account number setting for UPS OnlineTools was changed to a hidden field and marked for removal in a future update. This field is used only by legacy SOAP API connections which are being systematically disabled by UPS currently. Newer API-based connections use the account number entered during connection setup.
A new integration with USPS using their new API was released as a mini-update in January 2026 for all versions. These changes were incorporated into this version and new services were added for priority mail options – envelopes, padded envelopes, flat rate boxes.
Time in Transit (Delivery Estimate) functionality was disabled for UPS Online Tools. UPS has recently made updates to Time in Transit that now produces rating errors when rating zip codes tied to more than one city with the Time in Transit option active. This functionality will remain disabled until UPS fixes their Time in Transit logic.
Order Management
The Order Manager function which allows splitting partially complete orders to move unshipped items to a new order was modified. Previously orders could not be split if customer payments other than credits had been made against them. Now those orders can be split and the customer payments are split accordingly to maintain correct balances on all orders.
A new Order Merge function was added to the Order Managers. Now you can merge open orders together. Orders which have not been fully shipped, and have not had any returns processed, can be merged into other open orders placed by the same customer.
Changed Order Center search logic to match on exact order number entry quickly for current orders. This speeds up order searches using the Order Center by 10x when using an exact order number to locate current orders.
Added a field to Order Manager / Ship Items to allow suppressing mail messages sent to customers when shipping items. The new field is checked by default, and must be unchecked in order to suppress the customer shipment mail message.
Added an order review condition for low total orders. Now you can select low total orders as a review condition and set an amount for the low total check. Use store Order Manager settings to turn this new feature on.
General System
Changes were made to provided support for newer versions of PHP8. Currently the platform is fully tested and compatible with PHP5.6 through PHP8.3, and is known to run well on PHP versions higher than PHP8.3.
Modified the channel plugins to use properly formatted email addresses specific to the channel when the buyer email address is not available. Notably, this affects Amazon FBA orders which previously had the email address saved as ‘Unknown’, but now it is saved as ‘unknown@amazon.com’. This change was made to satisfy email validations handled by other plugins like QuickBooks Online.
Increased the height of search and on-page returned results sections in the management interface when viewing using wide/desktop devices. The height of these sections was nearly doubled to make it easier to navigate results on larger displays.
All Armed Forces (APO/FBO) state/province entries were updated to use United States as the country tied to the state/province entry. Previously no country was assigned. The localization helper updated to make use of this new configuration.
Password strength requirements were updated to make the minimum length for strong passwords twelve characters. Previously the minimum was ten. This update aligns the platform with edge PCI requirements being used by some entities like universities.
Predictive ajax search results used by the mini-search widget were updated to use stock status controls and suppress/resort out of stock items based on stock controls settings.
NEW Plugin: ShipStation
A new plugin was added that provides support for using ShipStation in conjunction with the Batch Shipping Manager plugin. Batch orders using Batch Shipping Manager then ship with ShipStation. This plugin is similar to the recently released StarShipIt plugin and makes use of ShipStation’s latest API to send shipments to ShipStation and retrieve package tracking information from ShipStation. Changes to batches and shipments are fully synched between the platform and ShipStation.
NEW Plugin: Unishippers
Now you can get realtime checkout ratings for shipments using your Unishippers account. Unishippers provides deeply discounted pricing for UPS shipments. This integration uses the latest Unishippers API.
Plugin: SEO MicroData
The MicroData plugin was updated to include more microdata elements for Collection Pages. Those pages now expose the number of items and item order.
Plugin: Amazon
The Amazon plugin was updated to safely handle the case where Merchant Shipping Group information cannot be obtained from Amazon. Now Merchant Shipping Groups will only be removed if a connection can be made, and Merchant Shipping Group info can be processed.
The Amazon plugin was updated to submit condition note information on new listings only, and not on listing updates. Management of this field for listings can be done at Amazon.
The Amazon plugin was modified to handle inventory updates differently when maximum inventory levels are set for Amazon offers. Previously the current inventory level was checked to determine if an update needed to be pushed. Now the maximum adjusted inventory level is used to determine update pushes.
Added additional logic to the Amazon module to double-check for duplicates against saved orders immediately prior to saving new orders. This adds a safeguard against duplicate orders being saved in the event a job runs overtime due to lag in the connection with Amazon. Previously there was exposure saving duplicate orders if a large data set was encountered while Amazon was experiencing connection lag.
Updated the Amazon plugin to only update offer names during synchs if the name is a valid, non-empty string provided by Amazon with listing data. Amazon has been returning offer names intermittently, and this change ensures offer names only update if a valid offer name is provided by Amazon.
Plugin: QuickBooks Online
The QuickBooks Online plugin was updated to send VAT/GST tax code references for line items for VAT-enabled companies (non-US). The tax code reference used is ‘No VAT’, which excludes VAT/GST from line items. This was done because VAT/GST is populated on it’s own line item in invoices, credit memos and purchase orders.
Plugin: Authorize.Net
The Authorize.net plugin was updated. The CIM (Customer Information Manager) payment method now flags customer profiles as guest (temporary) profiles when processing payments for customers who have chosen not to save their payment info. This is a new option which allows Authorize.net to purge old unused guest profiles that the customer chose not to save.
Plugin: OrderFollowUps
The Order FollowUp plugin was modified to trigger follow-up messages eight times daily. There was an issue indentified with the job trigger which was causing the job to fire intermittently. Additionally, the mail functionality was altered to send an HTML version of the followup message when entered for HTML versions of mail messages.
Structural and Architectural Changes
In the spirit of making updates easier, faster and providing near-future support for auto-updates:
Site and store demo data is no longer delivered as part of the installation package. It is now stored on the central server and downloaded and loaded when requested. The Remove Demo Data system helper was renamed Demo Data, and now handles both loading demo data and removing it.
Internal demo functions were removed from the platform. This functionality became obsolete many years ago when sessions moved to token-based logic. This functionality provided web-based demos of the platform, not store and site demo data. It was only used by Kryptronic and a few select partners.
Plugins now support storing and using include fields in their own includes directory. Moved all includes associated with plugins from the main core/app includes directories into an includes directory in the appropriate plugin module.
Added a new include_modulefile() function to the main Display class. This new function allows include files to be included from any module directory. The function accepts app, module and include filename as inputs. Legacy support was retained for including files referencing just app and filename using the include_file() function, and that function is still in use system-wide for including base system files that continue to be stored in the main core/app include directories.
Namespaces referencing includes were updated to use pointers containing the app, module and filename. Previously these pointers used filename only, and used the namespace’s app and the class module for that app. The newer pointer format allows includes for namespaces (like those for plugins) to be stored in any module directory. Legacy support was retained for namespace definitions that do not specify the app and module in the pointer. Modified all affected namespaces to support the new pointer format.
Advanced report pointers were updated to use pointers containing the app, module and filename. Previously these pointers used filename only, and used the report’s app and the class module for that app. The newer pointer format allows includes for reports (like those for plugins) to be stored in any module directory. Legacy support was retained for report definitions that do not specify the app and module in the pointer. Modified all advanced reports to support the new pointer format.
Form field, checkout form field and database column form field include pointers were updated to use pointers containing the app, module and filename. Previously these pointers used app and filename only. The newer pointer format allows includes for fields (like those for plugins) to be stored in any module directory. Legacy support was retained for field definitions that do not specify the module in the pointer. Modified all fields and database columns to support the new pointer format.
Support was added for running startup and shutdown logic using namespaces. Using file-based scripts stored in the main core and app directories is still supported and used by the platform by default. These new namespaces make it easier to add startup and shutdown logic using plugins.
Support was added for running all cron jobs using namespaces. Using file-based scripts stored in the main core and app directories is still supported and used by the platform by default. These new namespaces make it easier to add cron logic using plugins.
Support was added for running all order initialization, processing and completion functions using namespaces. Using file-based scripts stored in the main core and app directories is still supported and used by the platform by default. These new namespaces make it easier to add order initialization, processing and completion logic using plugins.
Support was added for running realtime shipment rating and tracking using namespaces. Using file-based scripts stored in the main core and app directories is still supported and used by the platform by default. These new namespaces make it easier to add realtime shipment rating and tracking logic using plugins.
Changed all plugins to use the term ‘Plugin’ in place of ‘Extension Module’ as it is a more meaningful description of these types of modules. Going forward plugins will be referred to as plugins in the software and all documentation. Plugins built by Kryptronic will continue to the class prefix ‘XMOD’ to identify them as plugins, but the terms ‘XMOD’ and ‘Extension Module’ are no longer used.
Modified settings listings to sort all settings groups alphabetically. This makes plugin settings easier to find. Previously they were marked as ‘Extension Module’ settings and grouped at the bottom of settings group lists.
Changed the logic for the management interface skin. Previously it was generated using the stock skin/theme logic. Now it is generated using a core include. This change allows for easier changes and maintenance of the management interface skin during updates. Logos (both the main logo and private label) were moved to {public}/media/skins/logos to be stored with all other logo images.
Changed the logic for the mail message skin. Previously it was generated using the stock skin/theme logic. Now it is generated using a core include. This change allows for easier changes and maintenance of the mail message skin during updates. Optional attachments should now be stored in {public}/media/mailattach.
