Mapping Business Central fields to a webshop platform's fields, such as product names, prices, and order details, is normally significant setup work. The default mapping already includes most of that configuration. Tinx Connector installs a working, preconfigured mapping automatically when you create your first sales channel, so you get basic webshop synchronization without having to configure every field yourself.
Default mapping for Business Central online
After you install the Tinx Connector app from Microsoft AppSource, it adds tables, reports, and codeunits to your Business Central. When you then create the first sales channel for a particular webshop, such as Shopify or WooCommerce, Tinx Connector installs the default mapping for that sales channel. The package that Tinx imports to your Business Central works similarly to a standard Business Central configuration package, but it isn't the same feature. The default mapping includes, among other things, synchronization dashboards and message definitions. They map Business Central fields to your webshop's fields. The default mapping also includes many more settings beyond this field mapping.
Creating the first sales channel for a webshop automatically triggers this mapping download. For example, step 4 in To create and configure a Shopware sales channel in Business Central is where Tinx Connector downloads the default Shopware mapping. A similar step and process apply for every other webshop platform.
This mapping download usually takes several minutes. For Shopify, it can take around an hour.
After you complete the initial setup steps, such as configuring the sales channel, these default mappings handle basic webshop synchronization. You can adjust and configure the default mappings to match your company's needs. Almost all companies using Tinx Connector have adjusted the default mapping in some way. For more information, see Synchronisation Dashboards.
Default mapping for Business Central on-premises
For on-premises installations, contact the Tinx Sales Team before setup. There's no self-service trial path for on-premises installations, unlike for cloud installations.
In Dynamics 365 Business Central on-premises, the default mapping might depend on the version of Business Central you use. In most cases, the Tinx Development Team prepares the most recent version of the default mapping that is adapted to your version of Business Central. If you already use Tinx Connector implemented by Tinx Consultants, updating the mapping to the new version is a separate project.
Field mapping
To see the field mapping for a specific message or dashboard, review the related message definition or synchronization dashboard, respectively.
To review message definitions
Select Search (Alt+Q) in the upper-right corner, enter Message Definitions, and then choose the related link.
-
On the Message Definition List page, choose the Edit or View action to check the details about each message definition.
The following screenshot shows part of the Shopware message definitions available on the Message Definition List page.
To review synchronization dashboards
Select Search (Alt+Q) in the upper-right corner, enter Synchronisation Dashboard List, and then choose the related link.
-
On the Synchronisation Dashboard List page, choose the Edit or View action to check the details about a synchronization dashboard.
This dashboard offers a more structured view than the Message Definition List page. It groups message definitions into sections related to specific synchronization operations, such as order import, product synchronization, and customer export.
The following screenshot shows the list of Shopware synchronization dashboards.
When you open any of these messages, you see a message definition with mapped fields.
The following screenshot shows the mapping used by the SW-086 message definition, whose role is to import Shopware webshop orders into the Webshop Orders page. The next message SW-087 converts those imported orders into Business Central sales orders.
A JSON or XML response from the webshop can contain many fields. In the message definition, you specify which of those fields to map to Business Central. The Field and Field Name columns refer to the Business Central table. For inbound messages, this is the table where data is added. For outbound messages, it's the table from which data is retrieved. The Webshop Field column shows the field name in the JSON or XML that the connector checks or to which it sends data.
The WooCommerce legacy mapping article walks through a detailed example of these standard fields and covers several of the most important message definitions. For more information, see WooCommerce legacy mapping.
New mapping and legacy mapping
Tinx Connector uses two default mappings: a new mapping and a legacy mapping. Each sales channel uses only one of the two. Whichever applies, Tinx Connector sets it up automatically after you create the first sales channel for that webshop, following your installation from Microsoft AppSource. The two mappings also number their messages differently.
New default mapping
The new mapping assigns a dedicated number range to each dashboard, based on its direction and function. This numbering structure applies to Shopify and WooCommerce. Business Central shows each dashboard with its platform prefix added, for example WOO_IN_CUSTOMERS for WooCommerce or GQL_IN_CUSTOMERS for Shopify.
Using WooCommerce doesn't automatically mean you're on the new mapping. If you installed WooCommerce before July 29, 2026, your sales channel is still on the legacy mapping, not the new mapping described here. For more information, see WooCommerce legacy mapping.
The following table describes what each range does, based on the message definitions in the WooCommerce and Shopify new mapping.
| Synchronization dashboard | Message definitions | Description |
|---|---|---|
| IN_CUSTOMERS | 000-020 | Downloads the customer linked to a webshop order and creates the matching Business Central customer and address. |
| OUT_PRODUCTS | 020-040 | Publishes products, variants, categories, and attributes from Business Central to the webshop. |
| OUT_CUSTOMERS | 040-060 | Publishes customer records from Business Central to the webshop. |
| OUT_STATUS | 060-080 | Sends order status and shipment tracking updates from Business Central to the webshop. |
| IN_REFUNDS | 100-120 | Downloads refunds from the webshop and creates the matching sales return order in Business Central. |
| IN_ORDERS | 120-140 | Downloads new webshop orders and creates the matching sales order in Business Central. |
| OUT_B2B_PRICING | 160-180 | Publishes B2B sales prices and discounts from Business Central to the webshop. Applies only to WooCommerce. |
| IN_OTHER | 180-220 | Downloads reference and catalog data from the webshop, used to prepare or match data before publishing. |
Legacy default mapping
Legacy default mapping applies to every webshop platform except Shopify and WooCommerce, which use the new mapping. If you installed WooCommerce before July 29, 2026, your sales channel is also still on the legacy mapping. This section uses Magento and Shopware as examples. In most cases, the same structure applies to the other webshops that use legacy-mapping. Use this section to find which dashboard, and roughly which message definitions, handle a specific task, such as importing webshop orders.
For a few dashboard types, Shopware and Magento use consistent message numbers.
| Synchronization dashboard | Message definitions | Description |
|---|---|---|
| IN_CUSTOMERS | around 006-008 | Downloads webshop customers and creates the matching Business Central customer. |
| IN_ORDERS | around 086-087 | Downloads webshop orders and creates the matching Business Central sales order. |
| OUT_PRODUCTS | starts at 020, also includes 075 and 078 | Publishes products and categories from Business Central to the webshop. |
For most other dashboard types, the message definitions aren't consistent between Shopware and Magento, and each webshop uses its own numbers.
Several of the most important legacy messages are explained in detail, using legacy WooCommerce mapping as the worked example. Although its message numbers are specific to WooCommerce legacy mapping, the same structure applies to Shopware and Magento. For more information, see WooCommerce legacy mapping.
Related information
Synchronization
dashboards
WooCommerce legacy
mapping
Sales channel
Key concepts in Tinx
Connector
Troubleshooting
checklist
Get help
from Tinx Support
Help us improve the documentation
We continuously update the Tinx documentation. This article was recently rewritten. Send your feedback to docs@tinx-it.nl to help us make it even better.
Last updated on September 2, 2026