Skip to main content

Discovery Template

Learn how to fill out your discovery list to get started risk-managing your suppliers, customers and own business units in Prewave

Nathanael avatar
Written by Nathanael
Updated over 3 weeks ago

Key Users and Quota Managers are the only ones that can upload the discovery template via the platform

Prewave Discovery Template – How to Get Started

Introduction

Getting started with risk management in Prewave begins with preparing and uploading your discovery template. This template forms the foundation for monitoring your suppliers, customers, and even your own business areas across the globe.

Each entry in the discovery template represents a Site - a physical location where business operations are carried out, such as a manufacturing plant, warehouse, distribution center, office, or retail outlet. By providing these details, you enable Prewave to assess risks, deliver insights, and connect your organization to a global network of monitored Sites.

To help you get started, we provide both a pre-structured template and a guideline document. These resources explain the required fields and structure, ensuring that your discovery template is complete and ready for processing. Filling out the template carefully is essential, as incomplete or incorrect information may prevent successful discovery of your Sites and slow down your onboarding process.


The number of Sites you can connect with depends on the limits defined in your contract. Please reach out to your dedicated Customer Success Consultant or Account Executive if you have questions or want to expand your scope.

You can download the current template here

You can download the guideline here


General Information

  • What is a Site?
    A Site refers to a physical location where an organization conducts its main operational activities, such as manufacturing plants, distribution centers, retail stores, transportation hubs, warehouses, or offices.

    • If a Site is not listed in the Prewave directory, you must provide a correct and complete Site list (see Appendix 1: Parameters).

    • Alternatively, you can use the Add-to-Directory function in the platform.

    • Prewave will not support:

      • Suppliers with an incomplete dataset

      • Sites associated with private/natural persons (e.g., home offices)

      • Sites where essential details are missing

      • Sites whose existence cannot be validated during Discovery

    • Prewave may refuse or later delete such Sites.

    • You can find more information about our Validation here.


Behavior of Special Fields

    • This field is now mandatory.

    • Values SUPPLIER_CUSTOMER and NONE are no longer supported.

    • Split into three fields.

    • All values will be joined together.

    • Each collection can be mapped to a Prewave industry or commodity for scoring.

industry / commodity

  • Split into three fields.

  • All values will be joined together.

  • You can provide:

    • A valid Prewave Industry (see the Value Sheet in the Template)

    • A valid ISIC code (see the Value Sheet in the Template)

    • Or a valid HS code (see the Value Sheet in the Template)

  • Unlike collection_name, no collection will be set up for these values.

CSDDD Use Case: For CSDDD compliance, providing HS codes is mandatory.

  • contact

    • Split into three fields.

    • All values will be joined together.

    • Entries must be valid email addresses.

  • website

    • Must be a valid web address.

    • The domain must be associated with the supplier.

  • external_reference_id & external_reference_type

    • These are now optional only.

    • Cannot be used as sufficient input on their own.

  • overwrite

    • If marked with Yes, existing data will be overwritten.

    • Use with caution: rollback may not be possible depending on the case.

    • If not wanted, mark with No or leave empty.

    • You can request a screening directly during the upload process.

    • This allows critical suppliers to be screened immediately without delays.

    • If not required, leave the field empty.

  • Multiple Reference Numbers (Supplier IDs)

    • Multi-values for your_reference are not supported.

    • To store multiple references:

      • Duplicate the row with the same name/address.

      • The same Site will be reused, and references added.

    • Important: Spend and impact data are stored per reference.

      • If you don’t want spend values to be summed, remove them from one of the duplicated rows.

The full list of parameters can be found in the template. The color coding is consistent throughout this export and the template:

  • 🟩 Green → Mandatory fields

  • 🟨 Yellow → Optional fields

Appendix 1

Field

Mandatory

Comment

Example

overwrite

optional

If set to Yes, existing data is replaced. ⚠️ Use with caution -rollback may not be possible. Leave empty or set to No to keep existing data.

Yes

connection_type

mandatory

How the Site is associated with your organization. The allowed values are: SUPPLIER, CUSTOMER and OWN.

SUPPLIER

your_reference

mandatory

A textual identifier that uniquely identifies a Site connected to your organization.

C12345

site_details_name

mandatory

The human-readable name for the site, usually canonicalized.

Prewave GmbH

country_code

mandatory

Alpha-2 ISO Code of the address. See https://www.iso.org/obp/ui for details.

AT

locality

mandatory

Refers to the city/town portion of the address. In regions of the world where localities are not well defined or do not fit into this structure well, use closest locality instead.

Vienna

address_line

mandatory

Unstructured address lines describing the lower levels of an address. Usually this is a street name and house number.

Rothschildplatz 4, Austria Campus 4/3rd Floor

postal_code

recommended

Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address.

1020

industry_1

mandatory

The industry which is relevant for your Site. Multiple industries can be added separated by a semicolon (;). These values will be mapped to Prewave industries or commodities.

IT / Software

industry_2

optional

Additional field to industry_1. Values will be joined together.

industry_3

optional

Additional field to industry_1. Values will be joined together.

collection_name_1

optional

The collection in which you want to group your Site. Multiple collections can be added separated by a semicolon (;). These collections can be mapped to Prewave industries or commodities for scoring.

IT-Suppliers;Grouping-A;Austrian Suppliers

collection_name_2

optional

Additional field to collection_name_1. Values will be joined together.

Supplier of the Year

collection_name_3

optional

Additional field to collection_name_1. Values will be joined together.

impact

optional

Your estimated impact on the operation of the Site. The allowed values are: CRITICAL, HIGH, MID, LOW and NO. If empty, impact is CRITICAL for own Sites, MID for SUPPLIER and CUSTOMER and NONE for all others.

MID

spend_data

optional

The total value of the goods and/or services you purchased at that site in EUR per year.

100000

website

recommended

The authoritative website for this site, such as a business' homepage.

prewave.com

external_reference_id

optional

External unique site identifier number.

300533068

external_reference_type

optional

Required if external_reference_id is stated. Reference to the source of the unique site identifier.

DUNS

contact_1

optional

E-mail of the Site’s contact to complete self-assessments. Multiple contacts can be added separated by a semicolon (;).

contact_2

optional

Additional field to contact_1. Values will be joined together.

contact_3

optional

Additional field to contact_1. Values will be joined together.

prewave_id

optional

A positive number that uniquely identifies a Prewave Site. If set, site_details_name, country_code, locality and address_line can be skipped.

6640371

Historical Screening

optional

Request a screening for the during upload. Leave empty if not needed.

Yes


Did this answer your question?