Team Price Group Pricings (⚠️ EOL)

⚠️
Soon to be deprecated
This table is being deprecated and will be removed. Please migrate to price_group_pricings as soon as possible.
Deprecation timeline:

Week 4, 2027 (week of 25 January): this model gets a DEPRECATED__ prefix. Queries using the current name will stop working — repoint to the new name to keep using it.

Week 8, 2027 (week of 22 February): this view is removed for good.

The replacement price_group_pricings table includes pricings for both team-owned and operator-owned price groups. In the new table, team_price_group_id is renamed to price_group_id. To get the same results as this table, filter on owner_type = 'Team'.

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: 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

Inclusion Criteria

the team_price_group_id must exist in the operator's team_price_groups.id

Data flow

Upstream tables	Downstream tables
`team_price_groups`	None

Alignment

Monta API

Aligns with the pricing objects in the Monta API get/price-groups endpoint
the masterPrice object requires that the master = true. There should be exactly 1 master price record per team_price_group_id
the fees object - where master = false and tariff_id is null. There can be 0 to many fee records per team_price_group_id
the tariffs object - where master = false and tariff_id is not null. There can be 0 to many tariff records per team_price_group_id