Phase 2: Design Integration Architecture (Weeks 5-8)

Key Design Decisions:

What Goes on Blockchain?

• Purchase order commitments (key terms only)
• Critical status changes (shipped, delivered, verified)
• Authentication events (certification validated)
• Payment triggers (conditions met, funds released)
• Dispute-prone data points (delivery times, quantities)

What Stays in EDI?

• Routine confirmations
• Detailed specifications
• High-frequency, low-value transactions
• Internal communications

Integration Methods:

Option A: API Integration (Most Common)

• ERP calls blockchain API to write/query events
• Clean separation, easy to test

Option B: Middleware Layer

• Monitors EDI transactions
• Automatically records designated events on blockchain
• No ERP modifications needed

Option C: Blockchain-Enabled EDI Gateway

• Processes EDI documents normally
• Creates blockchain records automatically
• Transparent to trading partners

Most organizations start with API integration for proof of concept, then evaluate middleware for production scale.