Claude Skills Guide

Logistics and supply chain operations involve complex orchestration of vendors, warehouses, transportation, and inventory systems. Developers building logistics software face unique challenges: processing shipping manifests, managing real-time inventory updates, optimizing routes, and generating compliance documentation. Claude skills provide programmatic capabilities that transform these manual workflows into automated pipelines, reducing errors and freeing teams to focus on strategic improvements.

This guide covers practical implementations of Claude skills for logistics supply chain software, with code examples you can adapt immediately.

Inventory Management with xlsx and csv Skills

Inventory tracking forms the backbone of any logistics system. The xlsx skill enables automated inventory updates across spreadsheets, maintaining SKU databases, stock levels, and reorder points without manual intervention.

# Automated inventory reorder logic
def check_reorder_need(current_stock, reorder_point, order_quantity):
    """Determine if reorder is needed"""
    if current_stock <= reorder_point:
        return {
            "reorder": True,
            "quantity": order_quantity,
            "priority": "high" if current_stock <= reorder_point * 0.5 else "standard"
        }
    return {"reorder": False}

# Claude skill execution:
# /xlsx Update inventory-tracker.xlsx, column E (Reorder_Status)
# based on values in column C (Current_Stock) vs column D (Reorder_Point)

For bulk inventory processing, combine the xlsx skill with batch operations to process thousands of SKUs simultaneously. Many logistics teams maintain master inventory spreadsheets with multiple tabs—one for raw materials, another for WIP (work-in-progress), and a third for finished goods. The xlsx skill navigates between tabs and applies consistent logic across all three.

To run a daily reconciliation, invoke the xlsx skill with a clear prompt:

/xlsx Compare warehouse-inventory.xlsx (column: SKU, Qty_On_Hand)
with erp-export.csv (column: SKU, System_Qty)
flag discrepancies where difference > 5 units
generate report in /reports/inventory-variance-{date}.xlsx

Shipping Documentation with pdf Skill

Generating Bills of Lading (BOL), packing lists, and customs documentation consumes significant staff time. The pdf skill automates creation and population of these forms from shipment data.

# Shipment data structure
shipment = {
    "bol_number": "BOL-2026-00142",
    "shipper": {"name": "Acme Logistics", "address": "123 Warehouse Ave"},
    "consignee": {"name": "Beta Retail", "address": "456 Distribution Blvd"},
    "items": [
        {"description": "Industrial Bearings", "quantity": 500, "weight_kg": 1250},
        {"description": "Steel Fasteners", "quantity": 2000, "weight_kg": 800}
    ],
    "carrier": "FastFreight Express",
    "terms": "FOB Destination"
}

# Claude skill prompt:
# /pdf Create Bill of Lading using template bol-template.pdf
# populate all fields from shipment data above
# save as /shipments/outbound/BOL-2026-00142.pdf

The pdf skill also handles reverse workflows—extracting data from carrier-provided PDFs into your internal systems. This proves essential when processing hundreds of shipping confirmations or customs clearance documents daily.

# Extract tracking data from carrier PDFs
skill: carrier-tracking-extraction
actions:
  - /pdf extract table from /incoming/carrier-pdfs/*.pdf
  - parse tracking_number, delivery_date, signature fields
  - append to /data/tracking-updates.csv
  - trigger webhook to update order status in ERP

Route Optimization with Claude Code

Transportation routing combines multiple variables: delivery windows, vehicle capacity, fuel costs, traffic patterns, and driver schedules. While Claude skills don’t perform the mathematical optimization directly, they orchestrate the data pipeline and integrate with routing engines.

# Route optimization data preparation
deliveries = [
    {"id": "DEL-001", "address": "100 Main St, Chicago", "time_window": "09:00-12:00", "weight": 450},
    {"id": "DEL-002", "address": "200 Oak Ave, Chicago", "time_window": "10:00-14:00", "weight": 320},
    {"id": "DEL-003", "address": "300 Elm St, Naperville", "time_window": "13:00-17:00", "weight": 680},
]

# Claude skill orchestration:
# 1. /xlsx Prepare route-input.csv with delivery addresses and constraints
# 2. Call external routing API (OR-Tools, Routific, etc.)
# 3. /xlsx Format optimized routes into driver-app.xlsx
# 4. Generate PDF route sheets for each driver

Warehouse Operations and Picking Automation

Warehouse management systems (WMS) require constant synchronization between physical movements and digital records. Claude skills automate the generation of pick lists, bin transfers, and cycle count reports.

# Cycle counting workflow
skill: cycle-count-automation
description: Generate cycle count sheets, process results, flag variances
steps:
  - query current inventory from database
  - /xlsx Generate cycle-count-{date}.xlsx with:
    - bin_location, sku, system_qty, counted_qty columns
    - random 5% sample of SKUs
  - After counting:
    - /xlsx Compare counted vs system quantities
    - Flag items with variance > 2%
    - Create adjustment requests for flagged items
    - Update inventory records in ERP

Integration with Transportation Management Systems

Modern logistics stacks connect multiple systems: ERPs, WMS, TMS (Transportation Management Systems), carrier portals, and customer-facing tracking. Claude skills serve as the integration layer, translating between formats and triggering downstream actions.

# Webhook handler for carrier status updates
def process_carrier_update(payload):
    """Process incoming carrier status webhook"""
    # Claude skill prompt:
    # /json Parse webhook payload from carrier API
    # /xlsx Update shipment-tracking.xlsx with:
    #   - tracking_number: from payload
    #   - status: map carrier status to internal status
    #   - estimated_delivery: parse from payload
    #   - last_update: current_timestamp
    # /slack Send notification to #logistics-ops if status == "exception"

Real-Time Alerts and Exception Handling

Supply chain disruptions require immediate attention. Claude skills monitor systems and generate alerts when exceptions occur.

# Exception monitoring skill
skill: supply-chain-monitor
schedule: every 15 minutes
actions:
  - query delayed_shipments where status == "in_transit" 
    and estimated_delivery < now() + 24h
  - query inventory_levels where stock < reorder_point
  - /xlsx Generate exception-report-{date}.xlsx
  - If critical exceptions > 5:
    - /slack Post to #supply-chain-alerts
    - Email to logistics-manager@company.com

Best Practices for Logistics Skill Development

When building Claude skills for logistics applications, consider these patterns:

Idempotency matters. Logistics operations process the same data multiple times. Design skills that produce consistent results regardless of how many times they run with the same inputs.

Audit trails are essential. Every automated action should log what changed, when, and why. Store these logs in structured formats (JSON, CSV) for compliance and debugging.

Handle partial failures gracefully. A shipment with 50 items where one fails validation shouldn’t block the other 49. Design skills to process valid items and report failures separately.

Timezone awareness. Logistics operates across regions. Store timestamps in UTC and display in relevant timezones using the skill’s formatting capabilities.

# Timestamp handling best practice
from datetime import datetime, timezone

def log_shipment_event(event_type, shipment_id, data):
    """Log with explicit UTC timestamps"""
    log_entry = {
        "timestamp": datetime.now(timezone.utc).isoformat(),
        "event_type": event_type,
        "shipment_id": shipment_id,
        "data": data
    }
    # Write to audit log
    return log_entry

Claude skills transform logistics operations from reactive firefighting into proactive management. By automating document generation, inventory reconciliation, and exception monitoring, your team focuses on optimization rather than data entry. Start with one workflow—shipment documentation or inventory counting—and expand as you prove the value.

Built by theluckystrike — More at zovo.one