Webshops and Business Central use different field names, data types, and value formats for the same information. Examples include customer addresses, order statuses, and product prices. Default mapping automatically translates between the two. This article is a practical example of how that mapping works in WooCommerce legacy mapping. Default mapping is a broader concept in Tinx Connector, covering multiple webshops and both legacy and new mappings. For more information, see Default mapping.
The message definitions and details described in this article are similar across Magento and Shopware because those platforms still use the same legacy-style mapping. The new mapping is currently available for Shopify and for those companies that installed WooCommerce after July 29, 2026. In the new WooCommerce mappping the message definition numbers differ from the ones in the legacy mapping. The webshop order process also uses more messages in the new mapping than the legacy mapping does.
Tinx released a new default mapping for WooCommerce on July 29, 2026. The new installations after that date use the new mapping that is not described in this article. The change doesn't affect your setup if you're already using the legacy mapping described here. You have the legacy mapping if you installed Tinx WooCommerce Connector before July 29, 2026. You have the new mapping if you installed it on or after that date.
Create webshop product
To create a webshop product, Tinx Connector uses the WOO-020 message definition with the description Create item in WooCommerce. The message definition uses the products web service. The connector publishes this data to WooCommerce, so WOO-020 is an outbound message. The WOO-020 message definition is a part of the product synchronization process.
The following screenshot shows the WOO-020 message definition.
The following table explains the particular lines in the WOO-020 message definition.
| Basic Product Sync | Table | Element Name | Field No. / Name | Webshop Field | Notes |
|---|---|---|---|---|---|
| Yes | 27, Item | products | 3, Description 18, Unit Price, 18, Unit Price 1, No. 5, Description 2 |
name price regular_price sku stock_quantity manage_stock backorders backorders_allowed short_description featured |
The values such as manage_stock and backorders are set to default values, such as yes or no. The stock value sent with the stock_quantity field is taken from the Item Card in Business Central (field 68). |
| No | 11205753, TINX Web Item Extension | products | 51, Woo Product Type 12, Visibility 10, Manage Stock 13, Status 105, Is Virtual 106, Is Downloadable 107, Reviews Allowed |
type catalog_visibility manage_stock backorders in_stock backorders_allowed status virtual downloadable reviews_allowed |
Fields such as catalog_visibility and manage_stock often get default values of true or false. These values are either set manually or, in this case, taken from a Tinx table (11205753). |
| No | 5404, Item Unit of Measure | dimensions | 7300, Length 7301, Width 7302, Height |
length width height |
|
| No | 11205755, TINX Attribute | attributes | 6, Webshop Id 2, Field Name 25, Position |
id name position visible variation |
|
| No | 11205761, TINX Attribute Options | options | 2, Option Value | option_value | |
| No | 11205296, TINX Web Text Line | description | 6, Text | description | |
| No | 11205296, TINX Web Text Line | short_description | 6, Text | short_description | |
| No | 11205751, TINX Web Category Item | categories | 11, Magento Category Id | id | |
| No | 27, Item | meta_data | 14, Item Disc. Group | _tinx_item_discount_group | |
| No | 11205284, TINX Image - Video Link | images | |||
| No | 7002, Sales Price | products | 5, Unit Price | sale_price |
Create sales order
To create a sales order based on the imported webshop orders, Tinx Connector uses the WOO-087 message definition. Its description is Download order and Create Sales Header in NAV. The message definition uses the orders/%1 web service. The connector downloads this data from WooCommerce, so WOO-087 is an inbound message. The WOO-087 message definition is a part of the order synchronization process.
Many values used during sales order creation are downloaded into the Tinx Webshop Order table through the WOO-086 and WOO-086-1 messages. The connector creates sales orders based on this table and the filters applied to it.
The following screenshot shows the WOO-087 message definition.
The following table explains the particular lines in the WOO-087 message definition.
| Table | Element Name | Field No. / Name | Webshop Field | Notes |
|---|---|---|---|---|
| 36, Sales Header | root/root | 1, Document Type 3, No. 2, Sell-to Customer No. 11, Your Reference 19, Order Date 20, Posting Date 100, External Document No. 43, Salesperson Code 23, Payment Terms Code 104, Payment Method Code 105, Shipping Agent Code 11205250, TINX Webshop Order 11205251, TINX Entity ID |
document_type no_ id order_key order_date posting_date id salesperson_code id id shipping_agent_code tinx_webshop_order id |
Field 3 uses a number series defined on the Tinx E-Commerce
Setup page. The sell-to customer is obtained through a lookup to the Webshop Orders table. Order and posting dates default to TODAY. Payment terms and method codes are also lookup fields to a different table. |
| 36, Sales Header | billing | 5, Bill-to Name 7, Bill-to Address 8, Bill-to Address 2 9, Bill-to City 85, Bill-to Post Code 86, Bill-to County 87, Bill-to Country/Region Code 79, Sell-to Customer Name 81, Sell-to Address 82, Sell-to Address 2 83, Sell-to City 89, Sell-to County 90, Sell-to Country/Region Code 88, Sell-to Post Code |
company address_1 address_2 city postcode state country company address_1 address_2 city state country postcode |
|
| 36, Sales Header | shipping | 13, Ship-to Name 15, Ship-to Address 16, Ship-to Address 2 17, Ship-to City,city 91, Ship-to Post Code 92, Ship-to County 93, Ship-to Country/Region Code |
company address_1 address_2 postcode state country |
|
| 37, Sales Line | line_items | 4, Line No. 5, Type 6, No. 15, Quantity |
line_no_ type sku quantity |
Line No. is set to a 10000 increment
value. Type is 2. The No. and Quantity fields are validated. The unit price field is added here if the price should be obtained from the webshop instead of Business Central. |
| 37, Sales Line | fee_lines | 4, Line No. 5, Type 6, No. 22, Unit Price 15, Quantity 11, Description |
line_no_ type no_ total quantity name |
|
| 37, Sales Line | shipping_lines | 4, Line No. 5, Type 6, No. 15, Quantity 22, Unit Price 11, Description |
line_no_ type no_ quantity total method_title |
|
| 44, Sales Comment Line,meta_data | meta_data | 6, Comment | custom_notes |
Change webshop order status
To change the webshop order status, Tinx Connector uses the WOO-088 message definition with the description Set status from web order in WooCommerce. The message definition uses the orders/%1 web service. The connector sends this status update to WooCommerce, so WOO-088 is an outbound message. The WOO-088 message definition is a part of the order synchronization process.
The following screenshot shows the WOO-088 message definition.
The following table explains the particular lines in the WOO-088 message definition.
| Table | Element Name | Field No. / Name | Webshop Field | Notes |
|---|---|---|---|---|
| 110,Sales Shipment Header | data | status | The default value is Completed. |
Create customer card
To create a customer card, Tinx Connector uses the WOO-008 message definition with the description Create Dynamics 365 Customer Card. The message definition uses the customers/%1 web service. The connector downloads this data from WooCommerce, so WOO-008 is an inbound message. The WOO-008 message definition is a part of the customer synchronization process.
Similar to sales order creation, some of the fields used to create the customer card are obtained through a different message, WOO-006.
The following screenshot shows the WOO-008 message definition.
The following table explains the particular lines in the WOO-008 message definition.
| Table | Element Name | Field No. / Name | Webshop Field | Notes |
|---|---|---|---|---|
| 18, Customer | root/root | 1, No. 2, Name 7, City 102, E-Mail 11205258, TINX First Name 11205259, TINX Last Name 11205250, TINX Publish to Webshop 11205251, TINX Webshop Customer ID |
no_ company city first_name last_name tinx_publish_to_webshop id |
The default value of the No. field is the number series assigned on the Tinx E-Commerce Setup page. The Publish to Webshop value has a default value of 1. |
| 18, Customer | meta_data | 1, No. 86, VAT Registration No. |
example vat_number |
|
| 18, Customer | billing | 2,Name 5,Address 6,Address 2 7,City,city 9,Phone No. 91,Post Code 92,County 35,Country/Region Code |
company address_1 address_2 phone postcode state country |
|
| 222, Ship-to Address | shipping | 3, Name 4, Name 2 5, Address 6, Address 2 7, City,city 91, Post Code 35, Country/Region Code 2, Code |
first_name last_name address_1 address_2 postcode country code |
The Code field is of type Increment, with a value of 1. |
Retrieve existing lines
There are situations where data must be filtered before it is used to create a new record in a table. This feature is often used in the order import. The following example illustrates how to use the Retrieve Existing Lines option.
To use the Retrieve Existing Lines option
- On the Message Line Fields page, select the Retrieve Existing Lines checkbox at the line level, fill in the Copy Into Table field, and then select the correct Table No. to copy data into.
- Add links at two levels between the parent and child table:
- Copy Links: The link between the parent table and the source table where the data resides.
- Links: The link between the target table and the parent table.
In the case of orders, Copy Links typically match the Entity ID to the Tinx Webshop Entity ID. Links are set to Document Type = Document Type and Document No. = No.
Links should be added at two levels between the parent and child table. The first is the Copy Links section. This is the link between the parent table and the source table that contains the data. The second is the general Links section. Here, we assign the link between the target and parent tables.
In this example, you take information from the TINX Sales Quote Line Option table 11205357 to the Sales Comment Line table 44. For that, you need a link between table 11205357 and table 36, and another link between table 36 and table 44.
Tinx Connector stores this data in its own tables, rather than reading it directly from the webshop. It does this because webshop data isn't always compatible with Business Central. For example, an order line's tax total might need to be calculated, split, or otherwise adjusted before Business Central can use it. Storing the data in Tinx Connector's own tables first gives more options for filtering, applying logic, and using formulas.
Inbound message metadata
To import values from a generic section, such as meta_data or custom_attributes, use the following setup. Depending on whether the file is formatted in XML or JSON, use / or . as the value separator.
Related information
Synchronize products
Synchronize orders
Default mapping
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