When integrating Tharstern MIS with Infigo, correct configuration of products within Tharstern is essential for live pricing, estimates, and order creation to function correctly.

If products are not configured properly in Tharstern, customers may experience issues such as:

• No pricing returned in Infigo

• “Please call for price” messages

• Estimates failing to generate

• Incorrect configuration options appearing in the storefront

This article explains how Tharstern products should be prepared to work successfully with Infigo.

How Infigo Uses Tharstern

When a customer configures a product on the storefront, Infigo sends a pricing request to Tharstern via API.

Tharstern then:

1. Creates an estimate

2. Calculates the price based on the configured product type

3. Returns the price to Infigo

Each pricing request typically generates a new estimate in Tharstern, which can be viewed in the Tharstern estimate list.

If pricing fails to return, it usually indicates a product configuration issue within Tharstern.

Key Tharstern Configuration Requirements

1. Products Must Be Linked to a Product Type

In Tharstern, pricing logic is determined by the Product Type.

Each product used by Infigo must be linked to a valid product type capable of generating an estimate.

The product type controls:

• production processes

• materials

• finishing options

• cost calculations

If a product type cannot produce an estimate manually, it will not work through the Infigo integration.

2. Work Types Must Be Supported by the Tharstern API

Not all Tharstern work types are supported by the API.

For example, during testing it was identified that:

• Flexo work types were not supported by the API estimate request method

If an unsupported work type is used, pricing requests will fail and Infigo may display:

In these cases, customers may need to:

• create an alternative product type

• configure a compatible work type

• replicate the production setup using a supported estimate structure

Your Tharstern consultant can help determine which work types are supported.

Controlling Customer Options

One challenge with e-commerce integration is that Tharstern product types often contain more options than should be exposed to customers.

There are two common approaches to managing this.

Option 1 — Control Options Within Infigo

You can use Infigo product configuration to:

• hide certain attributes from the customer

• set default values for attributes

• restrict available choices

For example:

A Tharstern product type may include options such as:

• folding methods

• binding methods

• production processes

These can be defaulted automatically in Infigo so the customer never sees them.

This allows the same Tharstern product type to be used for:

• internal estimating

• e-commerce orders

Option 2 — Create Dedicated Product Types for E-commerce

Another approach is to create separate Tharstern product types specifically for Infigo.

These product types contain:

• fewer configuration options

• simplified production logic

• only the attributes required for online ordering

This approach provides more control but requires additional maintenance because:

• internal estimating product types still exist

• e-commerce product types must be maintained separately

Many organisations prefer this approach because it creates a cleaner integration between the storefront and MIS.

API-Only Product Types

Tharstern also supports the concept of API-only product types.

These product types:

• can be used by API integrations such as Infigo

• cannot be manually selected by internal estimators

This ensures that e-commerce products remain separate from internal estimating workflows.

Testing Tharstern Pricing

If pricing is not returned in Infigo, the best troubleshooting step is to test the estimate directly in Tharstern.

Steps:

1. Create a manual estimate

2. Select the same product type

3. Enter the same quantity and options

If the estimate fails in Tharstern, the configuration must be corrected before the product can work in Infigo.

Best Practices

When configuring Tharstern products for Infigo, we recommend:

• ensuring all products generate valid estimates

• limiting exposed configuration options

• testing product types manually in Tharstern

• documenting which product types are used for e-commerce

Proper configuration ensures accurate pricing and a smooth ordering experience.

When using Tharstern MIS with Infigo, pricing is typically retrieved in real time through the Tharstern API.

If Infigo cannot retrieve pricing successfully, the storefront may display the message:

This indicates that the system was unable to generate a valid estimate from Tharstern.

This article explains the most common causes and how to resolve them.

How Pricing Works Between Infigo and Tharstern

When a user selects options on a product page, Infigo sends a pricing request to Tharstern using the configured product mapping.

Tharstern then:

1. Creates a temporary estimate

2. Calculates pricing using the selected configuration

3. Returns the price to Infigo

If this process fails at any stage, pricing cannot be returned to the storefront.

Common Causes of “Please Call for Price”

1. The Product Is Not Correctly Linked to Tharstern

Each Infigo product must be linked to a valid Tharstern product or item code.

If the connection is incorrect or incomplete, pricing requests will fail.

Things to check:

• The correct Tharstern Item Code is entered

• The product is connected through the Connect configuration

• Live pricing is enabled if required

Once the product is correctly mapped, pricing requests should begin generating estimates in Tharstern.

2. The Product Type Cannot Generate an Estimate

Pricing in Tharstern is determined by the product type configuration.

If the product type cannot successfully generate an estimate, Infigo will not receive pricing.

To verify this:

1. Create a manual estimate in Tharstern

2. Select the same product type

3. Enter the same quantity and options

If the estimate fails manually, the product type must be corrected before it can work with Infigo.

3. Unsupported Work Types

Some Tharstern work types may not be supported by the API estimate request method.

For example, during testing it was identified that certain work types such as Flexo printing may not be supported by the API.

If a product type uses an unsupported work type, the estimate request may fail.

Possible solutions include:

• creating an alternative product type using a supported structure

• replicating the production process using a different estimating method

4. Missing or Incorrect Attribute Mapping

If the product configuration in Infigo sends attributes that Tharstern does not recognize, the estimate may fail.

Examples include:

• material options not defined in Tharstern

• finishing options that do not exist in the product type

• incompatible production settings

Ensure that all attributes used in the storefront match valid values within the Tharstern product type.

5. No Estimate Generated in Tharstern

Each pricing request from Infigo should create an estimate in Tharstern.

If no estimate appears in Tharstern, the issue may be related to:

• API connection problems

• incorrect product mapping

• missing configuration in the product type

Checking the Tharstern API logs can help identify the cause.

How to Test Pricing

A simple way to diagnose pricing issues is to perform a controlled test.

Steps:

1. Open the product page in Infigo

2. Change the quantity or configuration

3. Check Tharstern for a new estimate

If an estimate appears, the API communication is working.

If the estimate fails or does not appear, the configuration in Tharstern or Infigo should be reviewed.

Best Practices for Reliable Pricing

To ensure smooth pricing integration between Infigo and Tharstern:

• Ensure all products are linked to valid Tharstern item codes

• Confirm product types can generate estimates manually

• Limit product options exposed to customers

• Test pricing whenever new products are added

• Monitor API estimate creation in Tharstern

Following these practices helps prevent pricing failures and improves storefront reliability.