Team Price Group Pricings
Table name: FUTURE__team_price_group_pricings
🛠️ Partner API Alignment Migration
✅ This table is new as of December 2025 and will not be impacted
1️⃣ Migrate to this table by April 2026
2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix
Contains pricing configurations and rules for team price groups, defining various charging tariffs, fees, and pricing structures applied to specific teams. This model filters pricing data to include only those associated with partner-specific team price groups, enabling partner-customized pricing management.
SQL: FUTURE__team_price_group_pricings
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | Primary key |
| Other IDs | ||
| team_price_group_id | INTEGER | Foreign key referencing the team price group this pricing configuration belongs to |
| team_id | INTEGER | Foreign key referencing the team associated with this pricing configuration |
| tariff_id | INTEGER | Foreign key referencing the tariff structure associated with this pricing |
| tag_id | INTEGER | Foreign key referencing tags used for categorizing or filtering this pricing configuration |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the pricing configuration was initially created |
| updated_at | TIMESTAMP_NTZ | Timestamp when the pricing configuration was last modified |
| deleted_at | TIMESTAMP_NTZ | Timestamp when the pricing configuration was soft deleted, null if still active |
| from_timestamp | TIMESTAMP_NTZ | Start timestamp when this pricing configuration becomes effective |
| to_timestamp | TIMESTAMP_NTZ | End timestamp when this pricing configuration expires, null for indefinite duration |
| Attributes | ||
| type | VARCHAR | Type of pricing configuration (tariff, fee, fixed_kwh, fixed_min, spot) |
| description | VARCHAR | Human-readable description explaining the purpose and details of this pricing rule |
| amount | NUMBER | Base monetary amount for this pricing configuration, in the system's default currency |
| vat | NUMBER | Value-added tax rate applied to this pricing configuration, expressed as a decimal |
| percentage | NUMBER | Percentage-based pricing component, used for percentage-based fees or discounts |
| start_min_after_charging | INTEGER | Number of minutes after charging begins when this pricing rule takes effect |
| start_min_after_fully_charged | INTEGER | Number of minutes after vehicle reaches full charge when this pricing rule activates |
| end_at_fully_charged | BOOLEAN | Indicates whether this pricing rule automatically ends when the vehicle is fully charged |
| amount_min | NUMBER | Minimum monetary amount that can be charged under this pricing configuration |
| amount_max | NUMBER | Maximum monetary amount that can be charged under this pricing configuration |
| interval | VARCHAR | Time interval for recurring pricing applications, such as hourly or daily billing cycles |
| master | BOOLEAN | Indicates whether this is the master pricing configuration for the group |
Changes from Last Version
Summary
- New table
Inclusion Criteria
- the
team_price_group_idmust exist in the operator'sFUTURE__team_price_groups.id
Data flow
| Upstream tables | Downstream tables |
|---|---|
FUTURE__team_price_groups | None |
Alignment
Partner API
- Aligns with the pricing objects in the Partner API get/price-groups endpoint
- the
masterPriceobject requires that themaster = true. There should be exactly 1 master price record perteam_price_group_id - the
feesobject -where master = false and tariff_id is null. There can be 0 to many fee records perteam_price_group_id - the
tariffsobject -where master = false and tariff_id is not null. There can be 0 to many tariff records perteam_price_group_id
Updated about 22 hours ago
