Changelog

Abeta makes continuous updates to the application. This overview shows the relevant changes and updates to the Abeta IO application per month.

#December 2025

The following FEATURES have been added to the Abeta IO application:

Order confirmations can be sent to a fixed endpoint (in addition to the Abeta endpoint) for procurement systems that require this.
Remarks and custom_data fields have been added to the cart lines.
(Admin) Ability to log specific outgoing requests.

The following CHANGES have been made to the Abeta IO application:

The delivery date is now taken from the line by default if it is not present in the header.
Updated handling of XML namespaces when they are not present.

The following FIXES have been applied to the Abeta IO application:

The following FEATURES have been added to the Abeta IO application:

Ability to pass through the user’s email address during login (for all applications).
(Magento) Verify prices in the webshop.

The following CHANGES have been made to the Abeta IO application:

Automatic date selection based on the order header, order lines, or cart.
Adjustment of xml:lang based on the webshop for cXML PunchOut.
Fully refactored processing of orders received via email with XML attachments in Abeta.
Additional logging for email orders with XML attachments.
Frame breaker added to the frontend to prevent loading in an iframe.

The following FIXES have been applied to the Abeta IO application:

The following FEATURES have been added to the Abeta IO application:

(Shopify) Added redirect URL after login.
Automatic order line number generation when missing in the purchase order.
Added customer-specific password option to the purchase order mapping. (For cases where the webshop expects a user password in the order confirmation.)
Added custom order method.

The following CHANGES have been made to the Abeta IO application:

The following FIXES have been applied to the Abeta IO application:

Unified differing User-Agent strings in specific calls. (Prevents false identification as a robot based on the User-Agent.)
(Magento) Fixed an error in the account status check that caused accounts to be incorrectly marked as disconnected.
(WooCommerce) Fixed an error where the custom URL was not respected for an order confirmation.

The following FEATURES have been added to the Abeta IO application:

The following CHANGES have been made to the Abeta IO application:

The following FIXES have been applied to the Abeta IO application:

Fixed an issue where empty meta values caused an error when creating an order in WooCommerce. (WooCommerce specific)
Fixed an issue with error message sanitation caused by a change in the error logging system.

The following FEATURES have been added to the Abeta IO application:

Optional checkout fields on the Abeta side for processing additional checkout data.
Simple connection details page added to connection.
ValueMapping (translation table) per webshop expanded.

The following CHANGES have been made to the Abeta IO application:

Automatic updates of external JavaScript with every change. [Lightspeed, Shopify]
Adjustment to the processing of a full name. Specifically for correct processing of the format “Last name, First name.”
Refactoring of various pieces of code.

The following FIXES have been applied to the Abeta IO application:

The following FEATURES have been added to the Abeta IO application:

The following CHANGES have been made to the Abeta IO application:

Assets are now loaded via separate buckets.
Reference in the SKU takes priority over separate order reference in the order confirmation.
The generation of the Purchase Order has been refactored for better future-proofing.

The following FIXES have been applied to the Abeta IO application: