# Supply Chain Integration

> Integrate procurement systems with supplier portals, delivery tracking, inventory management, and supply chain analytics for real-time visibility across the supply chain

- Skill: `construct-ai-primary/supply-chain-integration` (Agent Skill)
- Install (CLI): `npx skillmds@latest add construct-ai-primary/supply-chain-integration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/construct-ai-primary/supply-chain-integration/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: Construct-AI-primary (https://skillmd.com/u/construct-ai-primary)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/construct-ai-primary/supply-chain-integration

---


# Supply Chain Integration

## Overview

Integrate procurement systems with supplier portals, delivery tracking services, inventory management systems, and supply chain analytics to provide real-time visibility across the procurement lifecycle. Connects ERP/order management with external supplier systems and logistics providers.

**Announce at start:** "I'm using the supply-chain-integration skill to connect procurement systems with supplier and logistics integrations."

## When to Use This Skill

**Trigger Conditions:**
- Integrating supplier portal with internal procurement systems
- Connecting delivery tracking services (courier APIs, GPS tracking)
- Setting up inventory management integration (warehouse, site stores)
- Building supply chain analytics dashboards
- Implementing EDI/API integration with suppliers

**Prerequisites:**
- Supplier systems accessible via API, EDI, or portal integration
- Data mapping defined between internal and external systems
- Authentication and security configured for external connections

## Step-by-Step Procedure

### 1. Supplier Portal Integration

Connect internal procurement to supplier self-service portals:

| Integration | Purpose | Data Flow |
|-------------|---------|----------|
| RFQ Distribution | Send RFQs to multiple suppliers | Internal → Supplier portals |
| Quotation Submission | Collect supplier quotations | Supplier portals → Internal |
| Order Acknowledgment | Supplier confirms order (SO) | Internal → Supplier → Internal |
| Delivery Updates | Supplier provides shipping/dispatch | Supplier → Internal |
| Invoice Submission | Supplier submits electronic invoice | Supplier portals → Internal |

**Connection Pattern:**
```
Internal ERP/Procurement System
    ↓ (RFQ, PO)
Supplier Portal API / EDI
    ↓ (Acknowledgment, Shipment Notice, Invoice)
Supply Chain Integration Layer
    ↓ (Normalized data)
Internal Procurement System
```

### 2. Delivery Tracking Integration

Connect to delivery tracking services:

| Tracking Source | Data Provided | Integration Method |
|-----------------|---------------|-------------------|
| Courier APIs (DHL, FedEx, local) | Shipment status, tracking events, ETA | REST API |
| GPS Vehicle Tracking | Real-time vehicle location, geofencing | GPS API / IoT service |
| Supplier Shipping Notices | Dispatch confirmation, BOL, estimated arrival | EDI / Portal API |
| Site Receiving Confirmation | GRN recording, quantity verification | Internal ERP API |

**Tracking Workflow:**
```
PO Issued → SO Acknowledgment → Supplier Dispatch Notice
    → Courier Tracking Active → GPS Tracking En Route
    → Geofence Alert (Approaching Site) → Site Receiving
    → GRN Created → Order Status Updated
```

### 3. Inventory Management Integration

Connect procurement to inventory and warehouse systems:

| Integration | Purpose | Trigger |
|-------------|---------|---------|
| Stock Level Sync | Available quantity in warehouse/stores | On GRN, on issue, on adjustment |
| Reorder Point Alerts | Trigger requisition when stock below threshold | Stock level falls below reorder point |
| Material Issue Recording | Track material issued to work orders | WO material consumption |
| Stock Transfer | Track material between sites/stores | Inter-site transfer |

### 4. EDI/API Integration Patterns

Implement standardized data exchange:

**EDI Documents:**
| Document | Purpose | Direction |
|----------|---------|-----------|
| X12 850 / EDIFACT ORDERS | Purchase Order | Buyer → Supplier |
| X12 855 / EDIFACT ORDRSP | Order Acknowledgment | Supplier → Buyer |
| X12 856 / EDIFACT DESADV | Advance Ship Notice | Supplier → Buyer |
| X12 810 / EDIFACT INVOIC | Invoice | Supplier → Buyer |

**RESTful API Pattern:**
```json
// POST /api/orders — Create order
// GET /api/orders/{id} — Get order status
// PUT /api/orders/{id}/acknowledge — Acknowledge order
// POST /api/shipments — Record shipment
// GET /api/shipments/{id}/tracking — Get tracking status
// POST /api/invoices — Submit invoice
```

### 5. Supply Chain Analytics

Connect all data sources for supply chain visibility:

| Analytics Area | Data Sources | Insights |
|----------------|--------------|----------|
| **Supplier Performance** | Delivery tracking, GRN, quality records | On-time rate, quality rate, reliability score |
| **Inventory Health** | Stock levels, reorder events, consumption | Stock-out risk, carrying cost, turnover rate |
| **Delivery Reliability** | Tracking data vs. expected dates, delay records | Route analysis, carrier performance, delay causes |
| **Cost Visibility** | Order values, freight costs, currency changes | Total landed cost, cost variance, savings tracking |

## Success Criteria

- [ ] Supplier portal integration established and tested
- [ ] Delivery tracking active for all shipped orders
- [ ] Inventory levels synchronized between systems
- [ ] EDI/API data exchange validated with trading partners
- [ ] Supply chain analytics dashboard populated with live data
- [ ] Alert system configured for delivery delays, stock-outs, anomalies

## Common Pitfalls

1. **Assuming API Stability** — External supplier APIs change. Always implement version detection and change notification handling.
2. **Ignoring Time Zones** — Delivery tracking spans multiple time zones. Always store timestamps in UTC and convert only for display.
3. **No Fallback for Offline** — Courier APIs can be down. Store tracking events locally and sync when service recovers.
4. **Missing Data Mapping** — "Each" ≠ "Carton" ≠ "Pallet". Always map UOM between systems to prevent quantity errors.
5. **Overloading Supplier Systems** — Frequent polling can slow supplier systems. Use webhooks or event-driven patterns where possible.

## Cross-References

### Related Skills
- `procurement-order-management` — Order data flows to supplier integration
- `procurement-data-extraction` — Processes EDI/API messages into structured data
- `mobile-procurement` — Delivery tracking on mobile devices
- `procurement-analytics` — Consumes supply chain data for dashboards

### Related Disciplines
- `01700 Logistics` — Delivery coordination, site receiving, material handling
- `01200 Finance` — Invoice processing, payment reconciliation

## Example Usage

**Scenario:** Integrate SteelWorks Ltd supplier portal for real-time order tracking

1. **Connect:** Supplier API endpoint configured with authentication
2. **Send:** PO transmitted via EDI 850 → Supplier receives order
3. **Receive:** ORDRSP acknowledgment with confirmed quantities and dates
4. **Track:** DESADV advance ship notice triggers tracking workflow
5. **Monitor:** Real-time GPS tracking from dispatch to site arrival
6. **Record:** GRN created on site receiving, order closed
7. **Analyze:** Delivery on-time (2/14 weeks), quality pass (100%), supplier score updated

## Performance Metrics

**Target Performance:**
- Integration uptime: >99% for supplier portal connections
- Data synchronization latency: <5 minutes for order status updates
- Delivery tracking accuracy: >95% of shipments tracked to delivery
- Alert response time: <1 minute for critical delivery alerts
- EDI processing rate: >98% successful document processing