Understanding Data Mappings and Order Flow in Syncware

The Order Details page in Syncware provides visibility into how order data is mapped and flows from the source system through Syncware and into the end system. This insight helps users troubleshoot, validate, and better understand how data is transformed during the order lifecycle.

What Are Data Mappings?

Data mappings define how order fields from the source system are translated into Syncware fields and subsequently how Syncware fields are passed to the end system.

Each mapping includes:

• Source Field: The original field name from the external system.
• Value: The actual data contained in that field.
• Destination Field: The corresponding field name where Syncware will store or send the data.

Viewing Mappings on the Order Details Page

To view data mappings:

1. Log in to Syncware.
2. From the navigation menu, select Orders.
3. Click on the desired order number from the list to access the Order Details page.
4. Within the Order Details page, look for the Source to Syncware tab and optionally a Syncware to End System tab if the order has been processed downstream.

Example: Source to Syncware Mapping

When an order originates from a source like Faire, you’ll see a tab labeled Faire to Syncware showing field-level mappings.

In this example:

• Faire's id field contains the value bo_7mqkb45gea.
• Syncware receives and stores this value in the OrderID field.

Example: Syncware to End System Mapping

If the order is being sent to Shopify, a second tab labeled Syncware to Shopify will be available. This tab reflects the mapping between Syncware fields and Shopify fields.

This view shows how Syncware prepares data to send to the destination system. Fields left blank or unmapped may indicate optional data, mapping issues, or missing destination fields in the intended end system.

Key Takeaways

• Data mappings show how order information is transformed from one system to another.
• The Order Details page provides end-to-end visibility into both upstream (source to Syncware) and downstream (Syncware to destination) data flows.
• Use this feature to validate field-level accuracy and troubleshoot sync issues.