DAISORO

T2.3 / Portfolio Architecture

Device/Plan Bundle Architecture

Structures device-plan bundle mechanics, dependencies, public conditions, and versioned changes.

Plannedsecondary priority
Industry

Telecom

Family

Portfolio Architecture

Delivery

Direct file delivery / API access

Schema preview

Device/Plan Architecture

sample structure
01Device family and eligible plan
02Tenure options and repayment structure
03Subsidy, lock-in, and upgrade pattern
04Bundle dependency and included benefits
05Channel availability and offer evidence
06First seen, last seen, and change type

What it captures

  • Device family and eligible plan
  • Tenure options and repayment structure
  • Subsidy, lock-in, and upgrade pattern
  • Bundle dependency and included benefits
  • Channel availability and offer evidence
  • First seen, last seen, and change type

Decision workflows supported

  • Bundle architecture comparison
  • Device subsidy strategy inputs
  • Channel proposition review

Buyer roles

  • Pricing strategy leaders
  • CVM and retention teams
  • Product portfolio leaders
  • Data and AI teams
  • Regulatory and market intelligence teams

Delivery models

  • Direct file delivery
  • API access
  • Cloud push

Decision workflows supported

Pricing strategy

Monitor offer changes, bundle mechanics, channel variance, and competitor moves.

CVM / retention

Feed churn, retention, and portfolio-risk workflows with structured market signals.

Data & AI ingestion

Use stable IDs, schema fields, evidence references, and version states in AI pipelines.

Regulatory transparency

Review public terms, fair-use labels, evidence, and change history without overclaiming legal status.

Sample structure

Non-downloadable field preview

Request sample dataset

This preview shows the record structure without presenting field examples as live data.

Device family and eligible planidentifier / label
Tenure options and repayment structureidentifier / label
Subsidy, lock-in, and upgrade patternstructured value
Bundle dependency and included benefitsstructured value
Channel availability and offer evidenceevidence metadata
First seen, last seen, and change typeevidence metadata

Dataset scope

Refresh cadence

Periodic by market scope.

Coverage

Expansion by demand.

Evidence depth

Source URL, Capture timestamp, Screenshot archive, HTML or document archive where available, Version hash, QA status

EVIDENCE REFERENCES

Proof fields travel with the record.

Records are designed to preserve the source, capture state, and QA context needed for downstream review.

Source URLCapture timestampScreenshot referenceDocument referenceVersion hashQA state

VERSION HISTORY

Offer change trail.

1First seencapturevh_01a2
2Promo price addedprice deltavh_02b7
3Eligibility changedrule updatevh_03c4
4Allowance updatedbundle deltavh_04f9
5Offer retiredstatus changevh_05d1

Related datasets

Adjacent signals

Request sample dataset
T1.5

Bundle & Cross-Service Offers

In buildTelecomPricing & Promo Intelligence

Structures mobile, fixed, TV, OTT, gaming, family, and cross-service bundle offer attributes for comparison and monitoring.

Use cases
Competitive pricing intelligencePromo and portfolio monitoring
Key fields
Bundle type, such as mobile plus fixedStandalone versus bundle price comparison
View dataset
T1.6

Device Pricing & Financing Matrix

In buildTelecomPricing & Promo Intelligence

Maps publicly observable device pricing, financing labels, plan dependencies, contract terms, and bundle conditions.

Use cases
Competitive pricing intelligencePromo and portfolio monitoring
Key fields
Device variant, storage, and color metadataCash price versus installment price
View dataset

Next step

Request a sample or map this dataset to your workflow.

DAISORO can discuss market scope, evidence depth, delivery model, and sample structure for your workflow.

Back to catalogue