Connect: Label Traxx

Who are Label Traxx?

With over 30 years experience and over 500 worldwide customers Label Traxx is one of the leading MIS/ERP solutions for the labels & flexible packaging markets. They have built their own sophisticated MIS and we have built a plugin that integrates with it.

You can find out more about the company and their software here

 

Overview of our integration

The purpose of this integration is to push orders into the Label Traxx MIS and receive shipped status updates back.

Our Infigo platform offers the ability to provide a fully branded and customisable website experience, combining this with its powerful and flexible editors and the ability for customers to make transactions and take payment upfront for all orders that are placed. 

Orders will be then placed as tickets within LabelTraxx for the Infigo Customer which is linked to a LabelTraxx customer. If the Infigo customer placing the order does not have a pre-defined mapping to a Label Traxx customer, a fallback customer code can be specified and used instead.

When a new customer registers on the Infigo storefront this will automatically trigger a Label Traxx customer to be created and automatically mapped to the new infigo customer.

Status updates for shipping are captured automatically via the API.

 

Key Integration Features

  • Our integration uses a base template customer in LabelTraxx that template products will be assigned to
  • You can then map these Label Traxx template products to your Infigo products or attribute combinations
  • Infigo Customers are mapped to LabelTraxx users
    • If an order is placed by an unmapped customer, a generic fallback customer code will be sent instead.
  • When a new customer registers in Infigo a new customer will be created automatically in Label Traxx and a mapping will be created between the two systems for that customer.
  • Orders placed in Infigo will create custom tickets in LabelTraxx
    • We will split the Infigo orders optionally in multiple tickets based via split strategies. Currently we support:
      • No splitting
      • Split by SKU
    • We will create a copy of the template product for the current LabelTraxx user as a one off for the ticket - that copied template product will then be marked as inactive once the order has been shipped.
    • For line items with an artwork (Static PDF, MultiPart, Infigo, MegaEdit) - the artwork file is made available to the custom ticket item
  • Status updates from LabelTraxx to Infigo
    • when the order is being completed, we will mark the cloned LabelTraxx products as inactive
    • we will carry over the tracking code from LabelTraxx to the Infigo order

Template Customer and Template Products

In order to provide products from Label Traxx to map to products in Infigo (or attribute combinations for flexible selections), the concept of template customer and products has been introduced.

There is nothing specific about those other than convetion to create a new customer in Label Traxx to be classified as a template, holding all the products other can order.

Products owned by that user will then be able to be mapped to Infigo products.

Customers

Customers are created in LabelTraxx automatically during registration. or mapped via the external id for the Infigo customer. Mapping can be adjusted manually in admin at any time.

To create customers correctly in LabelTraxx during registration, the following fields are necessary (captured during registration):

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

In addition, we also need the Customer Service Number and Sales Representative Number which are both configured in the Connect Plugin directly (same value for the entire storefront).

 

Custom Ticket Creation

When an order is placed in Infigo, the plugin will check the selected split strategory (plugin configuration).

NOTE: only mapped products will be taken into account.

Currently it does either send the whole order or split by SKU. Meaning it will create individual tickets for each set of products with the same SKU.

For each ticket we will send:

Name LabelTraxx API property Description
Label Traxx Customer Identifier customerNumber The external id for the current Infigo customer
Dispatch Date shipByDate Matching Infigo's calculated dispatch by date for the Infigo order
Purchase Order Number customerPONumber The PO number captured during checkout.
Label Traxx Contact Identifier customerContactId The first contact of the customer in Label Traxx will automatically be used as the contact
Shipping address

shipAddress1
shipAddress2
shipCity
shipCountry
shipState

shipZip

Shipping address captured in Infigo
Billing address

billAddress1
billAddress2
billCity
billCountry
billState
billZip

Billing address captured in Infigo
Priority / Grouping

priority

Configuration option in the plugin for the entire storefront
Line Items

items

 
-> Product Number

productNumber

Label Traxx product number (of the clone created from the original template product.
-> Product Price

productPrice

The unit price for the product charged for in Infigo
-> Product Quantity

productQuantity

The quantity selected in Infigo for that product
-> Product Type

productType

Type of the LabelTraxx Product
-> Product Weight

productLineWeight

Weight of the cloned LabelTraxx Product
-> Product Description

productDescription

Label Traxx Product description of the cloned product

This supports all type of Infigo products and it will create a ticket item for each.

If the Infigo product type has an art file (Static PDF, MultiPart, MegaEdit, Infigo) - it will also provide a link to that artwork to Label Traxx with the following info:

  • Art Work URL: to download the full asset
  • File Name: combination of the (LabelTraxx) ticket item id and the (Infigo) job id
  • The ticket item and the ticket id to link to

We currently do not place orders for Label Traxx stock products specifically. Mapped Stock Products in Infigo are pushed to LT as part of the custom ticket without an artwork provided.

Status Updates

The Integration will check for status updates of the types

  • Shipped
  • Ship Complete

and if it sees those, will mark the order line items which are identified by the ticket items in the request as shipped. If all items in an order are marked as shipped, the order will be marked too and closed.

Tracking information is currently not captured.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.