12Distribution & Wholesale · ERP software

Supplier price history and purchase comparison

Buying decisions made against what each supplier actually charged over time.

  • Supplier price history
  • Comparison at PO entry
  • Price variance alerts
  • Supplier performance tracking

The problem

Purchase prices were remembered or found by digging through old invoices, so price creep went unnoticed and comparison between suppliers was impressionistic.

What we built

We retain every purchase price per supplier per item, presented as history and comparison at the point of raising a purchase order.

Modules delivered

  • Supplier price history
  • Comparison at PO entry
  • Price variance alerts
  • Supplier performance tracking
  • Lead time recording
  • Landed cost calculation

What changed

What the delivered system does differently from the process it replaced.

  • Price history is visible when the order is raised
  • Price increases are flagged rather than absorbed
  • Supplier comparison uses recorded prices

Built with

The stack chosen for this build.

  • Go
  • PostgreSQL
  • REST API

Why this customer is not named

Most of our customers allow the work to be described but not their name published. Where a customer has given permission, their name and testimonial appear here.

Independent accounts of our work are published by customers themselves on our Facebook reviews page.

Does this look like your problem?

If any of this is familiar, the first step is the same one this project started with: a free requirement study that ends in a written scope and a fixed price.

SYODONTECH
Supplier price history and purchase comparison | Case Study | Sydon Tech