Demand changed. Who can amend the plant’s purchase commitments?

HQ changes demand while a Slovak plant holds purchase commitments. Clarify who can amend them, what must be agreed and how cash effects are evidenced.

Taraf 205

The ERP milestone is marked complete. What is the business actually accepting?

ERP deliverable acceptance rests on agreed scope and test evidence, not a milestone report. Confirm who holds authority to sign before you do.

Beko Poland plant closure: what the Łódź and Wrocław wind-down asks of Group leadership

Beko Poland plant closure: how the Łódź and Wrocław wind-down tests delivery, people and governance, and what Boards should establish first.

An ERP change looks small. Who approves its effect on cost and launch?

ERP scope change control gives the sponsor one view of cost, testing and launch effect before a small request is approved. Four options, one record.

The group ERP template is approved. Which Czech plant exceptions are justified?

ERP global template local requirements: separate necessary Czech-plant exceptions from preference, and decide who validates and rules on each one.

Your Polish plant has an ERP launch date. What would justify going live?

ERP go-live readiness depends on evidence from the plant. See what a Polish plant must show before a sponsor approves, postpones or narrows a launch.

Your Slovak plant is live. Is it ready for the ERP launch team to leave?

Before the ERP launch team leaves a Slovak plant, confirm support ownership, unresolved issues, tested escalation and the exit the group is choosing.

One ERP site is live. What must change before the next country starts?

A first ERP launch does not approve the next country. Check transferable lessons, local conditions and shared specialist capacity first.

The Czech plant needs a new supplier. German HQ controls the decision.

A Czech plant has a replacement supplier ready. German HQ controls the emergency sourcing manufacturing decision: who should approve it, and within what limits?