Skip to content

BDS / Intraday usability

Intraday Provider Compatibility: Product, Instrument and Session

An advertised mechanism can be genuine while the selected plan does not fit the reader's account or clock.

Edition: 12 October 2026. Desk research and labelled teaching scenarios.

Keep the selected product attached

Name the plan and actual output before comparing a brand. A forex publisher can have a separate swing product; a platform can supply both chart tools and automation. The existence of one capability does not establish the purchased entitlement.

Retain a product identifier and the governing source date. When a plan changes name, ask whether its terms or delivery changed rather than assuming older reviews remain current.

Resolve the instrument

Confirm venue, contract or product type, quote currency and account availability as relevant. Do not infer a market count or every tradeable instrument from a broad product description. A familiar ticker is not complete compatibility evidence.

For copying, inspect the selected source and follower conditions. For manual messages, determine how the original instruction maps to the actual broker product. Unsupported mapping is a hard gap, not a minor preference.

Resolve the session

Ask for the eligible entry window, timezone, latest action and treatment of remaining positions. High activity does not prove a same-session mandate. A source trader may legitimately use a different horizon from the reader.

Do not silently keep only the convenient source trades and present their subset as the product's complete history. The clock mismatch should remain visible in the comparison.

Worked incompatible listing

Hypothetical case: a copying listing has frequent operations, but its open positions can extend beyond the reader's declared session. Frequency alone did not establish the required close policy. The platform mechanism and the reader's mandate are different objects.

The conclusion can be to defer that listing or investigate a different workflow. It does not require an allegation that the platform is defective.

Resolve current terms

Keep the current plan, recurring commitment, required components and cancellation route together. Where product pages conflict, request the governing answer instead of choosing the most attractive amount.

BDS does not maintain an authoritative current-price feed. Its Vector Ridge note specifically preserves unresolved product/campaign conflicts rather than asserting a tariff from older protected records.

Make the mismatch actionable

Name the artifact required to resolve the gap: product entitlement, instrument list, validity policy, follower configuration or official checkout. A specific request can be reviewed when evidence arrives.

A no-purchase outcome is valid when the mandatory boundary remains unclear. Source-linked descriptions are not personal suitability advice or proof of the best subscriber account.

A symbol is only part of identity

Instrument type, venue, contract terms and permitted account product can matter beyond a familiar ticker. A model snapshot does not establish every tradeable scope. Request the actual supported instrument list and record anything still unconfirmed instead of adding a market-count claim.

Compatibility is not a workaround promise

If a required connection is unavailable, a suggested alternative is a different workflow with its own terms and responsibilities. Do not describe an unofficial copier as an established feature of the selected product. Evaluate the alternative separately or leave the purchase deferred.

A source can be useful without final eligibility

An official guide can establish the advertised category while the reader's plan or location remains unconfirmed. This limited finding should stay explicit. It allows research to continue without inventing entitlement, legal status or subscriber safety.

Evidence Packet

Chapter-specific observation packet
Evidence objectRecord to retain
ProductSelected plan and purchased object
InstrumentExact mapping and account availability
SessionValidity and remaining-position policy

Related Session Questions

Session timing and evidence workbench

Primary References

The sources support documented mechanisms and source definitions. Our procedure and teaching examples are not completed paid-feed, latency or account tests.