Prototype case study

A pricing exception, corrected before approval.

A walkthrough of the public order demo, with its tested behaviour and current integration limits.

The problem

An incoming order can contain a valid product at the wrong price. Extracting its fields successfully is not sufficient: a system needs to check authoritative business rules and give a reviewer a clear path to correction.

The observed walkthrough

In the fixed price-mismatch scenario, WIDGET-A appeared at EUR 5.00 against an agreed EUR 25.00 price. Changing it to EUR 25.00 and rerunning checks created revision 2. Four units plus two CABLE-B units at EUR 12.00 produced a EUR 124.00 total. Human approval then returned a simulated order reference.

Pipeline and architecture

Input → extraction → validation → review → approval → result. The React/Next.js interface calls a Python/FastAPI order backend through a scoped API proxy. Application records use PostgreSQL/Supabase. Fixed scenarios skip file reading and AI extraction explicitly; PDF processing is a separate path.

What was verified

The September 2026 desktop walkthrough exercised the price exception, correction, revalidation and simulated approval. Repository tests also cover API proxy path restrictions and exact-origin checks. This walkthrough was not a load test or a verification of real ERP connectivity, PDF extraction accuracy or customer delivery.

What remains simulated

The ERP catalogue, stock reservation, Dynamics adapter and customer-confirmation preview are demonstration components. No real ERP order or customer email is created. Duplicate-protection behaviour needs its own test; a saved-order message alone is not proof of idempotency under failures.

From this prototype to your operation

A paid pilot would replace agreed simulation boundaries with your sandbox APIs, validate representative orders, test retries and record acceptance results. Scope the input channel, ERP and review rules before committing to a production rollout.

Start with a scoped pilot.

Discuss your inputs, acceptance criteria and integration access before agreeing on delivery and price.

Discuss your project →