Contact Book a call

Distribution · Customer story

Emailed RFQs read by AI and matched to SAP parts for an industrial distributor.

An enquiry platform for an industrial parts distributor that reads emailed RFQs with AI, matches parts against the item master, and works with SAP from enquiry to order.

Client
Revotec
Industry
Distribution
What we built
Enquiry and quotation platform on SAP
Built with
OpenAI
Enquiry and quotation platform on SAP for a revotec: Email RFQs read automatically

The results

In short

Revotec receives requests for quotation by email in every format. SBD built an enquiry platform that reads each RFQ with AI, matches requested parts against the SAP item master, and tracks each enquiry through to order. A review queue for uncertain matches is the next phase.

Before and after

What changed for the team.

BeforeAfter
RFQs read and re-typed from emailRFQs read automatically from email
Part numbers looked up by hand against the item masterParts matched to the SAP item master
Enquiry status tracked in inboxesEvery enquiry tracked through to order
Quotations built manuallyQuotations built from matched parts

How we did it

How the enquiry and quotation platform on sap was built.

  1. 1Read the inbox

    Emailed RFQs ingested and read by an AI step, whatever the format.

  2. 2Match the parts

    Requested items matched against the item master, including bearing part numbers in their many written forms.

  3. 3Connect SAP

    The platform works with SAP so enquiries and orders stay in the system of record.

  4. 4Extend

    Attachment parsing, spreadsheet quotations and a review queue proposed as the next phase.

The workflows

What runs now, and what sets it off.

  1. 01
    RFQ ingest

    When an RFQ email arrives

    Then

    Read by AI, items extracted

  2. 02
    Part matching

    When items are extracted

    Then

    Matched to the SAP item master

  3. 03
    Enquiry tracking

    When an enquiry changes stage

    Then

    Status updated through to order

Built with

The tools behind it.

Every account was created in the client's name.

What made it work

Matching against the item master the business already trusts, rather than a new catalogue.

What comes next

  • Attachment parsing
  • Quotations generated as spreadsheets
  • Offers entered into SAP
  • A review queue for uncertain matches

For distribution and logistics teams

Stock, orders and deliveries that agree.

The same pattern, built around your tools. Bring the one workflow your team still runs by hand and we will show you what this would look like for you.

Follow one delivery with us
A courier loading boxes into a delivery van outside a warehouse
Distribution and logistics Photo: Tima Miroshnichenko, Pexels.

Where this applies

The solutions this story proves.

How it starts

Every story on this page started with an audit.

One to two weeks. We map the work your team still does by hand, put an hours-a-week figure on each piece, and give you a costed blueprint in order of payback. The $500 is credited in full to the build.

  • Week 1 to 2Audit with the people who do the work.
  • Week 3Blueprint: fixed scope, fixed price, first build chosen by payback.
  • Week 4 onTwo-week sprints, working software every second Friday.
  • After go-liveSixty days of hypercare. Accounts and code in your name.

More customer stories