Automate vendor price checks by comparing the delivered offer, not a number copied from a page.

Define what counts as the same offer.

Price monitoring fails when it compares a case with a single unit, a net price with a tax-inclusive price, or a different grade of the same product. Begin with the SKU or specification, quantity band, currency, unit, and delivery destination.

Ask Strawberry to mark items as comparable, partially comparable, or not comparable. That simple distinction prevents false savings from entering a procurement report.

Capture the terms that change the landed cost.

Freight, handling, tax, payment terms, lead time, minimum order value, and discounts can all matter more than a small movement in list price. Put the available commercial conditions beside the quote rather than hiding them in a note.

The resulting report should state both the visible rate and the caveats that need a buyer’s confirmation.

Make a change report that explains the evidence.

A procurement owner needs to know which supplier, item, and date changed, what the previous evidence was, what the new page or quote says, and whether the comparison is clean.

Each Monday, the vendor scan can capture the agreed SKU, region, currency, quantity tier, contract term, and shipping assumptions from the selected supplier pages, then highlight material deltas. It must not overwrite the buying comparison without review: a promotional price or mismatched tier can send procurement toward the wrong vendor.

Keep negotiation and ordering under buyer control.

A discovered difference can justify a buyer’s question, a request for a new quote, or a sourcing decision. It is not authority to contact a vendor, amend a contract, update a master record, or submit a purchase order.

Prepare the evidence and the proposed question, then let the procurement owner decide the commercial move.

Frequently asked questions