Design a commodity pass-through policy with clauses and playbooks.
- User
Design a commodity pass-through policy with clauses and playbooks.
- Assistant
Commodity Pass-Through Policy
Designed by Sherlock, Trailblazer Labs AI
Executive Summary
This Commodity Pass-Through Policy (the "Policy") enables suppliers or service providers to transparently pass commodity price fluctuations (e.g., energy, metals, agricultural products) to customers, mitigating risk from market volatility. It ensures cost neutrality for the supplier while maintaining predictability for customers through indexed pricing, caps/floors, and clear governance.
Key Objectives:
- Protect supplier margins from commodity price swings.
- Provide customers with market-linked pricing transparency.
- Minimize disputes via automated adjustments and audit trails.
- Applicable to long-term contracts in energy, manufacturing, logistics, or food sectors.
Scope: Covers pass-through of specified commodities (e.g., crude oil, natural gas, steel, wheat). Excludes fixed-price contracts unless amended.
Core Clauses
These clauses are designed for insertion into master supply agreements (MSAs), service contracts, or purchase orders. Customize indices, thresholds, and parties as needed.
1. Definitions
1.1 "Commodity" means [specify, e.g., West Texas Intermediate (WTI) crude oil, Henry Hub natural gas, LME copper, CBOT wheat], as priced per the Index. 1.2 "Index" means the published price source [e.g., Platts, Argus, Bloomberg, CME], averaged over [e.g., monthly closing prices]. 1.3 "Base Price" means the Commodity price at contract commencement [date], fixed at [USD X per unit]. 1.4 "Pass-Through Adjustment" means the dollar-per-unit increase/decrease in charges equal to [X]% of the variance between Base Price and current Index price, subject to Caps/Floors.2. Pass-Through Mechanism
2.1 Pricing Formula: Customer charges = Fixed Fee + (Volume × Unit Rate) + Pass-Through Adjustment. Pass-Through Adjustment = Volume × [Pass-Through Rate, e.g., 100%] × (Current Index Price - Base Price). 2.2 Adjustment Frequency: Monthly, effective on the 1st of the following month, based on prior month's Index average. 2.3 Caps and Floors: Adjustments capped at ±[X]%, e.g., +20%/-10% of Base Price annually, to limit exposure.3. Notification and Billing
3.1 Supplier shall notify Customer of adjustments via [email/portal] by the [e.g., 10th] of the adjustment month, including Index data, calculations, and supporting evidence. 3.2 Invoices shall itemize Pass-Through Adjustments. Customer shall pay undisputed amounts within [e.g., 30 days]. 3.3 True-Up: Annual reconciliation within [90 days] of fiscal year-end; over/underpayments settled net.4. Audit and Verification
4.1 Customer may audit Supplier's calculations [quarterly/annually] upon [30 days'] notice, at Customer's expense unless discrepancy >[2]%. 4.2 Supplier shall maintain records for [5 years], including Index data, hedging documentation (if applicable), and consumption volumes.5. Dispute Resolution and Limitations
5.1 Disputes resolved via [mediation/arbitration] under [e.g., AAA rules] in [jurisdiction]. 5.2 No Pass-Through for Supplier's hedging gains/losses or internal inefficiencies. 5.3 Force Majeure: Adjustments suspended during events per Clause [X], but resume post-event based on prevailing Index.6. Termination and Amendments
6.1 Terminable on [90 days'] notice; final true-up required. 6.2 Amendments require mutual written consent.
Operational Playbooks
Playbooks provide step-by-step execution guides, scenario responses, and tools for teams (e.g., procurement, finance, legal). Implement via dashboards (e.g., Excel, ERP integrations like SAP).
Playbook 1: Monthly Adjustment Calculation
Steps:
- Gather Data: Pull Index prices (e.g., via API from Bloomberg).
- Calculate Variance: (Avg. Index - Base Price) × Pass-Through Rate.
- Apply Limits: Clamp to Caps/Floors.
- Forecast Impact: Volume × Adjustment = Total Delta.
- Notify & Invoice: Email template + automated billing.
- Document: Archive in shared drive/ERP.
Tool: Excel Template (link placeholder: [Adjustment_Calculator.xlsx]).
Step Input Formula Output Example 1 Index Avg: $80/bbl - Base: $70/bbl 2 Variance: $10 ×100% $10/bbl 3 Cap Check: +20% ($14) Min(14) $10/bbl 4 Volume: 10k bbls ×10k +$100k Playbook 2: Scenario Responses
Decision Tree:
Price ↑ (>Base + Cap)? ├── YES → Apply Cap; Notify "Max Adjustment Hit" → Escalate to Customer Rep for Negotiation ├── NO → Full Pass-Through → Standard Notification Price ↓ (<Base - Floor)? ├── YES → Apply Floor; Credit Customer → Issue True-Up Credit ├── NO → Full Pass-Through (potential rebate) Dispute Raised? ├── Within 10 Days → Provide Audit Trail → Mediate ├── >10 Days → Enforce Payment Terms → Escalate to LegalCommon Scenarios:
- Spike (e.g., Oil +30%): Cap activates; hedge via futures if pre-approved.
- Crash (e.g., Gas -40%): Floor protects supplier; customer gets max rebate.
- Stable: No adjustment; monitor for trends.
Playbook 3: Monitoring & Reporting
Dashboard Metrics (Weekly Review):
- Index Trend (YoY %).
- Cumulative Adjustments (Run-Rate Impact).
- Hedge Effectiveness (if using derivatives).
- Dispute Log.
Quarterly Tasks:
- Review contract performance vs. objectives.
- Benchmark indices (switch if unreliable).
- Train teams on updates.
Risk Mitigation:
- Integrate with ERP for auto-alerts (>5% variance).
- Annual legal review for index changes (e.g., Platts methodology shifts).
Playbook 4: Onboarding/Implementation
- Contract Signing: Embed clauses; set up Index feeds.
- Baseline: Lock Base Price; baseline volumes.
- Tech Setup: API integrations + dashboards (e.g., Power BI).
- Kickoff Meeting: Train stakeholders (30-min session).
- Pilot Month: Test adjustments; refine.
Implementation Recommendations
- Tech Stack: Bloomberg Terminal/API, ERP (Oracle/SAP), Contract Lifecycle Management (e.g., Ironclad).
- Legal Review: Consult counsel for jurisdiction-specific tweaks (e.g., UCC in US).
- Customization: Scale for multi-commodity (add matrix in Clause 1.1).
- Metrics for Success: <5% disputes, 100% on-time adjustments, margin stability ±2%.
This Policy is deductive in design—rooted in observable market data, airtight clauses, and executable playbooks. Questions or refinements, Watson?
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.