> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What Is a Good Way to Handle Customer Change Requests During Production?
- URL: https://blog.jestor.com/customer-change-requests-during-production/
- Published: 2026-10-13T21:19:48.000Z
- Updated: 2026-10-13T21:19:48.000Z
- Author: Bruno Bannach

A good way to **handle customer change requests during production** is to record every request on the order, assess its impact on materials, cost and delivery date, get internal and customer approval for any price or date change and update the production order only after approval.

In **Jestor**, change requests are linked to the order, with a full history of what changed and why.

## Why are mid-production changes risky?

Customers change dimensions, colors or quantities after production has started. Changes arrive by phone and are passed on verbally.

Some changes are applied to the wrong stage, others are forgotten, and extra costs are not charged.

Delivery dates slip without the customer understanding why.

## What problems does a change process solve?

- Changes applied incorrectly or forgotten
- Extra costs not charged
- Delivery dates changed without agreement
- Materials wasted on outdated specifications
- Disputes about what was ordered

## How do I handle change requests in Jestor?

1. **Record the change request** on the production order.
2. **Assess impact**: materials, labor, cost and delivery date.
3. **Approve internally**, with value limits for price changes.
4. **Send the new price and date** to the customer for approval.
5. **Update the order and BOM** and notify production.

| Impact    | Question                           |
| --------- | ---------------------------------- |
| Materials | Are materials already cut or used? |
| Cost      | What is the extra cost?            |
| Schedule  | How does the delivery date change? |
| Quality   | Do checks need updating?           |

## How do I protect production from confusion?

Production sees only the approved version of the order.

When a change is approved, an automation can notify the affected stations.

## Why use Jestor for change requests?

- **Linked to orders**: every change in context.
- **Impact fields**: cost and date changes recorded.
- **Approvals**: internal and customer decisions documented.
- **Notifications**: production informed of approved changes.

## What else helps you handle customer change requests during production?

- Tracking how many orders change mid-production also shows whether quoting or specification steps need improvement.
- Clear rules help customers too. Explaining in the quote when changes are still possible and how they affect price and dates reduces late requests.
- Recording each change also helps sales understand which customers change orders most often.

This is how you handle customer change requests during production without chaos.

## Frequently Asked Questions

### Can customers approve changes online?

Yes. A form or link can record the customer's approval.

### Where can I learn more?

Visit [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) to try Jestor free or talk to the team.

### Can price changes require approval?

Yes. Approval steps can route changes above a limit to a manager.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**.

Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.