CardanoTrace vs INSAP TraceChain

CardanoTrace is an open-source API and SDK for building supply-chain traceability solutions on the Cardano blockchain. Plutus smart contracts record product lifecycle events on-chain, covering events, lots, assets and policies. Its stated scope is end to end, with examples ranging from farm-to-fork supply chains to pharmaceutical logistics. The system uses modular, event-driven components designed for GS1- and ISO-aligned data, portability, and connection with existing systems and standards. Developers can use typed SDKs, including TypeScript, clean APIs and end-to-end examples. The repository describes a FastAPI REST API with documented endpoints, a QR service linking codes to blockchain transaction IDs, and a Python SDK. Local deployments list PostgreSQL for production and SQLite for development and testing, with Swagger and ReDoc documentation. CardanoTrace is MIT-licensed; API development is in progress, while the QR service and Python SDK are upcoming.

INSAP TraceChain provides serialization and supply-chain tracking from production to point of sale, with recall readiness and authenticity checks. It assigns batch-, lot-, or unit-level identities at production and links movement events into product genealogy across plants, depots, distributors, and shelves. The system can read production and movement events from SAP PP/MM and depot systems; recall actions return as governed transactions. The maker says genealogy can identify affected units and destinations in minutes, with expiry visibility. Field teams and consumers can scan against the genuine record, while duplicate and out-of-territory scans are flagged. Coding accommodates GS1 and customer-specific formats. Events are append-only; corrections become new attributed events rather than edits. Public scans reveal only details the customer chooses to publish, typically authenticity, batch, and expiry. Traceability extends only to the last point that scans. Existing printing and scanning points are usually used, though some levels of serialization may require new hardware. Data is stored in a region chosen by the customer. Pricing is on request and based on serialized volume and the lines and nodes in scope, determined after serialization design.