Skip to content
English
  • There are no suggestions because the search field is empty.

Must-have vs Nice-to-have Requirements

There are two types of requirement cards: Must-have and Nice-to-have.

Must-have requirements

Must-have requirement cards include documents that are mandatory for your suppliers.

Key characteristics:

  • You can include multiple document types within one requirement card.

  • The relationship between document types inside one card is OR.

    (Example: A supplier complies if they provide Rainforest Alliance OR Fairtrade OR SIZA.)

If you need suppliers to provide multiple different documents, you must create multiple requirement cards.

The relationship between separate requirement cards is therefore AND.

Automatic requests are generated for Must-have requirements when documents are:

  • Missing
  • Expired
  • Expiring soon

Nice-to-have requirements

Nice-to-have requirement cards include documents that are desirable, but not mandatory.

Important to know:

  • Nice-to-have requirements do not trigger automatic requests on their own.
  • They are included in outgoing requests only when a Must-have requirement already triggers a request.
  • You can include multiple document types in one Nice-to-have card.

This means suppliers are informed about these preferred documents, but they are not chased automatically for them.

What happens once a Nice-to-have document is uploaded?

If a supplier provides a Nice-to-have document and it is accepted:

  • It becomes an active requirement entry.
  • Once that document expires, the system will treat it like a normal requirement.
  • Automatic reminders will then be sent when it expires.

In short:

  • Must-have = Mandatory → triggers automatic requests.
  • Nice-to-have = Optional → only included when another request is already triggered.