🚀Connect: Tharstern Problem Solvers 🚀

What this article is for

A Product Type can exist in Tharstern, but still not appear in the Connect Link dropdown in Infigo when you are trying to link an Infigo product to Tharstern. This article explains why that happens in the current integration flow described in the ticket, and what to check.

The key concept, how the dropdown is populated

Infigo does not populate the Connect Link dropdown directly from Tharstern Product Types.

Instead the flow is:

1. Infigo calls Tharstern’s /api/products endpoint.

2. Tharstern returns a list of inventory items, each may include a ProductTypeID if a Product Type is associated.

3. If an inventory item is returned with ProductTypeID > 0, Infigo then uses that ID to make a second call to /api/producttypes, to retrieve the Product Type configuration for that ID.

4. The Connect Link dropdown in Infigo is populated only from the inventory items returned by /api/products, not directly from Product Types.

What this means in practice

If Tharstern does not return the expected inventory item in the /api/products response, then:

• The related Product Type never appears in Infigo.

• You cannot link your Infigo product to the correct Product Type.

• It looks like an Infigo issue, even though the absence originates upstream in Tharstern.

Why this often results in confusion

Customers often assume Product Types should appear directly from /api/producttypes. Instead, the integration requires the Product Type to be present via inventory returned by /api/products first.

Troubleshooting checks

Check 1: Confirm the Product Type is actually reachable via /api/products

The dropdown is sourced from /api/products. The most important question is:

“Is Tharstern returning an inventory item for this Product Type in /api/products?”

If the answer is no, the Product Type will not appear in Infigo.

Check 2: Confirm whether the missing data is upstream

Tharstern may not return the expected inventory item in /api/products. In that situation the root cause is upstream, not in the Infigo dropdown logic.

Check 3: Expectations about what Infigo can safely do

Overriding Tharstern data or trying to infer missing Product Types can cause mismatches in estimates, costing, or order creation. That is why the current behaviour depends on what Tharstern returns.

What to escalate, and where

Escalate to Tharstern when the expected inventory item is missing from /api/products.
Escalate to Infigo when the inventory item is confirmed as present in /api/products, but Infigo still does not surface it.

This article details various prerequisites which should be implemented and observed when configuring and mapping Tharstern with Infigo.

This may not constitute a complete list, and we will add to it when new points of interest emerge.

Contact Infigo Support if in doubt about your Connect: Tharstern configuration.

Prerequisite checklist for customers and implementers

1) Product Type finish sizes must be valid in Tharstern

We have seen examples where the Product Type has an error similar to: “Finish size code A4 does not exist.” This can be resolved by setting a default finish size and adding available sizes in Tharstern.

Practical guidance:

• In Tharstern, open the relevant Product Type and check for problems or errors.

• Ensure a valid default finish size is set.

• Ensure the relevant finish sizes are available on the Product Type.

This could also apply to areas other than finish size.

2) Size must be supplied, or there must be a default size available

We have observed estimate request failing with “No size supplied. No default size.”. In these cases, some size needs to be supplied within Tharstern. Once complete, check the Infigo Connect Link popup for a relevant attribute and mapping.

Practical guidance:

• In Infigo, open the Connect Link mapping popup for the product you are configuring.

• Look for the part of the mapping where a size can be supplied or selected.

• If size is not appearing, treat that as a signal to review the Product Type configuration in Tharstern, since Product Type size configuration changes can affect what appears in the Infigo mapping flow.

3) Paper codes must be applied, or a default must exist

We have observed estimate request errors such as: “No paper codes applied and no default available.”

Practical guidance:

• If you see that error, review the Tharstern Product Type and its paper related configuration, since the error indicates no paper codes are applied and there is no default available.

4) Product Type constraint errors must be resolved in Tharstern

Messages have been observed such as “Signature is too large to fit on the sheet”. This should be treated as a Product Type issue to investigate in Tharstern.

Practical guidance:

• If Tharstern returns a Product Type constraint error, the resolution is on the Tharstern Product Type side, not in the Infigo mapping UI.

Making Tharstern changes visible during mapping

These steps should be following in order to utilise any alterations you have made to your Tharstern setup and it’s impact on what is being received into Infigo.

• Return to Infigo.

• Close the current window Connect Link pop up.

• Open the Connect Link popup again.

What this article is for

Some Tharstern items have a packed in quantity, for example 100. This can sometimes cause confusion in ordering and pricing if the Infigo product is set up in units when it should be presented as packs.

Common Scenario

• A Tharstern product has a packed in quantity (eg 100).

• You try to order quantity 1 in Infigo, meaning “one pack of 100”.

• You get an error stating they must order in multiples of 100.

• When you order 100 instead, you may see something like “100 x 100”, which creates confusion in expected quantity and pricing.

The key concept

• Packs are how you present quantity to the end customer.

• In the back end, everything is units.

• Configuration such as minimum quantity and default basket quantity is handled in units, even if the UI is presenting packs.

How to configure an Infigo product for packed items

Step 1: Set Quantity selector mode to Packs

In the product variant settings, change Quantity selector mode from Units to Packs.

Learn more about Packs:https://academy.infigo.net/p/909

Step 2: Set Packing quantity to match the Tharstern packed in quantity

If the item is packed in 100, set Packing quantity = 100.

The intent is ordering one pack, but each pack contains 100.

Step 3: Resolve the configuration validation warnings

Several warnings may be present:

• “When using order by quantity, the default quantity must be a multiple of order by quantity.”

• “Quantity based pricing could not be used in combination with packs selector.”

Practical guidance:

• Adjust your default and minimum quantities so they align with your order by rules.

• If you need packs selector mode, be aware that quantity based pricing cannot be used in combination with packs selector.

Step 4: Update tier pricing so it matches the packed model

After switching to packs and using unit based configuration, it is recommended to adjust tier prices that make sense for packed quantities, explicitly suggesting values like 100, 200, 300 and removing smaller tiers that do not make sense in this model.

Learn more about tier pricing: https://academy.infigo.net/p/1858