Enterprise manufacturing · Large-scale D365 rollout

Consolidating systems for a national consumer brand

An enterprise program to reduce fragmentation and create a shared view across the value chain.

Business transformation in context

Project story

At national scale, the challenge was not one CRM or one ERP feature. It was making channels, customers, warehouses, campaigns, and operations behave like one business.

The setting

A top-three Chinese baijiu group was growing across production bases, distributor networks, e-commerce channels, customer operations, finance, and data. The operating picture included thousands of distributors, millions of online customers, multiple distribution centers, and a business that could not afford to treat every channel as a separate world.

Why now

Growth had created overlapping systems, fragmented ownership, and inconsistent visibility across production, distribution, customer relationships, marketing, finance, and supply-chain activity.

The tension

The organization needed enterprise consistency without flattening the differences between B2B distribution, B2C commerce, customer insight, warehouse fulfillment, and equipment operations. Speed mattered, but so did inventory control, consent, traceability, and recoverability.

People in the system

Every project has more than one point of view.

Perspective

Distributor and channel teams

Reliable order, price, credit, availability, and fulfillment information for a wide network of partners.

Perspective

E-commerce, marketing, and customer service

A usable customer view across channels, with consent and campaign context that could support better decisions.

Perspective

Warehouse and fulfillment teams

Clear allocation, routing, reservation, batch, shipment, and exception handling across distribution centers.

Perspective

Finance, asset, and technology teams

Stable system boundaries, auditable data, controlled integration, and a platform that could be supported after go-live.

The journey

How the work moved from problem to practice.

01
Create one enterprise picture
The program brought the business landscape into one conversation: customer and channel operations, Customer Insights, F&O, Power BI, warehouse fulfillment, finance, and equipment-related work.
02
Make the order path resilient
B2B, B2C, and external-channel demand needed a common intake, validation, routing, reservation, status, and reconciliation story instead of a different interpretation in every channel.
03
Turn customer data into a decision asset
Identity, consent, segmentation, activation, and campaign results needed to remain connected so marketing could act on a customer view that was explainable rather than merely large.
04
Connect fulfillment to the real operation
Warehouse availability, safety stock, reservation, batch genealogy, shipment status, and exceptions had to stay grounded in the system of record rather than being solved by manual inventory edits.
05
Design for adoption at scale
UAT, role-based training, phased rollout, operational support, and hypercare connected the enterprise design to the people who had to use it every day.

Decisions that shaped it

The turning points were business decisions as much as system decisions.

Decision

Keep source-of-truth boundaries visible

Customer context, customer insight, inventory, fulfillment, finance, and analytics each needed a clear responsibility so integration did not become a second hidden database.

Decision

Treat recovery as part of the customer experience

Duplicate orders, delayed messages, reservation failures, and status disagreements needed idempotency, correlation, reconciliation, and controlled replay so the business could recover without guessing.

Decision

Use AI and automation as governed assistance

Recommendations could accelerate matching, segmentation, service, and exception handling, but high-impact identity, consent, inventory, budget, and release decisions still needed ownership and review.

Ways to read the work

The same project can reveal different kinds of value.

Business lens

Turn scale into a coordinated operating model

The project is about helping a large consumer business grow without allowing every channel, warehouse, or team to invent its own version of the customer and the order.

Delivery lens

Sequence the change so the enterprise can absorb it

The value came from linking discovery, design, data, testing, training, rollout, and hypercare into one delivery rhythm rather than treating go-live as the finish line.

Systems lens

Make complexity observable and recoverable

The architecture story is about boundaries, states, source-of-truth rules, traceability, and recovery paths that remain understandable when channels and volumes are moving at the same time.

What changed

Outcomes are easier to trust when the evidence is visible.

Enterprise scale

The story spans a national consumer brand, multiple production bases, large distributor and customer populations, multiple fulfillment locations, and both B2B and B2C operating models.

End-to-end view

The narrative connects order orchestration, customer identity, activation, warehouse fulfillment, data migration, testing, training, rollout, and hypercare.

Business outcome

Fewer fragmented systems, better supply-chain visibility, faster reporting, and a stronger foundation for coordinated customer and operational decisions.

Reflection

High-level transformation becomes believable when it can explain both the big picture and the moment an individual order, customer, batch, or alert needs attention.

Project notes

Details behind the story.

I helped bring different business functions into one transformation conversation: product, customer service, marketing, procurement, finance, supply chain, data, and adoption. The important work was making the enterprise visible as one connected operating system rather than a collection of departments and legacy tools.

Consolidating systems for a national consumer brand

At national scale, the challenge was not one CRM or one ERP feature. It was making channels, customers, warehouses, campaigns, and operations behave like one business.

Every project has more than one point of view.

Distributor and channel teams

E-commerce, marketing, and customer service

Warehouse and fulfillment teams

Finance, asset, and technology teams

How the work moved from problem to practice.

Create one enterprise picture

Make the order path resilient

Turn customer data into a decision asset

Connect fulfillment to the real operation

Design for adoption at scale

The turning points were business decisions as much as system decisions.

Keep source-of-truth boundaries visible

Treat recovery as part of the customer experience

Use AI and automation as governed assistance

The same project can reveal different kinds of value.

Turn scale into a coordinated operating model

Sequence the change so the enterprise can absorb it

Make complexity observable and recoverable

Outcomes are easier to trust when the evidence is visible.

Details behind the story.