ON THIS PAGE
Maintain one instrument definition
Symbol management keeps platform names and instrument specifications consistent across feeds, bridges, CRM reports and internal services. A name such as EURUSD may look identical in two systems while its contract size, session or quantity rules differ. Use an explicit instrument inventory rather than treating a matching display name as proof of compatibility.
Record the fields that affect behaviour
The inventory should capture the internal identifier, platform and provider names, decimal precision, contract size, trading and quote sessions, currency fields and relevant volume limits. Include the source of each setting and its owner. Values that affect trading behaviour need review before they are changed in production.
Separate aliases from economic specifications
A suffix or display alias can help distinguish account groups or providers, but it should not hide changes in contract definitions. Maintain mapping tables with explicit identifiers and version history. Where one provider instrument is mapped to several platform symbols, document the differences intentionally.
Test changes across the stack
A symbol update can alter what the platform displays, what the bridge sends and what reports calculate. Check data delivery, permitted quantities, session transitions and account visibility after a change. Review existing integrations and open operational dependencies before removing an instrument.
Deliver an auditable configuration
A useful handover contains the instrument inventory, mappings, configuration baseline and a procedure for proposing updates. Review the platform contract specifications alongside your selected provider definitions. Use Price Feed for distribution requirements and Liquidity Bridge for price and execution mapping.