Reference · built on requestOperator by FibricInventory & supply

Purchase Order Draft

Drafts purchase orders from reorder triggers, open POs, vendor minimums and pack sizes. A buyer approves before anything is sent.

Request accessPricing ↗

About

A reorder trigger says what is short. It does not say how much to buy, from whom, or whether it is already on order. Purchase Order Draft reads the items at or below reorder point, the open purchase orders for the same items, and the vendor minimums, pack sizes, and order multiples held on the item record or in the buyer's spreadsheet.

It groups the shortfalls by vendor, rounds quantities to the terms, checks for stock already on order, and proposes one draft per vendor. The buyer reviews the lines and the requested receipt date and approves. Only then is a draft purchase order created in your ERP, still unsent, for the buyer to release.

This is a reference listing. It documents what Fibric would read from Purchase Order Draft and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Items at or below reorder point, from NetSuite's Reorder Point Items list or from Business Central planning parameters
  • Open purchase orders and lines with quantity and receivedQuantity in Business Central, so stock already on order is counted
  • Vendor minimums, pack sizes, and price breaks kept in a Google Sheet or Excel workbook you point it at
  • Order modifiers on the Business Central Item Card: Minimum Order Quantity, Maximum Order Quantity, Order Multiple
  • NetSuite item Reorder Multiple and Preferred Stock Level per location
  • Katana purchase orders in NOT_RECEIVED or PARTIALLY_RECEIVED status with their expected_arrival_date

Proposed actions

  • Target capability: propose a purchase order draft per vendor with lines, quantities rounded to pack size, and a requested receipt date
  • Target capability: propose adding a line to an open purchase order for the same vendor instead of opening a second one
  • Target capability: propose a quantity raised to the vendor minimum, shown against the quantity the reorder point called for
  • Target capability: propose creating the approved draft as a Business Central purchaseOrder in Draft status or a NetSuite purchaseOrder record

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Turn the reorder list into vendor drafts

    NetSuite items below reorder point are grouped by vendor and rounded to Reorder Multiple, with minimums from the buyer's Google Sheet. The buyer approves each draft and a purchaseOrder record is created.

    With NetSuite, Google Sheets

  • Respect case packs from the buyer's workbook

    Case packs and minimums in an Excel workbook are applied to Business Central shortfalls. The approved draft lands as a purchaseOrder in Draft status with a requestedReceiptDate.

    With Microsoft Excel, Microsoft Dynamics 365 Business Central

  • Add to an open order instead of a new one

    A Katana purchase order for the same supplier is still NOT_RECEIVED. Adding a row to it is proposed instead of a second order, and the buyer decides.

    With Katana Cloud Inventory, Cin7 Core

Requirements

  • An ERP or inventory system with purchase orders: Business Central, NetSuite, Katana, Cin7 Core, or Fishbowl Advanced
  • Reorder points or a replenishment list per item and location, held in that system
  • Vendor minimums and pack sizes, on the vendor or item record or in a spreadsheet with one row per vendor and SKU
  • A buyer named to approve every draft before it is released
Authentication
ERP credentials able to create purchase orders (a Business Central OAuth app, a NetSuite REST integration, or a Katana API key), plus read access to the sheet that holds vendor terms.

Limits

  • The draft is created in your ERP. Releasing or emailing it to the vendor is a step the buyer takes there.
  • A SKU with no vendor on record is listed for the buyer to assign. No vendor is guessed.
  • Vendor terms are read as the sheet holds them. A stale row produces a stale minimum.
  • It does not negotiate price. Unit cost is what the item or vendor record carries.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Purchase Order Draft ↗

Questions and answers

What exactly does the buyer approve?
One draft per vendor: the lines, the quantity the reorder point called for and the quantity after minimums and pack sizes, the unit cost on file, and the requested receipt date. The buyer can edit lines, split the order, or decline. Approval creates the draft in your ERP.
Can it send a purchase order to a vendor?
No. It creates a draft record, for example a Business Central purchaseOrder in Draft status. Releasing it or sending it to the vendor is done by the buyer in the ERP.
What is written down?
A receipt per draft: the trigger that started it, the open orders it checked, the vendor terms it applied, the quantities before and after rounding, who approved it, and the ERP record number. The receipt states how to delete or void the draft.
Ask about Purchase Order Draft

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy