Compliance requirements define what an Order has to satisfy to be considered compliant. There are two types, and both are optional; you can set either, both or neither. They drive the Order's status and the paperwork that travels with it.
Requirement type | What it does |
Traceability requirement | Checks that every product in the Order can be traced back to a chosen type of origin location. |
Evidence requirements | Require specific documents or certificates (from Evidence Templates) to be provided for the Order. |
Where to add or edit requirements
You can add or change compliance requirements in two places:
While creating an Order, click Create order and add requirements to open the Add order compliance requirements step. See How do I create an Order?
For an existing Order, open it, go to the Compliance tab and click Edit on the Order compliance requirements panel. The same form opens so you can add, change or remove requirements at any time.
Traceability requirement (trace back to a location)
Why add it: a traceability requirement makes OriginsNext automatically check that every product in the Order can be traced back to a chosen type of origin location. The check follows each product's full journey upstream, including any bulk transformations along the way. Add it when the Order needs to prove where its products come from, for example to satisfy due-diligence or market-access rules that require proof of origin, such as showing goods originate from compliant, deforestation-free land. It also surfaces, before you ship, any product that cannot yet be traced to the required origin, so you can close the gap.
How to add it: under Traceability requirement, choose the origin location type in Trace back to. The list covers the location types in your registry, for example Farm, Feedlot, Fishery, Hatchery, Mine, Warehouse, Distribution Centre, Silo, Transportation Hub or Port, so pick the origin type the Order needs to reach (for example, the Farm or Fishery where the goods originated). The Order then checks each product against it.
Evidence requirements
Why add them: evidence requirements define the certificates, permits, declarations or other documents the Order must have to be compliant (for example, an EUDR due-diligence statement, a health certificate, or an export permit). Adding them turns the Order's compliance into a measurable checklist: the Order's status reflects whether the required evidence is complete, and the evidence can be generated or attached and then shared with the buyer. Add the requirements that the destination market or your customer needs, so the Order ships with the right paperwork and an auditable record.
How to add them: under Evidence requirements, search the list of available Evidence Templates and tick Add for each one the Order needs. Each template shows its Name and its Issuer (the organisation that defined it). Tick Counterparty can generate if you want the other party to produce that evidence rather than you. This is useful when the document is theirs to provide, such as a supplier's own certificate. You can add more than one, then click Save. To remove a requirement later, reopen Edit and untick it.
What happens after you add requirements
Each evidence requirement appears on the Order's Compliance tab with its status (for example, Action required) and a Generate button to produce the evidence. Some templates break down into supporting requirements (individual checks the Order must pass) shown as a count such as 0/2 supporting requirements complete. For example, an EUDR template may require both “Supplier Location has Appropriate EUDR Certificates” and “Supplier Location has Traceable GeoData”. Expand Show to see each one; a check stays Incomplete until your locations or products satisfy it (for instance, while “no locations match evidence requirements”). These requirements also drive the Order's overall status. See What do the Order statuses mean?
Note: the traceability requirement and the evidence requirements are independent. You can add, change or remove either of them on its own from the Compliance tab using Edit.