Purchase orders

Stock dips below the reorder point. The PO is already drafted.

Open any supplier on the canvas to see every PO with that supplier in one place. Issue, receive, cancel. When inventory crosses a threshold, the bot drafts the next PO with the preferred supplier so you only have to hit Issue.

Supplier
Mouser Electronics
Purchase orders
+ New PO
  • PO-2026-00042
    Issued May 18 · expects May 27
    Issued
  • PO-2026-00038
    Issued May 10 · 60/100 received
    Partial
  • PO-2026-00033
    Received May 5 · stock updated
    Received
PO-2026-00038
USD 1,247.50
ATmega328P100 ea
Receive now40
Stock updated: ATmega328P 60 → 100 on hand

How it works

Drafted in the background

A daily reorder pass looks for inventory where Available (on-hand + on-order minus allocated) is below the reorder point. For each shortage it picks the preferred supplier, calculates quantity (reorder × 1.5 minus on-hand), and writes a draft PO you can find in the supplier node on the canvas.

You see a single workspace observation in the AI sidebar listing every supplier that needs an action today. No noise, no "your inventory changed" pings.

Issue, then receive (partial is fine)

Hit Issue. The bot allocates a PO number, flips the status, and the supplier email is yours to send (or pipe through the AI sidebar to draft on prior-thread context).

When the shipment arrives you enter received quantities per line, optionally with notes about damage or quality. Stock movements post immediately, on-hand updates, and downstream shortages clear. Receive less than ordered? The PO drops into Partially received and stays open until the rest lands.

Open one place, all the history

The supplier modal lists every PO you've cut to that vendor, with status badges and dates. Click any to see the lines, what's outstanding, and the receive flow. No separate POs screen to navigate to and back.

The same modal carries your TuringDock Payments savings panel, so when you go to pay this PO the cheaper international rate is one click away.

Why this is the new age of MRP

Legacy MRPs make purchase orders a separate module: a list view, a builder wizard, a receive workflow, a separate stock posting step. Five clicks before you've done anything.

TuringDock keeps POs on the canvas, attached to the supplier they belong to. The bot drafts them so a quiet day means you only review and issue. Receipts are one screen and stock updates in the same transaction.

Build what's next. Leave the MRPing to our AI.

Build what's next.

Leave the MRPing to our AI. Sign up free, set your shop up in an afternoon.

Get started for free

Common questions

Does TuringDock auto-draft purchase orders?
Yes. When any component crosses its reorder point, Alan drafts the next PO at the forecast quantity (weighted moving average + linear trend over 12 weeks of shipment history × lead time × 1.5 buffer), addressed to the preferred supplier with the latest unit price. You tap Issue and the supplier email goes out in your name with the PO PDF attached. Most reorder workflows go from 'noticed it's low' to 'PO sent' in under 60 seconds.
Can I issue POs by email to suppliers who don't have a portal?
Yes. The default issue flow renders a branded PDF (your accent color, legal name, tax line, supplier address, line items, totals, terms) and emails it to the supplier contact on file. The body is auto-drafted in your voice. The outbound message logs to the supplier thread so the next reply picks up the full conversation. No supplier portal required.
How does receiving partial shipments work?
Open the PO, hit Receive, enter the quantities that arrived. Stock movements post atomically in the same transaction; on-hand updates instantly across the canvas and any in-progress production task that consumes this component reflects the new availability. Multiple receipts against the same PO are supported until the PO is fully received or cancelled.
Does TuringDock integrate with Digi-Key, Mouser, McMaster-Carr?
Direct API integration for live inventory checks and programmatic PO submission is on the premium tier (currently in public beta with the first customers). Free tier handles every PO workflow via email-issued POs and manual receipt entry, which works for any supplier whether or not they have a public API.
Where does the PO number come from?
TuringDock auto-assigns per-workspace per-year sequential numbers (e.g., SPO-2026-00031). The format is fixed; the number is reserved when the PO is first drafted so the reference is stable even if you discard the draft and create a new one.

Last updated 2026-05-23