ISPO, ISCC, RSPO or GDST: four schemes, four different questions

An exporter in Jambi receives a questionnaire from a European buyer. Question fourteen asks: “Please confirm your traceability system meets scheme requirements.” Which scheme? Nobody says. The exporter sends a certificate they already have, the buyer’s compliance team marks it as non-responsive, and three weeks disappear.

The mistake is treating “traceability” as one requirement. It is at least four, and each one asks a different question about the same supply chain.

The four questions

ISPO asks whether Indonesian palm production meets national legality and sustainability requirements. It is the domestic baseline. If your buyer is Indonesian and regulated, this is the floor, not the ceiling.

ISCC asks whether a physical quantity of material can be tracked through custody with defined rules — mass balance, physical segregation, or book-and-claim. It is fundamentally a chain-of-custody accounting question: how many tonnes entered, how many left, and where did the difference go.

RSPO asks whether palm production met specific sustainability principles and criteria, verified by an accredited auditor. It is a production standard with its own supply-chain models, and it does not by itself answer the accounting question above.

GDST asks something different again: whether the data your system produces can be exchanged with another system in a common format. It is an interoperability standard, not a sustainability judgement. Indonesia’s national system being recognised as GDST-compliant matters here — it means data can move between parties, not that the fish were caught sustainably.

Why this matters in practice

Two consequences follow, and both cost money when ignored:

1. A certificate is not a record. Holding ISPO or RSPO certification does not give you a queryable trail from a delivered lot back to a plot. Auditors increasingly ask for the trail, because the certificate describes a management system, not a specific shipment.
2. Different schemes need the same underlying data. Identity, plot boundary, handover weight and lot reference. If you capture those four properly once, you can produce evidence for all four schemes without re-collecting anything. If you capture them per-scheme, you do the fieldwork twice and the numbers will disagree.

The practical sequence

• Ask the buyer which scheme, and request the exact clause they are assessing against. “Scheme requirements” is not an answer.
• Map what the scheme actually needs to a data field. If a scheme needs tonnage reconciliation, then weight at handover is mandatory — not optional.
• Capture once, in a structure, then export per scheme.
• Keep the source document, not a summary of it. Auditors accept primary evidence.

Where exporters get caught

The recurring failure is not a missing certificate. It is that the certified entity and the shipped lot cannot be connected. A mill holds ISCC certification; the smallholder cooperative that supplied the fruit has no linkable lot reference; the paint therefore cannot be traced past the mill gate.

Fixing that is unglamorous work: assign stable farmer IDs, map boundaries, record weight at every handover. It is also the only version of this work that survives more than one audit.

---

This is a practical overview, not compliance advice. Scheme requirements change — confirm the current version with the scheme owner before relying on any clause.