How to check if it is a TSU problem
TSU problems
Is TSU down?
TSU not in sync with websites
TSU not returning the right data
Sort order update
Bonus: TSU as a check tool
1. Is TSU down
Unavailable Tyre Selector is a common problem and very often the core of the problem is linked to Apostrophe and not TSU.
The first and most important thing to check, before alerting Tyredating team, is if Tyre Selector test page is working correctly and send the results (all the information about how to connect, all the links and the basic user guide can be found in TSU Test Environment DEV/PROD section).
All the Apostrophe instances are connected to TSU Production Environment, not the Dev one and this; is the one you need to check!
What you need to do is preform the same tests as on the website:
when TSU Production is working fine -> this means that the problem is related to Apostrophe platform and there is no need to ask Tyredating to interfere
when TSU Production is not working -> it's a Tyre Selector problem, which must be solved by Tyredating (you need to contact Rémi Farrot and Florian Lemarchand, by mail. It is also possible to alarm them via Slack dev-tsu channel, but never skip the mail).
2. TSU not in sync with websites
TSU API and APOS PROJECTS should be in sync and receive a Datastream update at the same time. Nevertheless, it is not always the case.
If you are waiting for a new product and you can see on the website (in the pieces), but it is not visible in the Tyre Selector, please contact Tyredating via mail asking to make checks on their side and relaunch their importers if needed.
3. TSU not returning the right data
The first thing to keep in mind is: TSU is connected to the Datastream. Everything you see in the TS comes from Datastream (if you see any differences, please check point 2).
Now, let's imagine you are doing some TS checks. When making going through your searches, you realize that the information shown is not correct.
There are two possibilities:
Data is not correct - it means you need to make some Apostrophe checks. Apotrophe pieces - the same incorrect information can be found in the Tyre pieces, such as incorrect tyre category? If it's the case, it is not TSU problem. The problem comes from the databases and needs to be corrected by the Business.
TSU is recommending incorrect tyre. Behind each project, TSU is using a specific algorithm (TSU rules giving us the possibility to match a vehicle with a tyre). They are documented within Gitbook or can be found in the TSU-Admin interface. If you spot any error in the searches, please contact TSU support and Data Team
For any evolutions, new rules for sorting tyres, warnings, association rules etc. Please send your business brief to Data Team for review and prioritization.
4. Sort order update
The sort order is being updated by Kamila.
If you want to learn how to do it and do it on your own, all the information can be found in the sort order chapter.
TSU as a check tool
As we mentioned already, TSU is connected to the Datastream. Sometimes it is easier to make some checks using TS test page, then within Apostrophe or Lizeo Back Office.
What can we check within TSU:
information missing from Apostrophe - is it a data or CRM problem Ex: my tires are coming up on the TSU under the wanted usage but they won’t show on up under that usage on pre-prod (as Transalp 2 on the screenshot).
vehicle related information Ex: a tyre is not showing up on this particular vehicle because a vehicle data related information keeps it from popping (Ex: exclusion of light truck tyres under a passenger car search).
categories/usages availability for tyres
products available for the chosen locale
sort order - if it matches with the one provided by the business
basic tyre info
Last updated
Was this helpful?