SupplyTetherBook a call

AI procurement for U.S. industrial manufacturers

One late part can hold up your whole production line.

Your buyers shouldn't spend the day chasing suppliers and updating spreadsheets. We're building an AI procurement agent that follows up on purchase orders, keeps Oracle current, and helps your team act before parts arrive late.

Book a callSee the workflow

In development

Open purchase ordersIllustrative workflow

  • PO 10479 · HX-1180

    M10 hex flange bolt

    On track

  • PO 10482 · BRG-6205

    6205-2RS bearing

    3 days late

  • PO 10485 · GSK-0430

    Pump housing gasket

    No acknowledgment

PO 10482 slipped past the production need date

ERP update preparedSupplier follow-up draftedBackup source to review
Illustrative example with fictional purchase orders. Not live data.

Your inbox changes. Your production plan falls behind.

01

Supplier updates get buried

A new ship date arrives in an email or a PDF. The ERP still shows the old one, so the plan looks fine until it isn't.

02

The same data gets typed twice

Buyers copy dates, quantities, and prices from supplier messages into Oracle and spreadsheets, one line at a time.

03

Replacements get sourced last minute

When a shortage shows up late, the team scrambles to find another supplier while the line waits.

From supplier update to a clear next step.

One supplier email moves a ship date by a week. Here is what SupplyTether is designed to do with it.

  1. 01

    Read the update

    Pull the PO number, part, quantity, and new date out of the supplier email.

  2. 02

    Match the order

    Find the purchase order line and compare the new date to when production needs the part.

  3. 03

    Flag the gap

    Show that parts now land three days late, with the source email attached.

  4. 04

    Prepare next steps

    Draft the ERP date change, a supplier follow-up, and a backup source for your buyer to review.

Illustrative workflow

Example data with fictional suppliers. Nothing here is sent or connected.

01Supplier email

Harlow Bearing Supply

Dana Pruitt · orders@harlowbearing.example

Re: PO 10482 ship date

Nov 3, 9:14 AM

Hi Alex, quick update on PO 10482. Our heat treat vendor is behind, so the 500 pcs of BRG-6205 will now ship November 19 instead of November 12. Pricing is unchanged. Sorry for the trouble.

PO
10482
Part
BRG-6205
Quantity
500 EA
New ship date
Nov 19

02Purchase order match

PO 10482 · Line 1

BRG-6205, 500 EA

Purchase order values compared with the supplier update
FieldERP todaySupplier says
Promised dateNov 12Nov 19changed
Quantity500 EA500 EAmatch
Unit price$4.85$4.85match

Schedule conflict, 3 days

Production needs this part Nov 16. The new ship date puts it 3 days late. No inventory buffer in this simplified example.

03Activity

  1. Supplier update read

    Email from Harlow Bearing Supply

  2. Purchase order matched

    PO 10482, line 1, BRG-6205

  3. Schedule conflict found

    Arrives Nov 19, needed Nov 16

  4. ERP update prepared

    Promised date change, awaiting approval

  5. Backup source proposed

    Availability unconfirmed

For buyer review

Drafts for PO 10482

Example only. Nothing is sent and no ERP is connected.

Prepared change to the purchase order shipment, waiting for buyer approval.

Purchase order
10482
Line / shipment
1 / 1
Item
BRG-6205
Promised date
Nov 12 → Nov 19
Source
Supplier email, Nov 3, 9:14 AM

In the product, a buyer edits or approves each draft before anything goes to a supplier or the ERP.

What we're building.

Six parts of one purchasing workflow, in development now.

  • Chase fewer confirmations

    Follow up on missing purchase order acknowledgments and delivery updates.

  • Keep purchasing records current

    Match supplier changes to order lines and prepare ERP updates.

  • Plan around real lead times

    Compare production demand, inventory, and open orders to surface material gaps.

  • See delays sooner

    Flag overdue responses and changed dates that threaten the production schedule.

  • Find a backup source

    Compare exact parts and potential equivalents from alternate suppliers for review.

  • Keep supplier history in one place

    Bring delivery, pricing, and quality records into the next buying decision.

Built around the systems your buyers already use.

SupplyTether is designed to read your purchasing inbox and supplier documents, then check them against open purchase orders in your ERP. Oracle is our first integration focus. Every setup is different, so we start by learning yours.

  • Buyers review exceptions before anything changes.
  • Supplier emails and ERP updates wait for approval.
  • Equivalent parts go to engineering or quality review. Nothing is substituted silently.
Talk to us about your Oracle setup

Purchasing inbox

Supplier emails and replies

Supplier documents

PDFs, spreadsheets, acknowledgments

SupplyTether

Reads, matches, flags, and drafts

Buyer approval

Review exceptions and approve changes

Oracle ERP

Purchase order updates

Intended design. Integration details depend on your Oracle setup.

Built from experience inside industrial operations.

SupplyTether is founded by Benjamin Thuroczy, an Industrial and Systems Engineering student at Ohio State graduating in December 2026, with a focus on data analytics and optimization.

He has worked in supply chain at GE Aerospace and in engineering at Swagelok, consulted for industrial manufacturing clients, and interned as a software engineer at JPMorgan. He has worked the purchasing workflow firsthand and is building the tool he wanted on the job.

Where does your purchasing process get stuck?

Walk us through how your team tracks purchase orders, follows up with suppliers, and handles late parts.

Book a call

Sales sales@supplytether.com

General info@supplytether.com