This release includes a broad set of enhancements across connectors and tools. Highlights include automated handling of FBA return orders and settlement reports for Amazon, GraphQL improvements for Shopify, and more flexible item management across sales channels. We’ve also added new order events and improved error logging to support smoother operations in Business Central.

General Improvements  

Reapply Customer Template on Updates

For some of our clients, the Tinx connector downloads customer data from a webshop and creates customer cards in BC. After this, it is also possible to update the customer card (for example after new orders are placed for that customer). We've added the ability to (partially) re-apply a customer template when updating a customer card in BC.

Provided the mapping is present to update data on customers cards and re-apply a customer template, clients can now go to the Sales Channel Card > Sales Channel > Apply Customer Template Fields to select which fields are re-applied. This means that clients can choose which fields to re-apply and which to not have touched.

Item by Sales Channel: Activation & Date Fields

We've added a new setting on the Sales Channel card or Multi Sales Channel syncing of products: Set Active to False. When this box is checked, when publishing an item via the Items by Sales Channel tables, the Active box is checked. This can be used for filtering.

Additionally, when the item is activated, the new Activation Date (30, Date) field is filled in with today's date.

Fix: Integer Fields Sent as Text

Fixed an issue where (Big) Integer fields were being sent as text fields instead of numeric.

Auto-Assign Attribute Sets by Item Category

Added the ability to assign an attribute set to items based on their Item Category. If multiple sales channels are used (and Boolean field 224 of E-commerce Integration Setup is set to True), one can add a Item Category (field 10) in table TINX Attribute Set (11205754). Once this is selected, a popup will show asking whether the set should be applied to all items with the selected item category code.

Separate Webshop Code & Sales Channel Code

Previously, when adding a new sales channel to a setup, the Sales Channel Code was filled in via lookup, making it impossible to say, add a WOOCOMMERCE channel when there was already a WOOCOMMERCE channel active. This erstwhile meant the old/existing channel code had to be changed before a new channel (automatically using WOOCOMMERCE) to the system. We've now separated the Webshop Code (i.e. the specific connector you'd like to install) from the Sales Channel Code (i.e. the code used within the configuration to indigate a specific sales channel record in the system).

New Order Events: Sales Credit Memo and Explode BOM

Added two new order posting event: post sales credit memo's and explode BOM. Example BOM below:

Data Management Tool: Update Field Value

A new option ‘Update Value for a Field’ has been added to our Data Mgt. Tool. With this feature you can, for example, rename a filtered value instead of resetting it or deleting it. Use case: helpful during customer upgrades when the sales channel values need to be updated in imported config.package data, such as transitioning from SOAP to REST integrations.

Webshop Order: Extended Fault Reason Logging

We've extended the 'Fault Reason' field in the Tinx Webshop Order table to add more information when an order has failed to create. Below and example of when the shipping agent code field was not filled in but was mandatory before creating a sales header in BC. This change will help customers more easily troubleshoot errors with order processing.


 

Order Import Error Email: Add Fault Reason

Now when using our E-mail Notification setup for order errors, that is the 'On Order Import Error' check, more information is provided about the order in particular.

Example:

Auto Insert Items per Sales Channel

A new feature has been added to automate the insertion of items into the Item by Sales Channel table (TINX Item by Sales Channel (11205331)), streamlining the setup process when working with multiple sales channels. Previously, this step had to be performed manually.

Now, using report 11205311, Tinx Auto Insert Items per Sales Channel, items can be added automatically.



Additionally, new settings allow you to:

• Define whether items should be automatically published to the sales channel upon insertion.

• Specify the maximum allowed length of the Item No. for compatibility with the webshop.

This improvement helps reduce manual effort and ensures better control over item synchronization and publication across channels.

Amazon

FBA Return Orders Automation

A new feature has been added to the Amazon Connector to support the handling of FBA Return Orders using Amazon’s GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA report. The process begins by retrieving and processing the report records. These are then used to generate entries in the Amazon Return Order table via report 11205848 – TINX AMZ FBA Returns.

Subsequently, the system fetches the related orders and uses the data from the Amazon Return Order table to automatically create the corresponding Sales Return documents in Business Central.

Partial Fulfillment of Amazon Orders

Added functionality to partially fulfill orders for Amazon as well.

Settlement Report Download (Private & Public Apps)

The Amazon Connector has been extended to support downloading and processing Settlement Reports from Amazon Seller Central, for both private and public Amazon apps. This addresses a common request from users who require access to settlement and inventory data via the Amazon API.

The process follows a multi-step flow similar to the handling of FBA Return Orders:

1. The system initiates the download of the Settlement Report using Amazon’s reports/2021-06-30/reports API (AMZ-SP-101). Unlike some merchant reports, this one is auto-generated by Amazon and does not require manual triggering.

2. Report 11205839 – TINX AMZ Reports Processing is executed to retrieve the settlement data into table TINX Amazon Report (11205938).

3. Report 11205847 – TINX AMZ Settlement processes the retrieved data and creates entries in the Settlement tables (TINX Amazon Settlement (11205367) and TINX Amazon Settlement Line (11205368)).

4. A CreateSettlement message (AMZ-SP-014) is used to generate and post General Journal entries (table 81) in Business Central based on the processed settlement data.

This new capability streamlines financial reconciliation for Amazon sellers and enhances automation in the settlement reporting workflow.

Shopify

GraphQL: Custom Field Selection

We're continuing work on converting our Shopify connector to GraphQL, including adding new features. One of these is the ability to select from a tree or schema which fields we want to send (i.e. mutations) or receive (i.e. queries) from Shopify. More to come soon.

External Location IDs per Sales Channel

Added a new table TINX Location Sales Channel (11205370) to store external location ids. This is useful when having multiple sales channels in BC, and therefore different Shopify backends. Whilst each Shopify backend has it's own ID, in the same BC company that does not have to be the case. With this addition we're able to better deal with this.