The customer changes the order after release. AUVY carries it into engineering and production.
A customer change after design release tends to reach production late, and then the extra cost stays with you. AUVY follows each order from release to acceptance, shows what a changed specification or a late supplier means for design, purchasing and delivery, and drafts the change request for the project manager to sign off.
← Use casesFor: Owners, project managers, design and production engineering, purchasing, service
Machine building & engineer-to-order
A week on a customer order.
After release, the customer asks sales by mail for a different conveyor height. A supplier confirms a drive two weeks late in a PDF that nobody links to the assembly date.
Use cases
What comes in, and what AUVY does with it.
- When
The customer asks for a different conveyor height after release.
AUVYMarks the change against the order specification and names the drawings, parts and dates it touches.
You getA change request for the customer to approve by link, with the price and date effect for you to fill in, and tasks for design and purchasing.
Reads Mail · Order specification · Part list export
- When
A supplier confirms a later delivery date.
AUVYCompares the confirmation with the date you ordered and shows which assembly step and customer date depend on it.
You getThe risk visible early, with a task and a note to the customer drafted.
Reads Supplier confirmation · Order · Plan
- When
Engineering releases a new revision of an assembly.
AUVYNames what changed since the last revision and whether production is still working from the old one.
You getProduction informed with the source attached, before the wrong part is made.
Reads Revision exports · Production plan
- When
The customer's acceptance test is next week.
AUVYLists every change agreed since the order, with its status and sources.
You getAn acceptance where every deviation is explained.
Reads Change requests · Specification · Mails
Sources
Every answer shows its work.
Before a partner puts an answer in front of a client, they want to know where it came from. In AUVY that takes one click.
What did we agree about the Munich site?
The client added Munich as a third site on 12 March.1 It is covered in the revised offer, section 4.2
2 of 3 sentences have a sourceNo source: “The workshop date is still open.”
- 4 Scope, phase 2
- 4.1 Munich is added as a third site,
- as requested by the client on 12 March.
- 4.2 One workshop and two site visits.
- 4.3 Dates follow the revised plan.
Meetings
Order kick-off, design reviews, acceptance.
Rules
How AUVY fits the way your trade works.
- Your ERP stays the system of record
- AUVY reads the exports and documents you give the project and writes nothing to your ERP or PLM.
- The order as sold is the baseline
- Changes are checked against the specification you gave the project, so every deviation is priced or given away on purpose.
- Customer approval by link
- The customer approves a change request from a link, without an account, and the answer is recorded with the order.
At a glance
- Walkthrough
- 40 minutes on one of your own projects, free.
- Price
- €59 per person a month, billed yearly, with every project, team and bot included.
- Your data
- Stored on our own servers in Helsinki, never used to train AI, and deleted within 30 days after the contract ends.
- Contract
- Every order includes the data processing agreement under Art. 28 GDPR, German text binding.
- Checked
Questions
Does AUVY connect to our ERP?
Not directly. It reads the exports, part lists and documents you give the project, and your ERP remains the system of record.
What counts as a change?
A relevant change in the sources you connected: a new requirement, a moved date, a changed quantity or revision. AUVY marks it where it arrived and shows what it affects.
Can AUVY track supplier delivery dates?
It reads the supplier confirmations you give the project, compares them with what you ordered and shows which steps depend on each date.
Also read



