🧭✨Future Charge Pricing Breakdowns (NEW)
✨ NEW TABLE - November 2025
🛠️ Partner API Alignment Migration
🧭 This table represents the post-migration state for
charge_pricing_breakdows.1️⃣ Migrate to this table by April 2026
2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix
Provides detailed pricing breakdowns for partner charges. This model joins partner-specific charge data with standard pricing breakdown information, enabling consistent price analysis across different partners.
SQL: FUTURE__charge_pricing_breakdowns
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | Primary key |
| Other IDs | ||
| charge_id | INTEGER | References the associated charge record from the partner charges table |
| currency_id | INTEGER | Identifier for the currency used in the pricing calculations |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the pricing breakdown record was created |
| updated_at | TIMESTAMP_NTZ | Timestamp when the pricing breakdown record was last modified |
| Attributes | ||
| type | VARCHAR | Categorizes the type of pricing breakdown (e.g., standard, promotional, special rate) |
| precision | INTEGER | Indicates the decimal precision used for price calculations |
| total_price | NUMBER | Total calculated price including all components and adjustments |
| total_master_price | NUMBER | Primary price component before additional fees or adjustments |
| total_secondary_price | NUMBER | Secondary or supplementary price component, if applicable |
| total_fees | NUMBER | Sum of all additional fees applied to the charge |
| total_adjustments | NUMBER | Net value of all price adjustments, including discounts or surcharges |
Changes from Last Version
- Renamed column: charge_pricing_breakdown_id → id to standardize primary key naming.
- No other changes to schema or data types; existing fields remain unchanged.
- This table is downstream of
FUTURE__chargeswhich is downstream of models with relaxed inclusion criteria.
Data inclusion criteria
- This table works with
FUTURE__chargestable, requiring thatcharge_idis among the partner'sFUTURE__charges.idrecords.
Data flow
| Upstream tables | Upstream tables |
|---|---|
FUTURE__charges | FUTURE__charge_pricing_breakdown_specifications |
Alignment
The charge_pricing_breakdowns table
charge_pricing_breakdowns table- this table (just like the one it replaces) depends on
chargeswhich further depends oncharge_pointsandteams. FUTURE__charge_points,FUTURE__teamsandFUTURE__chargesall have relaxed inclusion criteria.- one aligns this table by alinigning
FUTURE__chargesfirst, and then recreating inclusion criteria for this table.
Updated about 12 hours ago
