Connect: LabelTraxx

Introduction

Hello everyone, and welcome to this tutorial on integrating Label Traxx with the Infigo platform. Here, we'll explore how this integration streamlines your order processing by automating the flow of orders and shipment updates between the two systems.

We'll cover:

1. Integration overview and main purposes
2. Label Traxx and Infigo
3. Customer Mapping
4. Product Mapping
5. What happens when an order is placed in Infigo
6. Status Updates

Integration Overview and Main Purposes

The primary purpose of integrating Label Traxx with Infigo is to automate the transfer of orders and receive shipment status updates back. This integration ensures a seamless flow of information, reducing manual data entry and minimizing errors.

• Order Transfer: Orders placed on your Infigo storefront are pushed into the Label Traxx MIS as custom tickets.
• Shipment Updates: Shipment status updates from Label Traxx are automatically captured and reflected in Infigo.

This integration enhances operational efficiency by connecting your online storefront with your production management system.

Label Traxx and Infigo

Label Traxx

• A leading MIS/ERP solution for the labels and flexible packaging markets.
• Over 30 years of experience and more than 500 customers worldwide.
• Provides sophisticated management tools tailored to industry needs.

Infigo

• Offers a fully branded and customizable online storefront experience.
• Includes powerful editors for product customization.
• Allows customers to place orders and make payments upfront.

By integrating these platforms, you can offer an enhanced customer experience while streamlining backend operations.

Customer Mapping

Different Methods of Mapping Customers

To ensure accurate order processing, customers in Infigo are mapped to customers in Label Traxx.

1. Automatic Customer Creation and Mapping

   • When a new customer registers on your Infigo storefront, a corresponding customer is automatically created in Label Traxx.
   • This ensures synchronized customer data across both systems without manual intervention.

2. Manual Customer Mapping

   • You can manually map Infigo customers to existing Label Traxx customers via the external ID.
   • Adjust mappings at any time in the Infigo admin panel.
   • Useful for linking existing Label Traxx customers to their Infigo accounts.

Required Customer Information

To create customers correctly in Label Traxx during registration, the following fields are necessary:

• First Name
• Last Name
• Email
• Address Line 1
• Town
• State/County
• Zip Code
• Country

Additionally, the Customer Service Number and Sales Representative Number are configured in the Connect Plugin for the entire storefront.

Fallback Handling

• If an order is placed by an unmapped customer, a generic fallback customer code is used.
• This ensures orders can still be processed even without established customer mapping.

Product Mapping

How We Map Products

The integration uses template customers and template products in Label Traxx.

• Template Customer

  • A designated customer in Label Traxx that holds all the template products.
  • Classified as a template to organize products available for ordering.

• Template Products

  • Owned by the template customer.
  • Mapped to Infigo products or attribute combinations.
  • Ensures the correct product correspondence between Infigo and Label Traxx.

What We Need from Label Traxx

• A base template customer set up in Label Traxx.
• Template products assigned to this customer.
• Product numbers and details for accurate mapping.

What Happens When an Order Is Placed in Infigo

When an order is placed, the integration plugin performs several actions:

1. Order Splitting

   • Checks the configured split strategy in the plugin.
   • Supported Strategies:
     • No Splitting: Sends the entire order as a single ticket.
     • Split by SKU: Creates individual tickets for each product SKU.

2. Creating Custom Tickets in Label Traxx

   For each ticket, the following information is sent:

   • Customer Identifier (customerNumber): External ID of the Infigo customer.
   • Dispatch Date (shipByDate): Matches Infigo's calculated dispatch date.
   • Purchase Order Number (customerPONumber): Captured during checkout.
   • Contact Identifier (customerContactId): First contact of the customer in Label Traxx.
   • Shipping Address (shipAddress1): Captured in Infigo.
   • Billing Address (billAddress1): Captured in Infigo.
   • Priority (priority): Configured for the storefront.
   • Line Items (items): Details of each product in the order.

3. Line Item Details

   For each line item:

   • Product Number (productNumber): From the cloned template product.
   • Product Price (productPrice): Unit price charged in Infigo.
   • Product Quantity (productQuantity): Selected in Infigo.
   • Product Type (productType): Label Traxx product type.
   • Product Weight (productLineWeight): Weight of the cloned product.
   • Product Description (productDescription): From the cloned product.

4. Product Cloning

   • Clones the template product for the specific Label Traxx user.
   • The cloned product is a one-off for the ticket and marked inactive after shipment.

5. Artwork Handling

   • If the product includes artwork (e.g., PDFs, MegaEdit designs), it's linked to the ticket item.
   • Provides:
     • Artwork URL: Link to download the asset.
     • File Name: Combination of Label Traxx ticket item ID and Infigo job ID.
     • Ticket Linking: Associates the artwork with the correct ticket.

Note: Only mapped products are included when creating tickets.

Status Updates

The integration captures shipment status updates from Label Traxx:

1. Monitored Status Types

   • Shipped
   • Ship Complete

2. Updating Infigo Orders

   • Marks corresponding order line items in Infigo as shipped.
   • If all items are shipped, the entire order is marked as shipped and closed.

3. Product Deactivation

   • Cloned Label Traxx products are marked inactive once the order is completed.
   • Helps maintain an organized product catalog.

4. Tracking Information

   • Currently, tracking codes are not captured or transferred to Infigo.

Conclusion

In this tutorial, we've covered:

• Integration Overview: How orders and shipment updates flow between Infigo and Label Traxx.
• Customer Mapping: Automatic and manual methods to synchronize customer data.
• Product Mapping: Using template customers and products to align offerings.
• Order Processing: What happens when an order is placed, including ticket creation and data transfer.
• Status Updates: How shipment statuses are captured and orders are updated in Infigo.

By integrating Label Traxx with Infigo, you enhance efficiency, reduce manual tasks, and provide a better experience for both your team and customers.

Thank you for watching. If you have any questions or need assistance, please contact our support team.

Information sent with each ticket:

1. Create a Base Template Customer:
• Purpose: Acts as a holder for all template products that will be available through Infigo.
• Action: Set up a new customer in Label Traxx designated as the template customer.
2. Set Up Template Products:
• Purpose: These are the products that will be mapped to Infigo products.
• Action: Assign all the products you wish to offer on your Infigo storefront to the base template customer in Label Traxx.
3. Set Up API Access:
• Purpose: To allow communication between Infigo and Label Traxx.
• Action: Ensure that API access is enabled and properly configured in Label Traxx.

1. Template Product Details:
• Purpose: Enables accurate product mapping between Label Traxx and Infigo.
• Information Needed:
• Required field listed as "uniqueProdID" in Label Traxx API
• Action: Gather a list or spreadsheet containing product identifying details.
2. Customer Service Number and Sales Representative Number:
• Purpose: Required for customer creation and order processing in Label Traxx.
• Action: Input these numbers to Infigo for plugin configuration.
3. API Credentials and Access Information:
• Purpose: Allows Infigo to communicate with Label Traxx via the API.
• Information Needed:
• Base URL
• API Token / API Key
• Action: Input all necessary API access details to Infigo.
4. Existing Customer Mapping Information (if applicable):
• Purpose: To map existing Label Traxx customers to Infigo customers.
• Information Needed:
• Required field listed as "customerNumber" in Label Traxx API
• Action: Provide a mapping document or spreadsheet.

Connect: LabelTraxx Updates – January 25

We’ve made a series of improvements to our LabelTraxx integration to streamline order management, simplify shipping workflows, and provide greater flexibility for your team. Here’s what’s new:

1. Automatic Product Inactivation

What it does
Whenever an Infigo order is fully completed, canceled, or closed, any associated products in LabelTraxx are automatically deactivated.

Why it’s useful
This helps prevent clutter in LabelTraxx by removing products that no longer require any action, reducing confusion for your production teams.

How to implement it

1. Log into your Infigo Admin panel.
2. Go to Connect Plugins > Click Configure [Connect: LabelTraxx].
3. Ensure the setting “Inactivate product when order is closed” is turned on (if available in your settings).
4. Once enabled, the system will automatically manage the product status upon order closure.

2. Tracking Number Sync

What it does
Infigo now automatically retrieves tracking numbers from LabelTraxx once shipping labels (packing slips) are generated in LabelTraxx. The tracking number is then displayed in Infigo for the associated order.

Why it’s useful
It eliminates manual data entry and ensures real-time visibility of shipping statuses in Infigo, making it easy for you and your customers to track shipments.

How to implement it

1. When packing slips and tracking numbers are created in LabelTraxx, wait a short period for Infigo to poll the data. The tracking info will appear in the order details in Infigo.

3. Partial Shipping Updates

What it does
If an order ships in multiple batches (partial shipments), Infigo now automatically updates the status of those line items to “partially shipped.”

Why it’s useful
This lets you accurately communicate which items have shipped and which are still in production, improving visibility for both customers and internal teams.

4. Fallback Customer External ID

What it does
LabelTraxx requires a “Customer ID” for every ticket. We’ve expanded our mapping so that Infigo checks the customer’s assigned LabelTraxx ID, then any department-based ID, and finally uses a global fallback if neither is found.

Why it’s useful
This ensures that tickets can still be created in LabelTraxx even when a customer or department is not mapped to a specific external ID.

5. Artwork File Name Pattern

What it does
We’ve standardized the file naming convention for your artwork files to:

Why it’s useful
This helps avoid invalid file name characters and makes file references consistent in LabelTraxx, simplifying production workflow and reducing upload errors.

6. Default Ticket Status Configuration

What it does
Choose the default status that newly created LabelTraxx tickets will have. You can pick from Open, Credit Hold, Done, or Hold.

Why it’s useful
Allows for better control of how tickets enter the LabelTraxx system, matching your internal processes (e.g., starting tickets as “Open” vs. “Hold”).

How to implement it

1. In Connect Plugins > Connect : LabelTraxx, locate the “Ticket Status” dropdown.
2. Select the status that makes sense for your workflow.
3. Save settings. New tickets will use the selected status automatically.

7. Invalid Priority Handling

What it does
Previously, creating a ticket with an unrecognized priority in LabelTraxx would cause an error and block re-triggering. Now, if a priority is invalid, simply correct it and the system will successfully re-trigger the ticket creation.

Why it’s useful
Prevents tickets from getting stuck due to a simple mistake or misconfiguration, saving you time and hassle.

8. Field Length Restriction Improvements

What it does
LabelTraxx enforces a 25-character limit on Country/State fields. Infigo now automatically passes ISO code abbreviations where possible to avoid exceeding this limit.

Why it’s useful
Prevents ticket creation failures for users in countries with long names or states that exceed LabelTraxx’s character limit.

9. Order External ID Tokens & Placeholders

What it does
You can now embed the LabelTraxx ticket number (or external order ID) in Infigo message templates and job tickets using tokens like %Order.ExternalId.LabelTraxx% or placeholders like %ExternalId_LabelTraxx%.

Why it’s useful
It allows you to reference LabelTraxx IDs in emails or printed tickets, making tracking and identification easier across systems.

Individual Search Words

synchronization, integration, ERP, mapping, automation, tracking, linking, templates, cloning, shipment

Alternate Search Phrases

connect with Label Traxx, order sync with Label Traxx, Infigo Label Traxx integration, automated order sync, Label Traxx customer mapping, Infigo product synchronization, order status tracking, seamless order processing, MIS integration setup, linking products with Label Traxx