Source-aware field guide · 20 answers
TradeLocker Broker and Prop Platform
An operator guide to TradeLocker procurement, broker and prop-firm responsibilities, integration evidence, acceptance tests and handover controls.
Published · reviewed for scope, source visibility and answer ownership
How to use this guide
TradeLocker describes itself as a trading platform rather than a broker or prop firm. Its public help center directs traders to their broker or prop firm for account creation, credentials, funds, deposits, withdrawals, leverage, fees, instruments, execution and other account conditions. A buyer therefore needs a responsibility map that separates TradeLocker software from the operator, CRM, liquidity provider, bridge, payment provider, market-data source and implementation partner.
Use this guide to convert a demonstration into a procurement schedule and acceptance plan. Record the contracting entities, license model, environments, administrator roles, interfaces, data ownership, operating controls and escalation routes. Test ordinary workflows and failure cases with traceable accounts and timestamps. Keep screenshots, exports and signed outcomes so the launch decision rests on evidence rather than a feature label or a sales summary.
The cited TradeLocker pages are public supplier material reviewed for this collection. They do not establish the price, capacity, integration list, implementation timetable or support terms available to a particular operator. Those items may differ by contract and provider. Third-party CRM, liquidity, bridge and payment responsibilities must be confirmed directly with the relevant supplier and reproduced in the signed deployment record. Recheck the sources and contract before launch.
How to Map TradeLocker Operator Responsibilities
Create a responsibility matrix that separates the TradeLocker software from the broker or prop firm, CRM, liquidity provider, bridge, payment provider and implementation partner. Assign an accountable entity, named owner, evidence item and escalation route to every workflow.
- Use it to
- Use the matrix during contracting and repeat it in the launch runbook so staff know where each incident belongs.
- Check the boundary
- TradeLocker's help center says the broker or prop firm controls account services; the platform should not be presented as the counterparty for those services.
How to Build a TradeLocker Procurement Matrix
Compare TradeLocker proposals line by line for license scope, environments, user channels, administration, APIs, branding, market data, integrations, implementation, training, support, termination and data export. Mark each item included, optional, third-party or not offered.
- Use it to
- Require documentary evidence and an acceptance test beside each required line before treating two offers as comparable.
- Check the boundary
- Public feature pages do not define the commercial package. Pricing and inclusions that are not in current public material are not publicly disclosed.
What Belongs in a TradeLocker License Schedule
The license schedule should identify the contracting party, permitted business model, brands, domains, environments, territories, account volumes or other metering basis, administrator access, integrations, renewal terms, suspension triggers, termination steps and export rights.
- Use it to
- Cross-reference every commercial line to the technical scope and store the executed version with the configuration baseline.
- Check the boundary
- A broker license and a prop-firm license can have different terms; do not infer permission for one operating model from the other.
How to Accept a TradeLocker Broker Launch
Accept a broker launch only after registration, verification, account creation, symbol visibility, order entry, execution reporting, deposit notification, withdrawal review, client statements, staff permissions and incident escalation pass against signed test cases.
- Use it to
- Capture account IDs, timestamps, expected results, actual results and defect disposition in a launch-gate pack signed by business and technical owners.
- Check the boundary
- A successful terminal login does not prove that the broker's CRM, payments, liquidity, reporting or client-service controls are ready.
How to Accept a TradeLocker Prop Firm Launch
Test purchase, account provisioning, trading access, rule calculation, pass, breach, retry, payout review, trader notice, manual review and dispute reconstruction. Link every result to the operator's published rule version and source data.
- Use it to
- Run deterministic accounts through normal and edge cases, then preserve platform events and CRM decisions in one evidence bundle.
- Check the boundary
- TradeLocker supplies trading software; evaluation rules, checkout, payouts and trader decisions remain operator or third-party responsibilities unless the contract says otherwise.
How to Test TradeLocker Account Provisioning
Provision test accounts from every approved source and verify identifiers, group, currency, leverage, balance, symbols, permissions, credentials and lifecycle status. Include duplicate, rejected, delayed and retried requests as well as a clean creation.
- Use it to
- Reconcile the originating CRM record with the platform account and record the idempotency or duplicate-prevention behavior.
- Check the boundary
- TradeLocker's public help directs account and credential issues to the broker or prop firm, so the operator must own the end-to-end result.
How to Define TradeLocker CRM Responsibility
Define which system owns prospect data, KYC status, client profiles, trading-account requests, deposits, withdrawals, support records and lifecycle states. Specify the connector owner, field mappings, retry rules, audit logs and reconciliation frequency.
- Use it to
- Use a source-of-truth table and test updates in both directions, including failures that leave the systems temporarily inconsistent.
- Check the boundary
- A TradeLocker license should not be assumed to include a third-party CRM or its implementation, maintenance and data-quality controls.
How to Verify TradeLocker KYC Handoffs
Document where identity checks occur, which status authorizes account creation, what evidence is retained, how expiry or re-review is handled and which system blocks restricted users. Test approved, rejected, pending and manually escalated cases.
- Use it to
- Trace a single client from onboarding evidence through CRM decision to platform access and preserve the status history.
- Check the boundary
- The trading platform is not proof of regulatory suitability or completed KYC; the operator must apply its own legal and compliance requirements.
Who Owns TradeLocker Deposits and Withdrawals
The broker or prop firm and its payment providers own funding decisions, settlement and client communication. The implementation scope should identify how approved payment events appear in the CRM and platform, who reconciles them and who resolves exceptions.
- Use it to
- Test successful, failed, reversed, duplicated and delayed events plus a withdrawal requiring enhanced review before approval.
- Check the boundary
- TradeLocker's help material directs funds and payment questions to the operator; platform display does not prove settlement or provider acceptance.
How to Validate TradeLocker Chart Data
Identify the liquidity or data source for every instrument and compare timestamps, trading sessions, bid and ask values, candles and outage behavior with the agreed feed. Record the timezone and aggregation rules used by each view.
- Use it to
- Run a timed sample across the platform, source feed and execution records, then explain any expected transformation or delay.
- Check the boundary
- TradeLocker's help center states that chart data comes from the liquidity provider; platform presentation alone cannot establish source-feed accuracy.
How to Scope TradeLocker Liquidity and Bridge
List the liquidity counterparty, bridge or routing component, connectivity owner, symbol mapping, price-feed source, execution path, reconciliation files, monitoring and failover. State which provider contracts and supports each link.
- Use it to
- Use a sequence diagram and execute normal, rejected, disconnected and recovered orders while collecting logs at every boundary.
- Check the boundary
- Do not imply that a TradeLocker license includes third-party liquidity or bridge services unless the signed proposal names them and their responsibilities.
How to Test TradeLocker Order Routing
Build test cases for supported order types, market status, quantity limits, rejects, partial fills, modifications, cancellations, disconnects and recovery. Match client-visible states to platform logs, routing records and downstream execution reports.
- Use it to
- Assign expected codes and timestamps before testing so reviewers can distinguish correct rejection from an integration defect.
- Check the boundary
- Routing behavior depends on the operator's configuration and connected execution providers; do not infer it from the interface alone.
How to Approve TradeLocker Instrument Settings
Approve instruments from a controlled specification containing identifiers, display names, contract size, precision, tick size, sessions, margin, swap, commission and other client conditions. Compare configured values with the approved source before release.
- Use it to
- Export the active configuration, sample calculations and screenshots, then have product, risk and operations sign the same version.
- Check the boundary
- TradeLocker's help center directs instrument and trading-condition questions to the broker or prop firm; those settings are operator responsibilities.
How to Control TradeLocker Margin, Fees and Swaps
Maintain approved formulas and effective dates for leverage, margin, commission, spreads or markups, swaps and other charges. Test representative positions, account groups, overnight events and configuration changes against independently calculated expected values.
- Use it to
- Publish client terms from the same approved configuration source and reconcile charged amounts after every material release.
- Check the boundary
- TradeLocker's public guidance says the broker or prop firm determines these conditions; the platform does not validate their legal or commercial appropriateness.
How to Accept TradeLocker Branding
List every approved brand element, domain, application name, icon, color, legal notice and store asset. Verify them across supported web, desktop and mobile channels, including login, account, error and notification states.
- Use it to
- Use a device-and-screen checklist with dated captures, approver names and ownership records for domains and app-store accounts.
- Check the boundary
- Visual approval should follow confirmed license rights and technical feasibility; a mockup is not evidence that every channel is included.
How to Review TradeLocker Admin Permissions
Create a role matrix for onboarding, account operations, risk, finance, support, configuration and audit. Test least-privilege access, separation of duties, approval steps, denied actions, user removal and the audit trail for sensitive changes.
- Use it to
- Issue named test users for each role and preserve both successful and blocked outcomes before production credentials are released.
- Check the boundary
- Requested administrator functions may depend on the contracted license and provider arrangement, so verify actual access rather than assuming full control.
What TradeLocker Integration Evidence Is Needed
Retain interface specifications, field mappings, credential ownership, environment endpoints, test cases, logs, defect decisions, reconciliation results and signed acceptance for every CRM, liquidity, bridge, payment and reporting connection.
- Use it to
- Index the evidence by interface and release so an operator can reconstruct what changed and which test proved the new behavior.
- Check the boundary
- A vendor logo or connector name confirms neither production readiness nor commercial entitlement; verify the exact version and supported workflow.
How to Plan a TradeLocker Migration
Inventory accounts, balances, positions, orders, history, credentials, reports and consent records, then define what will move, transform, archive or remain read-only. Rehearse extraction, reconciliation, cutover, communication and rollback with production-like data.
- Use it to
- Set measurable reconciliation tolerances and require business owners to sign exceptions before the migration decision point.
- Check the boundary
- Data portability and import capability are contract- and system-dependent; confirm export formats, retention and provider assistance before committing to dates.
How to Triage TradeLocker Incidents
Classify incidents by client interface, operator configuration, CRM, payment service, market data, liquidity, bridge, network or TradeLocker service. Collect account, instrument, timestamps, request IDs, screenshots and relevant logs before routing the case.
- Use it to
- Use one incident record with a named owner, severity rule, provider ticket, workaround, client communication and closure evidence.
- Check the boundary
- Sending every issue to the platform provider delays diagnosis when the broker, prop firm or a third party controls the affected workflow.
How to Record TradeLocker Commercial Terms
Record setup, recurring, usage, integration, environment, branding, support, training, migration, renewal and exit charges using the supplier's actual units and assumptions. Keep taxes, third-party services and optional work on separate lines.
- Use it to
- Calculate comparable scenarios from the signed quote and store the quote date, currency, validity period and exclusions with the decision record.
- Check the boundary
- Where current official public pages do not state a price, describe it as not publicly disclosed and obtain a written quotation rather than inventing a figure.
Primary and official references
These sources establish definitions, standards or official product behavior used across this guide. Follow the exact source and check its current version before a live implementation.