MT5 White Label Platform Customization: What Is Included and What Is Extra
A white label is sold on control, but control comes in layers and each layer can carry a price. This guide helps buyers separate the customization that is normally included from the options that are billed on top.
Why customization shows up in the price
More control usually means more work for the provider and more risk for the platform owner, so it is often priced. Ask for the options in a list, with a price or a note saying included.
Branding options
Typical items are your company name and logo, a branded server identity and branded client terminals where the platform supports it. Ask which are standard and which need extra fees or approval. See the model in our white label turnkey guide.
Trading condition controls
You normally set account types, groups, leverage, commissions, markups and symbols within platform limits. Check how many groups and account types are included and what extra ones cost.
Integration options
CRM, payment, liquidity and plugin connections are often separate line items. Ask what interfaces you get access to and whether usage fees apply. Compare with the lighter model in grey label customization.
Change requests and updates
After launch, every configuration change may cost time. Ask how changes are requested, how long they take and whether there is a monthly allowance. Then ask who pays for testing after a platform update.
A list to attach to the contract
Ask the provider to list every customization option in a table with columns: option, included or extra, price if extra and lead time. Attach it to the contract.
When something is not on the list, treat it as not included. That one habit prevents most disputes about what a white label “should” have covered.
A customization list to attach to the contract
Attach a list that states, for each customization, whether it is included, extra or unavailable, and the price.
| Customization | Included | Extra price | Lead time |
|---|---|---|---|
| Branding on web and mobile | |||
| Account types and groups | |||
| Leverage and margin rules | |||
| Spread and commission settings | |||
| CRM integration | |||
| Payment integration | |||
| Liquidity bridge | |||
| Reports |
A contract with the list is easier to enforce than one that says "customizable".
A worked example of a change request
A broker wants to add a new account type for introduced clients. The vendor says it is a standard configuration, takes two days and costs a fixed fee. The broker asks for the fee in writing and for a rule that the same price applies to later account types.
Because the process and the price were agreed in advance, the change was quick and no one argued. Agree a process for requests before you need one.
Updates and who controls them
Platform updates may change behaviour. Ask how updates are announced, whether you can test them first and what happens if an update affects your customizations. A vendor that gives notice and a test window respects your operations.
Signs of a thin customization offer
- Everything is described as "available" with no prices.
- Changes need a new contract.
- No test environment.
- A refusal to list what is not possible.
Thin offers become expensive when you need to change something. See our grey label customization guide for the lighter version.
Estimating the effort for each customization
Ask the vendor to estimate effort, in days or hours, for each customization on your list, and the assumptions behind each estimate. Compare with your own sense. If an estimate seems high, ask what it includes. If it seems low, ask what is excluded.
Estimates help you decide which customizations to buy now and which to defer.
Testing and rollback
Ask how customizations are tested before release and how they can be rolled back. A vendor with a clear process protects you from a bad release. Ask for a test environment where you can try changes before clients see them.
Budgeting for ongoing change
Your business will change, so set aside a budget for customization after launch, perhaps a monthly allowance. Ask whether the vendor offers a block of hours at a discount. A planned budget is easier to manage than a series of surprises.
Prioritising customizations by value
List every customization you are considering and estimate the value and cost of each. Value might be extra revenue, lower support cost, reduced risk or better client experience. Cost includes the vendor’s fee, your time and the ongoing maintenance.
Buy the items with the best value-to-cost ratio first and defer the rest. A short, focused list delivers more than a long, ambitious one, and it is easier to test.
Ownership of customized work
Ask who owns customized code, configurations and designs, and what happens to them if you leave. Ask whether they can be reused elsewhere. If the vendor retains ownership, ask for a licence that survives termination. These terms matter when you consider moving to another provider.
Planning a customization roadmap
List customizations in three groups: needed for launch, wanted within six months and ideas for later. Estimate cost and effort for the first two groups and schedule them. Revisit the list each quarter.
A roadmap keeps customization purposeful and prevents ad hoc requests from dominating your vendor relationship.
Frequently asked questions
Why does customization affect price?
Each customization takes effort and carries risk, so vendors price it. Ask for a list with prices.
Can I change settings myself?
Some settings yes, others need a request. Ask which.
Who owns custom work?
This should be in the contract. Confirm it.
How do updates affect my customization?
Ask for notice and a test window before updates.