Purchase Order & Supplier Management

The Spreadsheet PO Is Costing You Money

I have watched sellers run $2M businesses with purchase orders stored in email threads. They forget to reorder. They order too much of the wrong SKU. They have no idea which supplier actually delivers on time and which one says "two weeks" but means five.

The problem is not that these sellers are disorganized. The problem is that creating a good purchase order requires information scattered across three or four systems: current stock levels, sales velocity, supplier lead times, MOQ rules, and whatever your last order looked like. Nobody can hold all of that in their head past about 30 SKUs.

ReplenishRadar pulls it together. Forecasts feed PO suggestions. Supplier rules shape the quantities. You review, approve, and send.

From Forecast to Purchase Order

Here is what the workflow actually looks like.

ReplenishRadar runs demand forecasts on every active SKU. When projected stock drops below your reorder point, accounting for lead time and safety stock, a PO suggestion appears. Not a vague "low stock" alert. A specific line item: this SKU, this quantity, this supplier, order by this date.

You can approve suggestions individually or batch them into a single PO per supplier. The system generates a PDF or Excel (XLSX) packet you can send to your vendor.

Every PO tracks through its full lifecycle: draft, approved, sent, in transit, received, closed. When goods arrive short, you create a backorder from the receiving screen. Supplier replies, quantity changes, and ship-date updates stay tied to the original PO lines instead of getting lost in email threads.

If you are migrating from Stocky or Inventory Planner, you can import open and historical POs from CSV. The importer previews the file before anything writes, preserves your existing PO numbers as the idempotency key, and records received quantities as history without moving stock.

Ordering Constraints That Actually Work

Real suppliers have rules. Minimum order quantities. Casepack sizes. Order multiples. Your supplier sells widgets in cases of 24, with a 10-case minimum. You need 197 units. What do you actually order?

Most sellers either under-order (and stock out) or over-order (and tie up cash). ReplenishRadar applies all constraints at once and rounds to the nearest valid quantity. Before you approve, you see a constraint preview showing exactly what changed and why.

Constraint	What It Does	Example
MOQ	Minimum units per order	Supplier requires 500+ units
Casepack	Units must ship in full cases	Cases of 24: order 192 or 216, not 200
Order multiple	Order in specific increments	Multiples of 50: order 200 or 250, not 197

All three can apply to the same SKU at the same time. The math gets non-trivial fast. That is precisely why you should not be doing it by hand. Read more about how ordering constraints work.

Cadence Ordering (Growth+)

Most inventory tools assume you can order from any supplier on any day. That is not how it works.

You order from Supplier A every other Tuesday because that is when their truck runs. Supplier B gets one PO per month because the freight cost only makes sense in bulk. Your FBA replenishment goes out every Friday.

Cadence ordering matches your real schedule. Set a rhythm per supplier, or confirm the rhythm ReplenishRadar infers from PO history, and the system builds a picklist for that window with enough inventory to cover demand until the next one. If demand is running hotter than the schedule allows, it warns you before the window closes. I used to do this with calendar reminders and a spreadsheet. It took half a day. Now it takes five minutes of reviewing what the system already calculated.

Supplier Scorecards

Your suppliers tell you their lead time is 21 days. Is it actually 21 days?

ReplenishRadar tracks every closed PO and builds a supplier scorecard from real data. You see on-time delivery rate, average lead time vs. stated lead time, and cost reliability across orders.

We had a supplier who quoted 14-day lead time for two years. The scorecard showed the actual average was 22 days with a standard deviation of 6. That gap was responsible for roughly $34,000 in emergency air freight over a single year because our safety stock calculations were using the wrong number.

The scorecard also stores contact info, purchasing rules, payment terms, and SKU-to-supplier mapping. One place for everything about a vendor instead of scattered across emails and notes apps.

Supplier Replies Stay on the PO

Send a secure supplier response link with the PO packet. The supplier can confirm quantities, propose ship dates, upload documents, and send changes without logging into ReplenishRadar. Your team still approves what gets applied, and accepted quantities stay attached to the original PO lines.

That matters when a supplier accepts 450 units on a 500-unit order. You can see exactly which lines changed, create a backorder for the shortage, and keep receiving tied to the PO you actually sent.

Match the PO, Receipt, and Vendor Bill

A PO is not finished when the supplier says yes. It is finished when the receipt and vendor bill agree with what you ordered.

ReplenishRadar records vendor bills and matches them against PO lines and receipt history. Price or quantity differences get flagged before payment, so a short shipment or invoice mismatch does not quietly become bad margin.

Landed Cost Tracking

The PO price is not your real cost. Freight, duties, insurance, and handling add up. ReplenishRadar tracks landed costs per SKU per PO, so your margin calculations reflect what you actually paid, not just the supplier invoice.

This matters more than most sellers realize. I have seen landed cost add 15-35% on top of supplier price for ocean freight from Asia. If your reorder decisions are based on supplier cost alone, you are working with wrong numbers.

Direct-to-FBA Purchase Orders

Some SKUs never touch your warehouse. They ship from your supplier straight to Amazon's fulfillment centers.

ReplenishRadar supports this with a direct-to-FBA option on any PO. The system factors in FBA receiving times when calculating order dates, so your supplier ships early enough for Amazon to process the inventory before you stock out.

POs and transfers stay separate. The supplier order answers "what are we buying from this vendor?" while the transfer or inbound plan answers "where does inventory need to move?" That separation keeps partial receipts, FBA send-ins, and warehouse replenishment from drifting into one brittle workflow.

Who This Is For

This solution fits sellers who place purchase orders at least twice a month and manage 50+ SKUs across one or more channels. If you are placing one PO a quarter, a spreadsheet is fine. If you are placing 20+ POs a month across five suppliers, you are spending hours on work that should take minutes.

The sweet spot: Shopify and Amazon sellers doing $500K to $10M in annual revenue who have outgrown spreadsheets but do not need a six-figure ERP.

Pricing

Standard - $99/mo

• 2 connected stores (Shopify, Amazon, or both)
• Up to 2,000 active SKUs
• 1,000 sales line items/month
• PO generation from demand forecasts
• Ordering constraints (MOQ, casepack, multiples)
• Full PO lifecycle tracking
• Real-time inventory updates

Growth - $199/mo

• 5 connected stores
• Up to 20,000 active SKUs
• 5,000 sales line items/month
• Cadence ordering per supplier
• Vendor workflows and supplier scorecards
• Real-time inventory updates

Scale - $499/mo

• 10 connected stores
• Up to 50,000 active SKUs
• 20,000 sales line items/month
• Owner Pulse AI digest
• Priority support
• Real-time inventory updates

All plans include a 14-day free trial. Start your trial

---

Related:

• Purchase Order Features - Full feature breakdown
• Supplier Scorecard - Vendor performance tracking
• How to Create a Purchase Order - Step-by-step guide
• Casepack, MOQ, and Order Multiples - Constraint math explained
• Compare ReplenishRadar to alternatives - See how we stack up