Things have been quiet from us during the summer in terms of new functionality in Kroconnect. Work continues, however, both on new features and onboarding of new customers. Here is a brief summary of the work we have done in Kroconnect during the period July to September.
Support for One Stop Shop (OSS) in Fortnox
We have added the ability to specify account classes per order line sent to Fortnox. This creates better control over your accounting if you sell to multiple countries and need to configure One Stop Shop (OSS) in Fortnox.
Improved logic in the mapper
The mapping logic for workflows has been extended. It is now possible to set conditions for whether a product (or other entity) should be updated or not in the other system. One example of this is only updating a product in WooCommerce if the “Publish in webshop” checkbox is checked on the item card in Specter.
We have also added new functions to the mapper that can be used to control how and what is sent to another system. It is now also possible to use functions such as fullCountryName, isEuCountry, toMajorUnits, toMinorUnits, toPriceExVat and toPriceIncVat. We are currently working on our documentation, where this will be explained in more detail.
Fixes and improvements
- Improved support for handling and sanitizing certain special characters in product sync from Specter, and to Fortnox. This feature can be extended in the future to handle additional characters.
- Reduces the number of calls to VendoPRO to fetch the current stock balance for products.
- Improved handling of how masked API keys are displayed in the Kroconnect web app. Previously, keys shorter than 4 characters caused an error, which prevented the Workflows page from rendering correctly.
