Skip to main content

FNP menu pricing in ViSN

FNP means Fleet National Pricing in ViSN. It supplies vehicle-specific service and repair menus, labour times, parts and, where the integration provides them, agreed menu prices. Suppliers select these descriptions on an enquiry's jobsheet. The vehicle manufacturer determines the provider; the enquiry's network terms and, for OEC/Ford, customer fleet level and supplier band determine what is available.

Reading guide

PageUse it to
ConfigurationEnable the relevant customer and supplier settings, choose bands and fleet levels, and verify the jobsheet workflow.
Providers and dataUnderstand manufacturer coverage, integration types, files, imports, tables and data dependencies.
Enquiry pricing flowFollow enquiry creation, provider lookup, saved descriptions, price filtering and jobsheet calculations.
Debugging missing pricingInvestigate an individual report that FNP did not load, including logs, database checks and recovery.
FNP bandsLook up the allowed band strings and OEC/Lex price-column rules.

Integration types and manufacturers

There are three provider identifiers and five manufacturer-specific retrieval paths:

IntegrationProvider identifierManufacturers with a current code pathMenu source and pricing behaviour
ModulusMODULUSCitroen, PeugeotImported vehicle and menu files. Resolve the vehicle identifier, then retrieve its menu rows. No OEC band filtering.
OECOECVauxhallImported VIN-specific menu rows containing fleet-level and band prices. The customer fleet level and supplier band select the applicable cost.
FordOECFordFord's own imported datasets and a PostgreSQL function produce descriptions, parts and region prices. It shares OEC's provider identifier and filtering flow.
Manufacturer filesOEMKiaImported vehicle and menu files joined by vehicle_id, using VIN. No OEC band filtering.
VWG live catalogue with imported reference dataOEMAudi, Skoda, Seat, Cupra, VolkswagenFetch packages from VWG using the VIN and supplier partner information; enrich parts and fluids from imported tables. Jobsheet prices are assembled from labour and parts/fluids rather than an OEC band price.

Ford is not a fourth provider enum; VWG is not a separate provider enum. Conversely, sharing OEM does not mean Kia and VWG use the same retrieval mechanism. The provider guide explains each path and its dependencies.

How the pieces fit together

Walk-in creation loads descriptions inline in the callable service. Other enquiries use the onEnquiryCreatedHandler Firestore creation trigger, which calls the provider endpoint in the callable service. Both paths save results under the enquiry's ancillary provider descriptions. Opening the jobsheet reads that saved result; it does not repeat the import or provider lookup.

What needs to be enabled or present

FNP availability depends on several separate pieces of state:

  1. Supported manufacturer and matching supplier franchise. ViSN resolves the provider from its manufacturer list. The supplier must offer that make in the applicable network terms.
  2. Supplier FNP enabled. The selected rate card determines whether ViSN reads DI network terms or customer-specific supplier terms. Editing the other network's terms will not fix the enquiry.
  3. Customer configuration. Integration entries support provisioning and VIN exports; customer fleet level controls OEC price selection. There is an implementation exception: the current loader bypasses the lease integration enabled check for the supported provider/manufacturer pairs listed above. It still requires the supplier and franchise checks. Do not use the lease switch alone to diagnose availability or to guarantee that loading is disabled.
  4. Vehicle and provider data. File integrations need matching imported records; VWG needs the VRM lookup VIN, supplier PPSO partner key, matching credentials and catalogue response.
  5. A saved menu for this enquiry. A later import or settings change does not automatically replace previously saved descriptions.
  6. Applicable prices. OEC/Ford need a matching fleet level and string band. VWG fluid prices are entered by the supplier; missing non-fluid parts prices mark a package incomplete and prevent selection until its upstream data is corrected.

Follow Configuration for the exact screens, fields and verification steps.

Terms used in these guides

TermMeaning
Menu / provider descriptionA selectable service or repair package with its description, labour time and optional price or parts data.
ProviderMODULUS, OEC or OEM, selected from the manufacturer mapping.
Manufacturer / make / franchiseThe vehicle make determines the provider; a matching supplier franchise is a separate eligibility requirement.
Fleet levelCustomer pricing group used for OEC/Ford: Service4Fleet, Platinum Service4Fleet or Lex Auto. The Platinum group's internal key is service4FleetPlatinumArval.
Supplier bandfnp.fnpBand, for example Band 2 LA3 or Ford Region 22; selects an OEC/Ford price within the fleet group.
Network termsEither diNetworkTerms on the supplier service unit or the customer's supplier service-unit record. These include fnp and franchises.
Enquiry snapshotTerms copied onto an enquiry, including fnp and fleetLevel, used later when retrieving prices. These can differ from today's configuration.
Ancillary descriptionsProvider menus saved separately from the enquiry, at ancillary/enquiries/descriptions/{enquiryId}/{provider}/descriptions.
Jobsheet / joblineWork and charges selected for the enquiry. Finding a menu and applying it to a jobline are separate steps.

FNP sits alongside HaynesPro, Glass and ViSN descriptions. A HaynesPro description or labour time being available does not prove FNP data loaded. Similarly, an FNP menu being visible does not prove every constituent part has a price. See Jobline descriptions for the wider description model.

Systems involved

RepositoryResponsibility
repair-serve-webSupplier jobsheet, eligibility request, saved-menu request and selection/calculation UI.
repair-serve-adminCustomer integrations/fleet level and supplier administration settings.
repair-serve-callableInline walk-in loading, eligibility, provider retrieval, Cloud SQL reads, VWG API access and saved-menu filtering.
repair-serve-functionsBackground loading after enquiry creation and VIN exports for file providers.
fnp-import-managerFile-provider validation and imports into Cloud SQL, including Ford datasets and VWG parts, fluids and VIN blacklist imports.
import-managerSupplier and network terms imports, including the supplier FNP flag, band and franchises.

The individual guides include source references and links to the existing file specifications. Environment-specific job names, deployed revisions and live data must be checked in that environment.

Implementation references