Skip to content
Case study

How our own team runs purchasing on BuyCast.

BuyCast was built inside an Amazon business and still runs its replenishment. This is that operation’s workflow, before and after, with the parts we still do by hand.

Our own operation · Internal case study

This is not a customer story. The operation described here is run by the people who build BuyCast. We publish it because it is the most honest account we can give of how the product is used every week. Screenshots are from the fictional demo tenant, not the live operation. Customer case studies will appear here as customers agree to be named.

The operation

Recurring replenishment, the same SKUs every week.

Wholesale Amazon FBA. The buying problem is not discovering products; it is deciding, every week, how much of each existing SKU to reorder from each supplier, and when.

Catalog

Hundreds of SKUs

Suppliers

Recurring replenishment

Purchasing team

A small team

On BuyCast

Since before launch

The workflow

Before and after, step by step.

The four steps in the homepage walkthrough are the four steps our buyer takes. Here is what each looked like before the product existed.

Deciding what to review

Before

A weekly export from Seller Central into a spreadsheet, sorted by days of cover. Anything the formula missed stayed missed until it stocked out.

Now

The overview flags SKUs for a decision using days of cover, velocity change, and forecast disagreement. The buyer works the list instead of building it.

Checking what is already on order

Before

PO history lived in email threads and a second spreadsheet. Double-ordering happened when someone forgot a PO was in transit.

Now

Every open PO and work order sits beside the SKU it is for, with expected arrival and receiving status. Nothing is ordered without seeing what is on the way.

Sizing the order

Before

A reorder formula nobody fully trusted, adjusted by gut. Forecast accuracy was never measured, so nobody knew when to trust it.

Now

A suggested quantity with its inputs shown and the forecast’s track record on that SKU. The buyer adjusts where the accuracy is low and leans on it where it is high.

Closing the loop

Before

Receiving updated inventory but not cost. Bills were re-keyed into QuickBooks at month end from the PO spreadsheet.

Now

Receiving posts against the PO, landed cost updates on the SKU, and the vendor bill lands in QuickBooks automatically. Settlements post as balanced journal entries.

The screens

What the buyer looks at each week.

Captured from the demo tenant, which mirrors the live workflow without exposing real supplier or sales data. Click to zoom.

What we still do by hand

The product informs the call. It does not make it.

Some of the most important purchasing decisions are judgement calls. We would rather be clear about where the product stops.

  • Supplier negotiation, price breaks, and payment terms.
  • New-product decisions and the first order for any SKU without history.
  • Cash-flow timing when several large POs land in the same month.
  • Deciding when a forecast with low accuracy should be overridden.

Want to talk to the people who run it?

We will walk you through our own weekly cadence, the numbers we are comfortable sharing, and what did not work. No script.

Want to be our first named customer story?

We draft it with you; you approve every metric, quote, and screenshot before it ships.