2026
Zeki Triko's Move to Nebim ERP
Building retail's decision architecture
A transformation case that handles product variants, stock, store sales and management decisions in fashion retail through a shared data and process discipline. Told from Gökhan Akdağ's management tenure at Zeki Triko; it makes no unverified technical or ROI claims.
ERP Transformation
Fashion Retail
Context
The success of an ERP transition is understood not by a new program going live, but by different units of the organisation giving the same answer to the same stock, sales and margin question.
More than a software project
For a fashion brand, growth is not only about opening a new store or launching a new collection. The real strength lies in having the right product at the right time, in the right size and in the right location. When what the store sells, what headquarters sees and what finance accepts as profitable are not based on the same data, growth may appear to accelerate; but the friction inside the system grows too.
This is what makes the Nebim ERP transition at Zeki Triko valuable to me: not only the technology choice, but defining commercial activities through a shared operating language. The relationship built between product, store, warehouse, sales and decision-making mechanisms is the real subject of an ERP transformation.
The business context: a premium brand, a complex operation
From a premium fashion and retail perspective, Zeki Triko was not simply a matter of selling products; it was a commercial model intertwined with collections, seasons, colours, sizes, positioning, store experience and international markets. In this world, the different sizes of the same product, demand density across stores and the sales rhythm within a season create a decision space far more complex than a single "do we have stock?" question.
Gökhan Akdağ's management tenure of roughly three and a half years at Zeki Triko covered marketing, retail, premium positioning, e-commerce and international growth together. Premium retail experience reaching markets such as Paris, Miami and Dubai made it concrete why the scalability of operations is a strategic matter.
The ERP transformation has to be read at this scale: collection management cannot live apart from retail, retail cannot live apart from financial results, and e-commerce cannot live apart from the reality of physical stock.
The real issue: not more reports, but fewer contradictions
The typical questions at the management table in fashion retail are simple: Which product is selling? Which size is missing where? In which store is stock building up? Which discount actually protects margin? When should we transfer? Which product should be shown online?
The simplicity of these questions is misleading. A sound answer requires product cards, locations, warehouses, prices, orders, sales and return records to speak with the same set of definitions. Reducing ERP to accounting or a till system means missing the core problem that determines decision quality.
The commercial meaning of moving to Nebim was to handle operations around a single language of measurement and responsibility. The critical distinction is this: transferring data into software is a technical task; institutionally defining which data counts as "the right data" is a management decision.
Data and Stock
Dirty data does not get cleaned when it moves into a new system; it simply circulates faster.
The backbone of the transformation: workflow first, screens second
The starting point of a good ERP transition is not the question "which module will we switch on?". First, the product's journey inside the company must be described:
Collection decision → product card → season / colour / size variant → purchasing / sourcing → central stock → allocation to stores → point of sale / digital channel → returns / exchanges → financial record → performance analysis.
When one link in this chain is defined differently, all the remaining reports may look correct yet be incomplete from a decision standpoint. In the Zeki Triko example, the transformation areas to be considered through Nebim are exactly these interconnected layers of the chain.
This framework is used not to overstate software features, but to connect ERP to the business model.
Product master data: model, colour, size and season must be one truth
In fashion retail a "product" is not a single line. A model's size and colour variants and its collection and season links change what the product means at each point of sale. When coding discipline is weak, transfers, stock counts, sales analysis and discount performance weaken too.
The first agenda of data governance therefore consists of: product hierarchy; variant definitions; season and collection tags; uniqueness of barcode / stock code; product statuses; category ownership; rights to create, correct and deactivate data.
Management lesson: Dirty data does not get cleaned when it moves into a new system; it simply circulates faster. Before an ERP project starts, the owner of the product dictionary must be clear.
Visibility between store and headquarters
The product physically present in a store and the quantity shown as "sellable stock" at headquarters are not always the same concept. Reserved items, items in transfer, count differences, items awaiting return and display items lead to different decisions. Reading store sales performance soundly depends on these distinctions.
That is why the store–warehouse–headquarters data relationship must define not only quantity but stock status, location, transaction time and responsibility. This approach gives the central team a more reliable basis for decisions and gives stores a clearer transaction discipline.
Stock allocation and transfer: reading demand, not just distributing product
A product moving slowly in one store may be missing stock that loses demand in another. A decision about the same model in the same season should not be taken without reading together the store profile, sales velocity, size breakdown, current stock, transfer cost and the remaining season.
This is where the commercial value of the ERP transformation becomes clear. A transfer should be seen not merely as a warehouse movement but as repositioning a potential sale. Yet not every transfer is right: consuming a low unit margin with a high transfer cost can increase the store's sales while reducing the company's profitability.
A usable decision matrix is therefore:
Demand: sales rhythm and size breakdown over the last 4 / 8 weeks.
Inventory: on-hand, in-transit, reserved and available stock.
Economics: product margin, transfer cost, estimated probability of sale.
Time: time left until season end, possibility of reordering.
Alternative: transfer, price decision, digital sale or hold?
These items are an explanatory management framework; they should not be presented as a software algorithm used one-to-one in the project or as realised decision records.
Store, Price and Channel
The real value of a KPI is not in the report but in the decision you take afterwards.
Translating store sales data into commercial language
Revenue alone does not tell how healthy a store is. Units, gross margin, conversion, average transaction value (ATV), units per transaction (UPT), sales per m² and like-for-like growth (LFL) should be monitored together for the same period.
The purpose of this measurement language is not to put stores into a single league table. Is a store's low performance caused by location, missing size distribution, pricing, window display or staff training? Data alone does not produce the answer; it makes sure the right question is asked.
Management lesson: The real value of a KPI is not in the report but in the decision you take afterwards. ERP turns into commercial value to the extent that it makes decisions visible and traceable.
Price, promotion and premium brand discipline
In a premium brand, a discount is not just a sales-boosting button. A wrong price hierarchy can create inconsistency between stores; excessive promotion can weaken the brand's long-term pricing power.
For this reason, in the relationship between ERP and commercial management, list price, campaign authority, end-of-season discounts, store-level differences and margin impact should be assessed within the same control framework. The store's daily target and the brand's medium-term positioning should not contradict each other.
The bridge between e-commerce and physical retail
When physical and digital sales rely on different stock and product truths, the customer experience becomes fragile. A product shown on a website but not actually available creates lost sales as well as costs in customer trust and operations.
When the e-commerce connection is addressed in an ERP programme, product information, stock availability, order status, returns, cancellations, sales channel and financial reconciliation must be assessed together. This is a commercial architecture problem that goes beyond the phrase "the website is connected to the ERP".
E-commerce and premium retail growth at Zeki Triko explain the strategic importance of this integrated view; however, this page does not claim that e-commerce growth happened directly because of the Nebim transition.
Authority matrix and responsibility design
A transformation needs owners of decisions as much as owners of software screens. Who opens a product card? Who approves a stock correction? Who owns transfers between stores? Who defines a price exception? Who closes a return discrepancy? At what point does finance reconcile?
If these questions are not answered, the company may technically move to a single system yet keep its old habits from a management perspective.
Example responsibility map: category and product teams own product master data; retail operations own the accuracy of store movements; finance owns the record–reconciliation relationship; IT owns system access and integration health; top management owns exceptions and the decision rhythm. This map is a proposed governance logic; it is not Zeki Triko's verified official organisation chart.
Management and Lessons
In retail, scale means decision quality does not drop as more stores open.
Change management: the most important integration is people
ERP transitions are often described in the language of data or software. Yet a transformation cannot be considered complete unless the daily behaviour of store staff, stock teams and managers deciding at headquarters changes.
Training should teach not only which key to press but the commercial reason behind the transaction. Why does a missing sales record break stock accuracy? Why does a delayed return show inventory wrongly? Why does a wrong size code lead to wrong product allocation? When users see this chain, compliance turns from an obligation into a shared responsibility.
Controlled validation instead of an uncontrolled "go-live"
A solid transition methodology should test product data, opening stocks, sales and return scenarios, store transfers, pricing rules, financial records, user authorisations and report reconciliation. If necessary, a pilot store, parallel reporting, a rollback plan and an issue-tracking system are run.
The items listed here are good-practice checkpoints. Since we do not have project minutes showing exactly which pilot, test scenario or transition schedule was used at Zeki Triko, no dates or details claimed to have been applied have been invented.
What does the transformation change at the management level?
A well-designed ERP programme aims at three fundamental behavioural changes:
One: Testing intuition with data. An experienced store manager's observation remains valuable; but it is evaluated together with stock, sales velocity and margin data.
Two: Separating local success from company success. If a store grows its own sales while reducing company margin through stock or discount effects, this must become visible.
Three: Not normalising the exception. Last-minute Excel corrections, off-system price lists and person-dependent workarounds should not become a permanent business model.
The real value of an ERP transformation is not producing more screens; it is being able to decide with less uncertainty.
Measurement model: how is real success proven?
For an ERP project to count as a "success", sales growth alone is not sufficient evidence. Indicators that can be measured in such a project include:
Stock accuracy rate: alignment between physical counts and the system.
In-stock availability: the requested size / variant being available at the relevant location.
Stock turnover: the pace at which held stock turns into sales.
Full-price sell-through: the share of products sold without discount.
Stock ageing: slow-moving inventory carried to season end.
Transfer efficiency: post-transfer sales relative to transfer cost.
Return and reconciliation differences: frequency of wrong records / closing delays.
Report production time: speed at which analysis reaches decision makers.
User adoption rate: transactions completed without leaving the process.
In the published case these indicators appear as measurement proposals; they are not measured project results for Zeki Triko. Exact before–after values can only be added from internal reports.
The commercial scale of the Zeki Triko period and separately measured achievements
Among the commercial performance highlights of Gökhan Akdağ's roughly 3.5-year management experience at Zeki Triko, previously shared, are an approximately 135% increase in like-for-like (LFL) store revenue and international premium retail expansion including Paris, Miami and Dubai. The career narrative also mentions around 25 premium store openings.
Important distinction: These belong to the broader commercial and brand development context of the management period. They are not presented as independent, causal and measured effects of the Nebim transition. No exact savings, staff productivity, stock reduction or return on investment (ROI) figure for the ERP project has been shared.
Why does this case still matter today?
Today ERP, POS, e-commerce, CRM and analytics platforms may be more advanced. But the fundamental question of the business has not changed: are store, product, customer and finance data turning into a shared decision system?
The leadership lesson drawn from the Nebim ERP transition at Zeki Triko is that retail technology must be handled together with operational discipline and brand strategy. A company that only changes its system moves data. A company that also develops its business rules, data ownership and way of deciding builds a scalable organisation.
Gökhan Akdağ's perspective
"For me, an ERP transformation is not a software purchasing story; it is about being able to connect the reality of the store to the board's decision. The right system is not the one that produces the most reports, but the one that makes the wrong decision visible earlier."
This statement is an editorial assessment written for this case text; it should not be presented as a historical interview quote.
Who can learn from this case?
This case is particularly relevant for multi-store fashion retailers, brands carrying season- and variant-based stock, management teams redesigning store–e-commerce integration, family businesses that want to protect data quality during growth and senior leaders who do not want to see the ERP decision merely as an IT project.
Final word: In retail, scale is not just a larger number of stores. Scale means decision quality does not drop as more stores open.
Related reading and contact
Related case: Lelas's Transition to SAP Systems
Frequently Asked Questions
Why was the move to Nebim ERP a strategic issue at Zeki Triko?
In fashion retail, product variants, stock, stores, sales and finance form the same decision chain. Moving to ERP requires rethinking this chain in terms of data consistency and management responsibility.
What is the most important criterion when choosing an ERP for fashion retail?
Not a single feature list, but overall fit with the business model: model–colour–size tracking, multi-location inventory, store operations, pricing rules, digital channel needs and reporting processes.
Is Nebim ERP used only for stock tracking?
No. According to Nebim's public product documentation, the solution family covers interconnected areas such as retail sales, channel management, store performance and stock processes. However, this general platform information does not show that all modules were used in the Zeki Triko project.
What are the biggest risks in an ERP transition?
Faulty product master data, unclear process ownership, insufficient user training, untested integrations and reducing project success measurement to a technical go-live.
How much did the move to Nebim ERP increase Zeki Triko's sales?
No project-specific causal sales increase or ROI figure has been publicly verified. Other commercial achievements of the management period are not presented as direct results of the ERP transition.
Why should ERP transformation be on the top management agenda?
ERP affects who trusts which data, who takes which decision and who takes responsibility. That makes it a matter of organisation and commercial management, not only technology.
More Works
(Gökhan Akdağ)
©2026
FAQ
01
What does GA Consulting do?
02
What is your approach?
03
How do projects progress?
04
What is your focus?
05
Which areas do you work in?
06
What value does it create for companies?
07
Which companies is it right for?
08
How long until a project delivers results?
2026
Zeki Triko's Move to Nebim ERP
Building retail's decision architecture
A transformation case that handles product variants, stock, store sales and management decisions in fashion retail through a shared data and process discipline. Told from Gökhan Akdağ's management tenure at Zeki Triko; it makes no unverified technical or ROI claims.
ERP Transformation
Fashion Retail
Context
The success of an ERP transition is understood not by a new program going live, but by different units of the organisation giving the same answer to the same stock, sales and margin question.
More than a software project
For a fashion brand, growth is not only about opening a new store or launching a new collection. The real strength lies in having the right product at the right time, in the right size and in the right location. When what the store sells, what headquarters sees and what finance accepts as profitable are not based on the same data, growth may appear to accelerate; but the friction inside the system grows too.
This is what makes the Nebim ERP transition at Zeki Triko valuable to me: not only the technology choice, but defining commercial activities through a shared operating language. The relationship built between product, store, warehouse, sales and decision-making mechanisms is the real subject of an ERP transformation.
The business context: a premium brand, a complex operation
From a premium fashion and retail perspective, Zeki Triko was not simply a matter of selling products; it was a commercial model intertwined with collections, seasons, colours, sizes, positioning, store experience and international markets. In this world, the different sizes of the same product, demand density across stores and the sales rhythm within a season create a decision space far more complex than a single "do we have stock?" question.
Gökhan Akdağ's management tenure of roughly three and a half years at Zeki Triko covered marketing, retail, premium positioning, e-commerce and international growth together. Premium retail experience reaching markets such as Paris, Miami and Dubai made it concrete why the scalability of operations is a strategic matter.
The ERP transformation has to be read at this scale: collection management cannot live apart from retail, retail cannot live apart from financial results, and e-commerce cannot live apart from the reality of physical stock.
The real issue: not more reports, but fewer contradictions
The typical questions at the management table in fashion retail are simple: Which product is selling? Which size is missing where? In which store is stock building up? Which discount actually protects margin? When should we transfer? Which product should be shown online?
The simplicity of these questions is misleading. A sound answer requires product cards, locations, warehouses, prices, orders, sales and return records to speak with the same set of definitions. Reducing ERP to accounting or a till system means missing the core problem that determines decision quality.
The commercial meaning of moving to Nebim was to handle operations around a single language of measurement and responsibility. The critical distinction is this: transferring data into software is a technical task; institutionally defining which data counts as "the right data" is a management decision.
Data and Stock
Dirty data does not get cleaned when it moves into a new system; it simply circulates faster.
The backbone of the transformation: workflow first, screens second
The starting point of a good ERP transition is not the question "which module will we switch on?". First, the product's journey inside the company must be described:
Collection decision → product card → season / colour / size variant → purchasing / sourcing → central stock → allocation to stores → point of sale / digital channel → returns / exchanges → financial record → performance analysis.
When one link in this chain is defined differently, all the remaining reports may look correct yet be incomplete from a decision standpoint. In the Zeki Triko example, the transformation areas to be considered through Nebim are exactly these interconnected layers of the chain.
This framework is used not to overstate software features, but to connect ERP to the business model.
Product master data: model, colour, size and season must be one truth
In fashion retail a "product" is not a single line. A model's size and colour variants and its collection and season links change what the product means at each point of sale. When coding discipline is weak, transfers, stock counts, sales analysis and discount performance weaken too.
The first agenda of data governance therefore consists of: product hierarchy; variant definitions; season and collection tags; uniqueness of barcode / stock code; product statuses; category ownership; rights to create, correct and deactivate data.
Management lesson: Dirty data does not get cleaned when it moves into a new system; it simply circulates faster. Before an ERP project starts, the owner of the product dictionary must be clear.
Visibility between store and headquarters
The product physically present in a store and the quantity shown as "sellable stock" at headquarters are not always the same concept. Reserved items, items in transfer, count differences, items awaiting return and display items lead to different decisions. Reading store sales performance soundly depends on these distinctions.
That is why the store–warehouse–headquarters data relationship must define not only quantity but stock status, location, transaction time and responsibility. This approach gives the central team a more reliable basis for decisions and gives stores a clearer transaction discipline.
Stock allocation and transfer: reading demand, not just distributing product
A product moving slowly in one store may be missing stock that loses demand in another. A decision about the same model in the same season should not be taken without reading together the store profile, sales velocity, size breakdown, current stock, transfer cost and the remaining season.
This is where the commercial value of the ERP transformation becomes clear. A transfer should be seen not merely as a warehouse movement but as repositioning a potential sale. Yet not every transfer is right: consuming a low unit margin with a high transfer cost can increase the store's sales while reducing the company's profitability.
A usable decision matrix is therefore:
Demand: sales rhythm and size breakdown over the last 4 / 8 weeks.
Inventory: on-hand, in-transit, reserved and available stock.
Economics: product margin, transfer cost, estimated probability of sale.
Time: time left until season end, possibility of reordering.
Alternative: transfer, price decision, digital sale or hold?
These items are an explanatory management framework; they should not be presented as a software algorithm used one-to-one in the project or as realised decision records.
Store, Price and Channel
The real value of a KPI is not in the report but in the decision you take afterwards.
Translating store sales data into commercial language
Revenue alone does not tell how healthy a store is. Units, gross margin, conversion, average transaction value (ATV), units per transaction (UPT), sales per m² and like-for-like growth (LFL) should be monitored together for the same period.
The purpose of this measurement language is not to put stores into a single league table. Is a store's low performance caused by location, missing size distribution, pricing, window display or staff training? Data alone does not produce the answer; it makes sure the right question is asked.
Management lesson: The real value of a KPI is not in the report but in the decision you take afterwards. ERP turns into commercial value to the extent that it makes decisions visible and traceable.
Price, promotion and premium brand discipline
In a premium brand, a discount is not just a sales-boosting button. A wrong price hierarchy can create inconsistency between stores; excessive promotion can weaken the brand's long-term pricing power.
For this reason, in the relationship between ERP and commercial management, list price, campaign authority, end-of-season discounts, store-level differences and margin impact should be assessed within the same control framework. The store's daily target and the brand's medium-term positioning should not contradict each other.
The bridge between e-commerce and physical retail
When physical and digital sales rely on different stock and product truths, the customer experience becomes fragile. A product shown on a website but not actually available creates lost sales as well as costs in customer trust and operations.
When the e-commerce connection is addressed in an ERP programme, product information, stock availability, order status, returns, cancellations, sales channel and financial reconciliation must be assessed together. This is a commercial architecture problem that goes beyond the phrase "the website is connected to the ERP".
E-commerce and premium retail growth at Zeki Triko explain the strategic importance of this integrated view; however, this page does not claim that e-commerce growth happened directly because of the Nebim transition.
Authority matrix and responsibility design
A transformation needs owners of decisions as much as owners of software screens. Who opens a product card? Who approves a stock correction? Who owns transfers between stores? Who defines a price exception? Who closes a return discrepancy? At what point does finance reconcile?
If these questions are not answered, the company may technically move to a single system yet keep its old habits from a management perspective.
Example responsibility map: category and product teams own product master data; retail operations own the accuracy of store movements; finance owns the record–reconciliation relationship; IT owns system access and integration health; top management owns exceptions and the decision rhythm. This map is a proposed governance logic; it is not Zeki Triko's verified official organisation chart.
Management and Lessons
In retail, scale means decision quality does not drop as more stores open.
Change management: the most important integration is people
ERP transitions are often described in the language of data or software. Yet a transformation cannot be considered complete unless the daily behaviour of store staff, stock teams and managers deciding at headquarters changes.
Training should teach not only which key to press but the commercial reason behind the transaction. Why does a missing sales record break stock accuracy? Why does a delayed return show inventory wrongly? Why does a wrong size code lead to wrong product allocation? When users see this chain, compliance turns from an obligation into a shared responsibility.
Controlled validation instead of an uncontrolled "go-live"
A solid transition methodology should test product data, opening stocks, sales and return scenarios, store transfers, pricing rules, financial records, user authorisations and report reconciliation. If necessary, a pilot store, parallel reporting, a rollback plan and an issue-tracking system are run.
The items listed here are good-practice checkpoints. Since we do not have project minutes showing exactly which pilot, test scenario or transition schedule was used at Zeki Triko, no dates or details claimed to have been applied have been invented.
What does the transformation change at the management level?
A well-designed ERP programme aims at three fundamental behavioural changes:
One: Testing intuition with data. An experienced store manager's observation remains valuable; but it is evaluated together with stock, sales velocity and margin data.
Two: Separating local success from company success. If a store grows its own sales while reducing company margin through stock or discount effects, this must become visible.
Three: Not normalising the exception. Last-minute Excel corrections, off-system price lists and person-dependent workarounds should not become a permanent business model.
The real value of an ERP transformation is not producing more screens; it is being able to decide with less uncertainty.
Measurement model: how is real success proven?
For an ERP project to count as a "success", sales growth alone is not sufficient evidence. Indicators that can be measured in such a project include:
Stock accuracy rate: alignment between physical counts and the system.
In-stock availability: the requested size / variant being available at the relevant location.
Stock turnover: the pace at which held stock turns into sales.
Full-price sell-through: the share of products sold without discount.
Stock ageing: slow-moving inventory carried to season end.
Transfer efficiency: post-transfer sales relative to transfer cost.
Return and reconciliation differences: frequency of wrong records / closing delays.
Report production time: speed at which analysis reaches decision makers.
User adoption rate: transactions completed without leaving the process.
In the published case these indicators appear as measurement proposals; they are not measured project results for Zeki Triko. Exact before–after values can only be added from internal reports.
The commercial scale of the Zeki Triko period and separately measured achievements
Among the commercial performance highlights of Gökhan Akdağ's roughly 3.5-year management experience at Zeki Triko, previously shared, are an approximately 135% increase in like-for-like (LFL) store revenue and international premium retail expansion including Paris, Miami and Dubai. The career narrative also mentions around 25 premium store openings.
Important distinction: These belong to the broader commercial and brand development context of the management period. They are not presented as independent, causal and measured effects of the Nebim transition. No exact savings, staff productivity, stock reduction or return on investment (ROI) figure for the ERP project has been shared.
Why does this case still matter today?
Today ERP, POS, e-commerce, CRM and analytics platforms may be more advanced. But the fundamental question of the business has not changed: are store, product, customer and finance data turning into a shared decision system?
The leadership lesson drawn from the Nebim ERP transition at Zeki Triko is that retail technology must be handled together with operational discipline and brand strategy. A company that only changes its system moves data. A company that also develops its business rules, data ownership and way of deciding builds a scalable organisation.
Gökhan Akdağ's perspective
"For me, an ERP transformation is not a software purchasing story; it is about being able to connect the reality of the store to the board's decision. The right system is not the one that produces the most reports, but the one that makes the wrong decision visible earlier."
This statement is an editorial assessment written for this case text; it should not be presented as a historical interview quote.
Who can learn from this case?
This case is particularly relevant for multi-store fashion retailers, brands carrying season- and variant-based stock, management teams redesigning store–e-commerce integration, family businesses that want to protect data quality during growth and senior leaders who do not want to see the ERP decision merely as an IT project.
Final word: In retail, scale is not just a larger number of stores. Scale means decision quality does not drop as more stores open.
Related reading and contact
Related case: Lelas's Transition to SAP Systems
Frequently Asked Questions
Why was the move to Nebim ERP a strategic issue at Zeki Triko?
In fashion retail, product variants, stock, stores, sales and finance form the same decision chain. Moving to ERP requires rethinking this chain in terms of data consistency and management responsibility.
What is the most important criterion when choosing an ERP for fashion retail?
Not a single feature list, but overall fit with the business model: model–colour–size tracking, multi-location inventory, store operations, pricing rules, digital channel needs and reporting processes.
Is Nebim ERP used only for stock tracking?
No. According to Nebim's public product documentation, the solution family covers interconnected areas such as retail sales, channel management, store performance and stock processes. However, this general platform information does not show that all modules were used in the Zeki Triko project.
What are the biggest risks in an ERP transition?
Faulty product master data, unclear process ownership, insufficient user training, untested integrations and reducing project success measurement to a technical go-live.
How much did the move to Nebim ERP increase Zeki Triko's sales?
No project-specific causal sales increase or ROI figure has been publicly verified. Other commercial achievements of the management period are not presented as direct results of the ERP transition.
Why should ERP transformation be on the top management agenda?
ERP affects who trusts which data, who takes which decision and who takes responsibility. That makes it a matter of organisation and commercial management, not only technology.
More Works
(Gökhan Akdağ)
©2026
FAQ
01
What does GA Consulting do?
02
What is your approach?
03
How do projects progress?
04
What is your focus?
05
Which areas do you work in?
06
What value does it create for companies?
07
Which companies is it right for?
08
How long until a project delivers results?
2026
Zeki Triko's Move to Nebim ERP
Building retail's decision architecture
A transformation case that handles product variants, stock, store sales and management decisions in fashion retail through a shared data and process discipline. Told from Gökhan Akdağ's management tenure at Zeki Triko; it makes no unverified technical or ROI claims.
ERP Transformation
Fashion Retail
Context
The success of an ERP transition is understood not by a new program going live, but by different units of the organisation giving the same answer to the same stock, sales and margin question.
More than a software project
For a fashion brand, growth is not only about opening a new store or launching a new collection. The real strength lies in having the right product at the right time, in the right size and in the right location. When what the store sells, what headquarters sees and what finance accepts as profitable are not based on the same data, growth may appear to accelerate; but the friction inside the system grows too.
This is what makes the Nebim ERP transition at Zeki Triko valuable to me: not only the technology choice, but defining commercial activities through a shared operating language. The relationship built between product, store, warehouse, sales and decision-making mechanisms is the real subject of an ERP transformation.
The business context: a premium brand, a complex operation
From a premium fashion and retail perspective, Zeki Triko was not simply a matter of selling products; it was a commercial model intertwined with collections, seasons, colours, sizes, positioning, store experience and international markets. In this world, the different sizes of the same product, demand density across stores and the sales rhythm within a season create a decision space far more complex than a single "do we have stock?" question.
Gökhan Akdağ's management tenure of roughly three and a half years at Zeki Triko covered marketing, retail, premium positioning, e-commerce and international growth together. Premium retail experience reaching markets such as Paris, Miami and Dubai made it concrete why the scalability of operations is a strategic matter.
The ERP transformation has to be read at this scale: collection management cannot live apart from retail, retail cannot live apart from financial results, and e-commerce cannot live apart from the reality of physical stock.
The real issue: not more reports, but fewer contradictions
The typical questions at the management table in fashion retail are simple: Which product is selling? Which size is missing where? In which store is stock building up? Which discount actually protects margin? When should we transfer? Which product should be shown online?
The simplicity of these questions is misleading. A sound answer requires product cards, locations, warehouses, prices, orders, sales and return records to speak with the same set of definitions. Reducing ERP to accounting or a till system means missing the core problem that determines decision quality.
The commercial meaning of moving to Nebim was to handle operations around a single language of measurement and responsibility. The critical distinction is this: transferring data into software is a technical task; institutionally defining which data counts as "the right data" is a management decision.
Data and Stock
Dirty data does not get cleaned when it moves into a new system; it simply circulates faster.
The backbone of the transformation: workflow first, screens second
The starting point of a good ERP transition is not the question "which module will we switch on?". First, the product's journey inside the company must be described:
Collection decision → product card → season / colour / size variant → purchasing / sourcing → central stock → allocation to stores → point of sale / digital channel → returns / exchanges → financial record → performance analysis.
When one link in this chain is defined differently, all the remaining reports may look correct yet be incomplete from a decision standpoint. In the Zeki Triko example, the transformation areas to be considered through Nebim are exactly these interconnected layers of the chain.
This framework is used not to overstate software features, but to connect ERP to the business model.
Product master data: model, colour, size and season must be one truth
In fashion retail a "product" is not a single line. A model's size and colour variants and its collection and season links change what the product means at each point of sale. When coding discipline is weak, transfers, stock counts, sales analysis and discount performance weaken too.
The first agenda of data governance therefore consists of: product hierarchy; variant definitions; season and collection tags; uniqueness of barcode / stock code; product statuses; category ownership; rights to create, correct and deactivate data.
Management lesson: Dirty data does not get cleaned when it moves into a new system; it simply circulates faster. Before an ERP project starts, the owner of the product dictionary must be clear.
Visibility between store and headquarters
The product physically present in a store and the quantity shown as "sellable stock" at headquarters are not always the same concept. Reserved items, items in transfer, count differences, items awaiting return and display items lead to different decisions. Reading store sales performance soundly depends on these distinctions.
That is why the store–warehouse–headquarters data relationship must define not only quantity but stock status, location, transaction time and responsibility. This approach gives the central team a more reliable basis for decisions and gives stores a clearer transaction discipline.
Stock allocation and transfer: reading demand, not just distributing product
A product moving slowly in one store may be missing stock that loses demand in another. A decision about the same model in the same season should not be taken without reading together the store profile, sales velocity, size breakdown, current stock, transfer cost and the remaining season.
This is where the commercial value of the ERP transformation becomes clear. A transfer should be seen not merely as a warehouse movement but as repositioning a potential sale. Yet not every transfer is right: consuming a low unit margin with a high transfer cost can increase the store's sales while reducing the company's profitability.
A usable decision matrix is therefore:
Demand: sales rhythm and size breakdown over the last 4 / 8 weeks.
Inventory: on-hand, in-transit, reserved and available stock.
Economics: product margin, transfer cost, estimated probability of sale.
Time: time left until season end, possibility of reordering.
Alternative: transfer, price decision, digital sale or hold?
These items are an explanatory management framework; they should not be presented as a software algorithm used one-to-one in the project or as realised decision records.
Store, Price and Channel
The real value of a KPI is not in the report but in the decision you take afterwards.
Translating store sales data into commercial language
Revenue alone does not tell how healthy a store is. Units, gross margin, conversion, average transaction value (ATV), units per transaction (UPT), sales per m² and like-for-like growth (LFL) should be monitored together for the same period.
The purpose of this measurement language is not to put stores into a single league table. Is a store's low performance caused by location, missing size distribution, pricing, window display or staff training? Data alone does not produce the answer; it makes sure the right question is asked.
Management lesson: The real value of a KPI is not in the report but in the decision you take afterwards. ERP turns into commercial value to the extent that it makes decisions visible and traceable.
Price, promotion and premium brand discipline
In a premium brand, a discount is not just a sales-boosting button. A wrong price hierarchy can create inconsistency between stores; excessive promotion can weaken the brand's long-term pricing power.
For this reason, in the relationship between ERP and commercial management, list price, campaign authority, end-of-season discounts, store-level differences and margin impact should be assessed within the same control framework. The store's daily target and the brand's medium-term positioning should not contradict each other.
The bridge between e-commerce and physical retail
When physical and digital sales rely on different stock and product truths, the customer experience becomes fragile. A product shown on a website but not actually available creates lost sales as well as costs in customer trust and operations.
When the e-commerce connection is addressed in an ERP programme, product information, stock availability, order status, returns, cancellations, sales channel and financial reconciliation must be assessed together. This is a commercial architecture problem that goes beyond the phrase "the website is connected to the ERP".
E-commerce and premium retail growth at Zeki Triko explain the strategic importance of this integrated view; however, this page does not claim that e-commerce growth happened directly because of the Nebim transition.
Authority matrix and responsibility design
A transformation needs owners of decisions as much as owners of software screens. Who opens a product card? Who approves a stock correction? Who owns transfers between stores? Who defines a price exception? Who closes a return discrepancy? At what point does finance reconcile?
If these questions are not answered, the company may technically move to a single system yet keep its old habits from a management perspective.
Example responsibility map: category and product teams own product master data; retail operations own the accuracy of store movements; finance owns the record–reconciliation relationship; IT owns system access and integration health; top management owns exceptions and the decision rhythm. This map is a proposed governance logic; it is not Zeki Triko's verified official organisation chart.
Management and Lessons
In retail, scale means decision quality does not drop as more stores open.
Change management: the most important integration is people
ERP transitions are often described in the language of data or software. Yet a transformation cannot be considered complete unless the daily behaviour of store staff, stock teams and managers deciding at headquarters changes.
Training should teach not only which key to press but the commercial reason behind the transaction. Why does a missing sales record break stock accuracy? Why does a delayed return show inventory wrongly? Why does a wrong size code lead to wrong product allocation? When users see this chain, compliance turns from an obligation into a shared responsibility.
Controlled validation instead of an uncontrolled "go-live"
A solid transition methodology should test product data, opening stocks, sales and return scenarios, store transfers, pricing rules, financial records, user authorisations and report reconciliation. If necessary, a pilot store, parallel reporting, a rollback plan and an issue-tracking system are run.
The items listed here are good-practice checkpoints. Since we do not have project minutes showing exactly which pilot, test scenario or transition schedule was used at Zeki Triko, no dates or details claimed to have been applied have been invented.
What does the transformation change at the management level?
A well-designed ERP programme aims at three fundamental behavioural changes:
One: Testing intuition with data. An experienced store manager's observation remains valuable; but it is evaluated together with stock, sales velocity and margin data.
Two: Separating local success from company success. If a store grows its own sales while reducing company margin through stock or discount effects, this must become visible.
Three: Not normalising the exception. Last-minute Excel corrections, off-system price lists and person-dependent workarounds should not become a permanent business model.
The real value of an ERP transformation is not producing more screens; it is being able to decide with less uncertainty.
Measurement model: how is real success proven?
For an ERP project to count as a "success", sales growth alone is not sufficient evidence. Indicators that can be measured in such a project include:
Stock accuracy rate: alignment between physical counts and the system.
In-stock availability: the requested size / variant being available at the relevant location.
Stock turnover: the pace at which held stock turns into sales.
Full-price sell-through: the share of products sold without discount.
Stock ageing: slow-moving inventory carried to season end.
Transfer efficiency: post-transfer sales relative to transfer cost.
Return and reconciliation differences: frequency of wrong records / closing delays.
Report production time: speed at which analysis reaches decision makers.
User adoption rate: transactions completed without leaving the process.
In the published case these indicators appear as measurement proposals; they are not measured project results for Zeki Triko. Exact before–after values can only be added from internal reports.
The commercial scale of the Zeki Triko period and separately measured achievements
Among the commercial performance highlights of Gökhan Akdağ's roughly 3.5-year management experience at Zeki Triko, previously shared, are an approximately 135% increase in like-for-like (LFL) store revenue and international premium retail expansion including Paris, Miami and Dubai. The career narrative also mentions around 25 premium store openings.
Important distinction: These belong to the broader commercial and brand development context of the management period. They are not presented as independent, causal and measured effects of the Nebim transition. No exact savings, staff productivity, stock reduction or return on investment (ROI) figure for the ERP project has been shared.
Why does this case still matter today?
Today ERP, POS, e-commerce, CRM and analytics platforms may be more advanced. But the fundamental question of the business has not changed: are store, product, customer and finance data turning into a shared decision system?
The leadership lesson drawn from the Nebim ERP transition at Zeki Triko is that retail technology must be handled together with operational discipline and brand strategy. A company that only changes its system moves data. A company that also develops its business rules, data ownership and way of deciding builds a scalable organisation.
Gökhan Akdağ's perspective
"For me, an ERP transformation is not a software purchasing story; it is about being able to connect the reality of the store to the board's decision. The right system is not the one that produces the most reports, but the one that makes the wrong decision visible earlier."
This statement is an editorial assessment written for this case text; it should not be presented as a historical interview quote.
Who can learn from this case?
This case is particularly relevant for multi-store fashion retailers, brands carrying season- and variant-based stock, management teams redesigning store–e-commerce integration, family businesses that want to protect data quality during growth and senior leaders who do not want to see the ERP decision merely as an IT project.
Final word: In retail, scale is not just a larger number of stores. Scale means decision quality does not drop as more stores open.
Related reading and contact
Related case: Lelas's Transition to SAP Systems
Frequently Asked Questions
Why was the move to Nebim ERP a strategic issue at Zeki Triko?
In fashion retail, product variants, stock, stores, sales and finance form the same decision chain. Moving to ERP requires rethinking this chain in terms of data consistency and management responsibility.
What is the most important criterion when choosing an ERP for fashion retail?
Not a single feature list, but overall fit with the business model: model–colour–size tracking, multi-location inventory, store operations, pricing rules, digital channel needs and reporting processes.
Is Nebim ERP used only for stock tracking?
No. According to Nebim's public product documentation, the solution family covers interconnected areas such as retail sales, channel management, store performance and stock processes. However, this general platform information does not show that all modules were used in the Zeki Triko project.
What are the biggest risks in an ERP transition?
Faulty product master data, unclear process ownership, insufficient user training, untested integrations and reducing project success measurement to a technical go-live.
How much did the move to Nebim ERP increase Zeki Triko's sales?
No project-specific causal sales increase or ROI figure has been publicly verified. Other commercial achievements of the management period are not presented as direct results of the ERP transition.
Why should ERP transformation be on the top management agenda?
ERP affects who trusts which data, who takes which decision and who takes responsibility. That makes it a matter of organisation and commercial management, not only technology.
More Works
©2026
FAQ
What does GA Consulting do?
What is your approach?
How do projects progress?
What is your focus?
Which areas do you work in?
What value does it create for companies?
Which companies is it right for?
How long until a project delivers results?