Vendor & Purchase Order Management That Keeps Your Supply Chain Tight

Vendor management tracks every supplier relationship alongside your inventory and orders in one system - purchase orders, receiving against those POs, vendor product catalogs with vendor-specific SKUs and pricing, lead times, and performance history. Without it, vendor relationships live in email chains, spreadsheets, and phone calls with no audit trail and no data to drive better purchasing decisions.

The connection to inventory is direct: your vendors supply the products you sell. When vendor management lives in a separate system from inventory and orders, the data that should inform purchasing decisions (what's selling fast, what's running low, which vendor delivers on time) is disconnected from the data that triggers those decisions. SkuNexus links every PO to its vendor, tracks scan-verified receiving against ordered quantities, maintains a full product catalog per vendor with SKU mapping, and connects reorder triggers directly to PO creation so the purchasing workflow is continuous and data-driven.

You create a PO specifying the vendor, products, quantities, costs, and expected delivery date. The system tracks the PO through its full lifecycle: created > sent to vendor > in transit > partially received > fully received > closed. As items arrive at your warehouse, your team scans them against the PO line items, and the system updates quantities received versus not received in real time.

Partial receiving is critical because vendors rarely deliver everything at once. A PO for 500 units might arrive in three shipments over two weeks. Your system needs to track how many units arrived in each shipment, reconcile against the ordered quantity, and flag discrepancies (short shipments, wrong items, damaged goods). SkuNexus supports scan-verified partial receiving - your team scans each item as it arrives, the system matches it against the PO, and you always know exactly what's been received, what's still outstanding, and what came in wrong.

Yes. You set a minimum stock threshold per product - either a simple quantity or a calculated value based on sales velocity and vendor lead time - and when inventory drops below that level, the system either alerts your purchasing team or auto-generates a purchase order to the assigned vendor. This prevents the reactive scramble of discovering you're out of stock when a customer order can't be fulfilled.

The difference between basic and smart reorder points is the calculation behind the threshold. Basic: reorder when stock drops below 50 units. Smart: reorder when stock drops below (average daily sales x vendor lead time in days) + safety buffer. The smart approach accounts for how fast you're selling and how long the vendor takes to deliver, so the PO arrives before you run out. SkuNexus connects reorder triggers directly to PO creation with vendor, product, and quantity pre-populated, so the workflow from trigger to purchase order is continuous.

A vendor product catalog maps each vendor to the products they supply, including the vendor's own SKU numbers, their pricing, minimum order quantities, and lead times. This means when you need to reorder Product A, the system already knows which vendor supplies it, what they call it in their system, at what price, how many you need to order minimum, and how long delivery takes.

This mapping is essential for two reasons. First, your internal SKU and the vendor's SKU are often different - without the mapping, someone has to look up the vendor's product code every time they create a PO. Second, when you have multiple vendors who can supply the same product, the catalog lets you compare pricing, lead times, and performance data to choose the best option. SkuNexus maintains a full product-level catalog per vendor with vendor SKU mapping, so PO creation pulls the right vendor product codes, pricing, and quantities automatically.

Dropship vendor management automates the workflow when a vendor ships directly to your customer instead of sending inventory to your warehouse. When an order is routed to a dropship vendor through the Auto-Decision Engine, the system generates and sends the vendor a PO or notification with the customer's shipping address and order details. The vendor ships directly and provides tracking, which pushes back to the customer through the sales channel.

The challenge with dropship is that one platform couldn't handle leaving dropship items alone during fulfillment - it kept trying to adjust inventory for items the merchant never physically stocked. This is a common frustration: systems built for warehouse fulfillment that bolt on dropship as an afterthought. SkuNexus treats dropship as a native fulfillment path at the line-item level, routing dropship items through the Auto-Decision Engine alongside warehouse and store pickup items on the same order.

Track vendors by measuring on-time delivery rate (did the shipment arrive when promised), fill rate (what percentage of the ordered quantity was actually delivered), lead time accuracy (how does actual delivery time compare to quoted lead time), and defect rate (what percentage of received items fail inspection). These four metrics tell you whether a vendor is reliable and getting better or worse over time.

The data has to come from your actual receiving records, not from the vendor's self-reported metrics. Every time your warehouse team receives against a PO - scanning items, comparing quantities, noting discrepancies - those events generate the data that feeds vendor scorecards. SkuNexus records every PO lifecycle event from creation through scan-verified receiving, giving you the raw data to measure vendor performance objectively and hold suppliers accountable with facts rather than gut feelings.

Yes. PO data - vendor, line items, quantities, costs, receiving dates, and payment terms - should flow directly to your accounting system so purchasing and accounts payable stay aligned without manual journal entries or duplicate data entry. When a PO is received in the warehouse, the inventory asset value in your accounting system should update automatically.

The alternative is manual reconciliation: someone receives inventory in the WMS, then logs into the accounting system and enters the same data again. This creates lag, introduces transcription errors, and means your financial records are always slightly behind operational reality. SkuNexus integrates with QuickBooks and other accounting platforms so PO data, COGS, and inventory valuation sync natively. The event happens once in SkuNexus - receiving a PO, shipping an order, adjusting inventory - and the financial record updates in your accounting system without a second touch.