- 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.