B2B - OHT/TLD (includes AG)
Objects
B2B Data model can be found on what we called the 'Rosetta table', accessible here: https://docs.google.com/spreadsheets/d/1-UQGdHEJ8unHAk79phP1hamCKlcgMzLF3LNGxSWoDdY/edit#gid=0 There are 4 types of objects in the B2B Data model:
Common
Tyre
Dealer
Retread (in build)
'Common' attributs
Those attributs are always attached to an object no matter what is the object behind. Indeed, a feed will always have: - _id = database ID of the object - createdAt = creation of an object in the feed - updatedAt = latest reception of an object in the feed - id = - globalId = Unique identifier of a product ( is not present for a dealer) - active = is the object active or inactive in the database - brand = For which brand does this object exist (enum) - productLineActivity = For which business line does this object exists (enum) - country = For which country does this object exists - lang = For which language does this object exists - createDate - updateDate - provider = who pushes the feed (Lizeo, Salsify, other?)
Specificities
B2B data model has been build to take into account AG, TK, GC, and mining tyres. It is quite exhaustive but takes at the same time into account tyres from all business lines.
Tyres object
tyre.templateTDP
=> It drives the template of TDP. Depending on the value, we do not display the same informations in the SKU table.
Export rules
A product is exported only if:
It is in the product template
There is a template TDP
There is a univers - vehicle type
There is an usage
Retread object
Being developed
Import/Export rules
Import: to import only the tyres that meet the following criteria:
1.MFG
should be = MRT
in 'RETREAD_MASTER' tab
2.Market_CM
should be = USC
or USA
in 'RETREAD_MASTER' tab
3.Brand_Website
should be = MRT
or MRTO
in 'RETREAD_MASTER' tab
4.Brand_Website
should be = PMRT
or MMRT
in MCPL
tab
Then for Apostrophe export, to consider a tyre as active
= yes here are the rules:
5. stock_status
= A
in 'RETREAD_MASTER' tab (product level)
6. stock_status
= A
, or T
in 'MCPL' tab (article level)
7. Tire_release
should have a date in the past or no date in 'RETREAD_MASTER' tab
Then for Apostrophe export, to consider a tyre as active
= no but to still send it in the export:
8. stock_status
should be = T
in 'RETREAD_MASTER' tab (product level) 9. stock_status
should be = T
in 'MCPL' tab (article level)
Other rule:
10. if coming soon
attribut is on, then we should export the softlaunchdate
(column to be added soon on Access database)
Dealer object
B2B Dealer data model is similar to B2C one and there are few rules on the export:
GooglePlace ID
is being generated by Lizeo based on "latitude" and "longitude" fieldsisPL
|isGC
|isAG
| - is generated based on rules listed belowdealerPin
- is generated based on the rules mentioned below. The pin can take four values: MSCN, MTRTD, MTD and AG.
Dealers universes (USA)
On B2B model we have three possible universes: PL (Poids Lourds), AG (Agriculture) and GC (Génie Civil). In the US case, this three universes are being determined based on the following columns from the US Dealers Database:

At least one of the mentioned services must be marked as true in order to qualify a dealer as a part of the universe.
Universes are being shown using badges:

There is also a separate badge for retread dealers:

The rule behind this badge is ProMRT
and/or ProOliver
dealer must be marked as True.
Dealer Pins (USA)
There two values for dealer pins:
Michelin Commercial Service Network (MSCN),
Michelin Tire Dealer (MTD).
Rules were created in order to assign only one pin to a dealer:

Last updated
Was this helpful?