Requirements Product Content Management (PCM) Version 1.0: 02.03.2026 1. Document History Revision Number Revision Date Summary of Changes Author 2. General Requirements This section describes the high-level business needs. The information, requests are based on the current Product DB and most of them have not been implemented yet. Before working on the new PCM, we should align on the new structure. For the following brands (Switzerland only): • Hyundai • Nissan • KGM • Maxus • Alfa Romeo • Fiat (separate brand) • Abarth (separate brand) • Jeep • Fiat Professional MG and Nissan Austria are currently out of scope! General # Prio Business Requirement Additional comment P001 MVP Modular Database • API interface needs to be available P002 MVP Performance • No long loading time • DB works quickly, no long waiting when creating new trims/engines/packages, adding/deleting new features, switching between functionalities, etc. P003 MVP Import • Manual one-time excel import for product managers to e.g. start a new pricelist (trims, engines, packages + translations), features and their translations, etc. • Updates need to be done in the Product DB P004 MVP Pricelists (structure, format, generation) • Structure for each brand should be the same • Look & Feel for each brand (e.g. fonts, colours, etc.) • Primary goal are html pricelists • Possibility to create PDF pricelists for print needs to be available as well P005 MVP Pricelist History • Pricelist history: throughout a Model Year, several updates are made, possibility to store/access older versions (e.g. end of each month automatically), with the possibility to access each version and download it if needed P006 MVP User experience • Easy access to desired model data – few clicks • Translations should be visible and accessible without going to another tab/overview • Easy to use for users; simple, logical structure and layout P007 MVP Brand / Model / Model Year / Type • Each Brand has their own overview • Product Managers have access to their own brand(s) - access needs to be modular • Model / Model Year / Type are necessary for each brand to distinguish the different data/pricelists P008 MVP Accessories Database • Accessories page – connected to Aftersales Accessories Database, so Accessories and WKR tables are automatically updated • Pictures of accessories would be a next step • Warranty extension tables could be a next step (currently screenshot of an image) P009 MVP Publishing Pricelists • There should be a possibility to enter/modify data in the PCM without that these informations are live on the websites • Therefore, a possibility to publish should be available • Also, publish all pricelists (all languages) at once should be possible (to reduce clicks) P010 MVP Download/Export • Possibility to download/export certain information/values from the Product Database via excel file; • Download all Pricelists (all languages) at once → reduce clicks P011 MVP Migration existing data • Migration for the above mentioned brands needs to be done for all the above mentioned brands (market Switzerland) P012 MVP Connectivity • The data from the new Product Database is the source for connected projects such as: Car Configurator / Car Specs Sheets / Lead Capture App / Brochures etc. P013 MVP Display of values • Not available “-” • Standard “circle filled” • If Price is stated - “1’000 CHF” • Optional “circle not filled” • P – if feature is within a Package available • In the pricelist status/availability can be shown for each Trim/Engine (exploded columns) or grouped. • Product Managers can easily decide and change the settings (default: exploded columns yes) P014 MPV Status • Draft • Current • Past • Archive Possibility to add (if needed) more. P015 MVP Salesforce ID • Salesforce ID (Test and Production) is needed P016 MVP Test Drive / Offer Request • Possibility for the Product Managers to set available for Test Drive and Offer Request available • Both infos are important for Dealer Websites (Model page-Baselballcards for each model) and should be connected to the DWS P017 MVP Range • Depending on the Brand, selection of Range via PCM • Type should be visible under this P018 MVP Flag Key • New • Upcoming (at the moment) P019 MVP Name • Model name as shown on DWS • Name needs to be available for all 3 languages (not in tabs but next or under each other) P020 MVP Download PDF Pricelist • In the PDF Settings should “Author” be filled-out, i.e. for example for Hyundai pricelists --> Hyundai Switzerland • When downloading a pricelist, the document name should be the “Market- Brand-Model-MY-Type Code” P021 MVP Clickable link • On the last page of the pricelist, we need a clickable link where the QR- Codeis displayed • Customers click on the QR-Code and/or text under the QR-Code and will come to the desired page • Generally, if we want to integrate QR- Codes on different levels this should also be possible P022 MVP Selection of important standard equipment • In the PCM it should be possible to define the most important features for each trim level and/or engines and then display them on a separate page in the price list • It should be able to select “additional to engine xy” as well so the main points compared to the first engine are shown (see example) • This would allow the content page to be automated (currently manually created) and eliminate the need for manual maintenance • This information about the most important standard feature should also be able to be used for the Car Configurator Example (Jeep=: P023 MVP Inheritance changed settings • Changes in information in the PCM should be passed down (inherited) from above, so that the changed information is also adapted accordingly in other (connected) places • Example: when e.g. changing an engine/trim from e.g. status “current” to status “past”, this information automatically changes in variants etc. P024 MVP Dealer Cockpit • For dealers via the Dealer Cockpit it should be possible to see also pricelists for older model years (and not only the newest) • Product Managers decide which type they want to archive via button “archive as version” --> still shown in Dealer Cockpit resp. Infos are still available for Car Specs Sheets P025 MVP Price/Disclaimer etc. changes • Currently, in the Product DB it is only possible to set the price and/or disclaimer etc. For each trim/engine or even variant (when it differs) • In order for the Product Managers to save time and effort to set the same disclaimer, price (for colours) - button to push the same disclaimer e.g. within a colour etc. Is required • The Product Manager decides if only for one trim or all trims (in the example of colours) • Also, for LCVs there are multiple variants, therefore, setting/changing a price requires a lot of time P026 MVP Mapping PCM – Astara Platform • A mapping PCM – Astara Platform (Salesforce) needs to be established and implemented (currently in progress on our side) • Goal is that Product Managers do not need to enter data in the PCM and Salesforce, but that they can export the needed data from the PCM and import it into Salesforce • An interface between the two systems is most probably not required • Therefore, the type of input/codes etc. Might be different/modified to the current Product DB Units # Prio Business Requirement Additional comment MVP Units in alphabetical order • Required to have units sorted alphabetically MVP Units • Consistency throughout all Brands and numeric units to separate decimal places with either a dot or comma --> to be confirmed what should be used • 1 or 2 decimal digits after a comma is displayed • Integers are not displayed with “.0” at the end MVP Units • Translations should be centrally possible (for Astara Admin) • Generally, the translations for all units are valid for all Brands Free text field – also texts in FR and IT should be possible. If no text is added for FR and IT, the DE text should be displayed for the other languages. MVP Adding feature with unit • When adding a data feature, users currently need to select the feature code and again the unit, even though the feature already has set the unit (in the feature structure) • To avoid twice the work and errors, this should not be the case Trims # Prio Business Requirement Additional comment MVP Trim Section • Each pricelist (model) needs to have a Trim section MVP Shift Trim • Possibility to shift trims and change order MVP Clone/copy trim • Possibility to clone/copy data of existing trims (no manual copying is necessary; changes can be made in fewer time) MVP Import • Manual one-time excel import for product managers to e.g. start a new pricelist • Updates need to be done in the Product Database MVP Adding new features • Should be easy for the Product Managers • In the current ProductDB you have to enter the code for the feature, only when starting to add the code some propositions show. In order to facilitate this feature for users, may be have e.g. a drop-down menue, where users can select and look for the desired feature to add. There may be other more user- friendly solutions from your side!? MVP New categories • In the current ProductDB, there is no real logic for the categories under “Trims” and the sequence is not following the one in the feature structure • Users should have the possibility to add new categories resp. To delete categories on their own Engines # Prio Business Requirement Additional comment MVP Engine Section • MVP Shift Engine • Possibility to shift engines and change order MVP Clone/copy engine • Possibility to clone/copy data of existing engines (no manual copying is necessary; changes can be made in fewer time) MVP Dimension page • Only engines are necessary to show for the dimension page Variants (Versions) # Prio Business Requirement Additional comment MVP Variants (Versions) section • Variants – combination of 1 trim and 1 engine • Can be possible that values change for specific variants (currently not the case in Switzerland) Shift Variants • Change order of existing variants Packages # Prio Business Requirement Additional comment MVP Packages • Possible to have 1 or more packages within a pricelist • Under trims in the pricelist it should be shown as “P” for package (if feature is included in a Package) MVP Package table • Under the price table, a table for packages should be visible Features / Feature Structure # Prio Business Requirement Additional comment MVP Features • Feature Structure for each brand • Features need to be available in 3 languages (German, French, Italian) • Translations must be easy to do and without clicks (not in separate tabs; can be side by side) • Adding new features should be easy and quick • Subsequent code adjustment must be possible MVP Visibility usage • Users must see which feature is used for which pricelist (categores, Category Items, Sub Category Items) MVP Selection / Sorting • Multiselect option, where several features could be selected and moved at once together to e.g. another category • Drag & drop of one/several features to e.g. another category MVP Search functionality • A search functionality to look for features and be able to select them • The search needs to work for categories, categoryItems, sub category items – for each level MVP Import • An import of features including their translations should be possible (at least in the beginning resp. when bigger changes are necessary) MVP Pricelist creation process • As a user, I would like to select multiple features in the feature structure and be able to send these features directly from there to the desired model • Therefore, a separate adding of features (one after another) under each model in trims/engines is not necessary (but possible) • This could save time in the current pricelist creation process MVP Sequence feature structure • In the current ProductDB, the feature structure defines the sequence of each feature in the pricelist for a brand (and thus each model of a brand). If a user wishes to override the sequence of features, he/she should be able to do so. MVP Deletion of features • Currently in the ProductDB, when a feature is deleted, it is not completely deleted in the pricelist if it was before in a package and was marked as “Yes”. • If this is the case, it should nonetheless be removed from the pricelists it was used (therefore it is important to see next to a feature for which models/pricelists it is used) Disclaimers # Prio Business Requirement Additional comment MVP Disclaimers • Disclaimers on different levels/position necessary: Per Feature / Per Category / Per Trim / Per engine • 1 (same) disclaimer for several features, categories etc. should be possible • Position of disclaimer is important and needs to be e.g. right after the category, end of page, etc. → customers do not need to search to see them • Available for Car Configurator, e.g. versions cannot be ordered and are only available from stock MVP Version page (Variants) • Disclaimer per Version • If filled, disclaimer will be shown below the pricelist • Numbers to identify the correct disclaimer to the correct version • Should be shown directly under price table • Disclaimer should be used for Car Configurator --> e.g. some versionsare only available e.g. “ab Lager” (from stock) MVP Identical disclaimers • Possibility to choose one disclaimer for different features/engines/versions/trims (all disclaimer options) and not have multiple identical disclaimers shown MVP Engine/Trims • Product Managers need to be able to put a disclaimer for each engine and each trim separately • The disclaimer (if any) should be shown with the price table (right under) MVP Category • Users should have the possibility to set a disclaimer for a category – visible for all models of a brand • It should also be possible to set a disclaimer per category per type • The disclaimer needs to be displayed right under each category and not at the end of all categories MVP Position of disclaimer • Disclaimers need generally be visible right under the category, price table, or on the same page where the feature is shown in a pricelist MVP Colours • Disclaimers for colour page needs to be available MVP CMS # Prio Business Requirement Additional comment MVP CMS • Easy to use for users • Easy workflow to create a new pricelist from scratch • Quick creation of content pages • Easy integration of images: images should not be distorted when correct size is used; quality of images for online pricelists • Decommission feature • Self-integration of disclaimers • Not connected to other brands/markets • Preview possible (no download/export is necessary) • Template for certain content pages for all brands • No link to other Pricelists MVP Texts/images • Possibility for texts and/or images to choose alignment (left, center, right) MVP Decommission Feature • For content pages it is required to have a decommission feature • If a brand creates a promotional page, it is possible to put a date until the promotional page should be active • After this date the content page is not shown in the pricelist anymore resp. The pricelist is published automatically without this specific content page Option: • Instead of automatically publish – inform someone about the need to check and publish the page (e-mail address can be added) MVP Linked entries • Linked entries should be possible, that is a page is valid throughout a brand (e.g. Accessories & SErvices page --> texts and images are the same for a brand) • However, some other pages or sub- pages may not be valid for the whole brand / all models and therefore users should easily be able to delink content. • Also, the creation of existing pricelists from scratch should be relatively easy and less time consuming for Product Managers LCVs # Prio Business Requirement Additional comment MVP Prices excl. VAT & incl. VAT • For LCVs it is required to show prices excl. VAT. However, legally it is also required to show prices incl. VAT • Workflow: enter the price once in the PCM (excl. VAT) and the price incl. VAT is calculated automatically (currently 8.1% VAT) • This workflow depneds if the car is a PV or LCV – option to flag models (PV or LCV) tbd Technical data • For LCVs it is desired to be able to have different tables for technical data in order to show different groupings o Technical data engine: group – length/height + engine o Weight: Grouping – Body + engine o Dimensions: Grouping – Body + Length/Height tbd Price table • Different grouping for LCVs – need to be defined again with the Product Managers (examples are available if needed) tbd Categories • For LCVs different categories might be necessary – need to be defined again with the Product Managers