Routing rules
Define criteria, priority and the destinations available to each workflow.
07 / EXECUTION
A-Book / B-Book Routing
Turn your execution policy into explicit routing rules that can be reviewed, tested and monitored.
Configuration scope
A_B_ROUTING.SRVA routing label alone does not define how orders should behave. TGS Trade scopes the rules, available destinations and operational overrides that implement the broker’s chosen execution model.
Controlled changes
Document the baseline and agree testing and rollback procedures.
Decision visibility
Track route selection, execution responses and behaviour during outages.
Make rule priority reviewable
Translate the selected operating model into rules that can be inspected. State the relevant criteria, available destinations, rule priority and approved operational overrides. Keep a versioned baseline so a routing outcome can be explained in the context of the policy that was active at that time.
Test changes before activating them
A new destination or rule can alter the behaviour of an existing workflow. Agree which test cases are required before activation, which state must be preserved and how the previous configuration can be restored. Include unavailable sessions and uncertain order state in the acceptance discussion instead of treating them as an afterthought.
Acceptance evidence
VERIFY.SYSAgree the test examples and expected results before implementation. The final plan follows the selected systems and interfaces.
| Check | Expected evidence |
|---|---|
| Rule priority | Representative test orders select the expected route when criteria overlap. |
| Destination availability | The agreed policy is followed when an execution endpoint is unavailable. |
| Decision records | The route and relevant rule version can be identified from operational evidence. |
| Change control | The approved baseline and rollback procedure are part of the handover. |
The brokerage selects its execution and risk policy. The technical scope implements the agreed behaviour within the capabilities of the selected systems.
Service questions
README.TXTCan routing use a hybrid model?
The rules can be scoped around a hybrid model when supported by the platform and connected execution components.
Does the service choose our risk policy?
The broker defines its operating and risk policy. The technical project implements and tests the agreed routing behaviour.
Connected modules
RELATED.DIRC:\TGS\CONTACT
DIRECT CONNECTIONDISCUSS YOUR PROJECT
Connect your broker stack.
Tell us which platform you use, which connections you need and what is already in place. We will scope the modules and integration work around your requirements.
Your messenger opens with a draft. Review it and send when ready.
PROJECT TOPICA-Book / B-Book Routing
Message on Telegram@whitelabelmetatraderfx[ New tab ]Message on WhatsApp+358 82 371 1153[ New tab ]Choose a messenger to discuss your project.