specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: CargoSmart providerId: cargosmart created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: false tags: - FinOps - FOCUS - Logistics - Ocean Freight - Supply Chain description: 'FOCUS-aligned FinOps for CargoSmart/IQAX: enterprise license + per-tracked-container fees on the IQAX shipment-management platform; billing is contract-based.' notes: CargoSmart/IQAX does not publish public API or container-volume pricing. FinOps mapping is provisional pending enterprise-contract reconciliation. sources: - https://www.cargosmart.com/ - https://www.iqax.com/ alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: CargoSmart Limited (IQAX) serviceCategory: Shipment Management Platform billingModel: pricingCategory: Subscription + Per-Container billingFrequency: Annual billingCurrency: USD chargeCategories: - Purchase - Usage - Adjustment focusColumns: ServiceName: CargoSmart / IQAX Platform ServiceCategory: Shipment Management Platform ProviderName: CargoSmart PublisherName: CargoSmart Limited (IQAX) InvoiceIssuerName: CargoSmart Limited (IQAX) BillingCurrency: USD meters: - name: enterprise_license unit: year aggregation: sum dimensions: - module - name: tracked_containers unit: container aggregation: sum dimensions: - carrier - trade_lane - name: bookings_created unit: booking aggregation: sum dimensions: - carrier - name: documents_processed unit: document aggregation: sum dimensions: - document_type - name: named_users unit: seat-month aggregation: max principles: - name: Visibility description: Use the IQAX platform reporting and audit logs to attribute container-volume cost to trade lanes, carriers, and business units. - name: Allocation description: Allocate by carrier, trade lane, and originating business unit; multi-BU customers should configure distinct organization tenants. - name: Optimization description: Right-size tracked-container quotas to actual fleet activity; consolidate carrier integrations via GSBN where possible. - name: Accountability description: Logistics-operations / digital-supply-chain lead owns the relationship; quarterly volume reviews with CargoSmart/IQAX are typical. maintainers: - FN: Kin Lane email: kin@apievangelist.com