Skip to content
BYC Data & Performance

Leggerini gravure, stone engraving workshop

The purchase order received by email becomes an order

Every purchase order received by email, as a PDF or a photo, becomes an order in the workshop's application, attachments included.

Testimonial
1 review on Malt

Context

The workshop receives its purchase orders by email, as PDFs or photos, from several agencies. Every order has to go into the workshop's application.

The problem

A first automation filtered emails on a word in the subject. Invoices and bank details slipped through: fake orders. Purchase orders scanned as photos were discarded. An email with two PDFs created two orders. And one morning, a failure lost an order, which had to be retyped by hand.

In seventeen days: 490 emails with attachments, 42 picked up by the keyword.

What we built

A single automation, and one rule: one email, one order.

  • An AI model reads the attachments. It answers in a structured way: purchase order or not, then the order details.
  • All the attachments are linked to the order and copied to the archive.
  • A likely duplicate (same name within ninety days) is flagged without blocking.
  • Unrecognized files are set aside quietly. Anomalies go to the workshop's contact address, failures to the consultant.
  • Before go-live, a test mode replayed twelve real cases, without writing anything.

The AI model is an outside service, named and chosen with the client.

Result

In service since 8 October 2026. One email, one order, attachments included. No order is lost on a failure anymore.

5.0 / 5 · 7 reviews on Malt

What the client says

  • Bene listened carefully to my automation project. He presented a clear, structured approach, with a precise step-by-step schedule. He took all my business constraints and all my requests into account, without ever trying to force a one-size-fits-all solution.

    Translated from French

    Jordan Managing director, Leggerini gravure, stone engraving workshop
For your IT team: Power Automate, SharePoint, OneDrive, Outlook, AI model (document reading)
  • Hosting: inside your Microsoft 365. If an outside tool is useful, it is named and you decide.
  • Accounts: a service account of your own for the automations.
  • Permissions: inherited from your Microsoft 365 groups, nothing separate to maintain.
  • Licenses: announced before we start, with the exact cost.
  • Handover: documentation, user guide, quick reference; no proprietary code.

A process that costs you too much? An Excel file that has outgrown itself? A team losing time?

Describe it in five lines. Reply within 24 h with a costed estimate.