Start with the incoming offer.

Wholesale offers arrive as email attachments, spreadsheets, PDFs and long lists with different layouts. Before comparison can begin, someone has to identify the product, locate the commercial fields and check what is missing.

Once the agreed inbox and file workflows are connected, Pycache automatically captures and structures supported material. It extracts and normalises EAN, product references, descriptions, brands, prices, currencies, quantities, order minimums and availability where supplied and supported. Stock and preorder offers remain distinct.

Supported formats and fields are established with your representative files during implementation. Unreadable or incomplete material needs review; automatic intake does not make every layout reliable.

Start with the same product.

A supplier list is useful only when its rows can be compared with the right products. A familiar name can conceal a different size, pack or variant. An attractive price can describe a carton while another describes one unit. Those differences need resolving before a price ranking means anything.

The structured offers connect with product and commercial records for review. EAN, size and other relevant product details help establish identity. Where an input is incomplete or uncertain, the operator needs to see the source and resolve the issue. Implementation begins with representative files and agreed layouts; supported intake is established with your actual material.

Put the price beside the terms.

Review currency, unit or pack basis, available quantity, minimum units, minimum order value and stock versus preorder status together. Keep the supplier's offer date and validity visible. A previous purchase provides context, but its quantity, terms and date may differ from today's offer.

Illustrative comparison: the same 30 ml serum
OfferUnit priceAvailabilityMinimum units
North€7.20120 units in stock24
East€6.80Preorder, stated availability in 45 days120

Assume two customers have requested 72 units and need them before that preorder becomes available. East's lower unit price does not answer the timing question, and its unit minimum exceeds those requests. North merits review, but its stated stock still needs confirming.

For this example, both offers also have a €1,000 supplier minimum order value. Seventy-two North units total €518.40 before any freight or tax, so this product alone does not meet that order minimum. Other products may complete an order, but the buyer must review them too. These are fictional terms, not available stock or a savings claim.

Keep the comparison connected to its source.

Open the original supplier file when a value needs checking. Keep a distinction between what the supplier stated, what was converted to a common basis and what remains unknown. Freight, duties and tax treatment can change the cost of a decision; an unquoted charge must not quietly become zero.

Comparisons across currencies require an agreed conversion source and date. Pack conversions need a confirmed number of units. The supported reporting currency and treatment of these costs are part of implementation scope. A price comparison is not automatically a complete landed-cost calculation.

For a practical spreadsheet method, follow our guide to comparing supplier price lists, including an example of different pack sizes and minimum orders.

Work with the result.

Dashboards and comparison tables bring the structured offer together with buying history, alternative supply, sales history and available market references. Recommended next actions help prioritise review, negotiation and source checks. They depend on the evidence present and remain decisions for your team.

Open the original file, investigate a flagged row and export the buying comparison. Once the relevant list and selling terms are approved, Sales can prepare a customer offer with the fields it is permitted to see. See how source access, role visibility and approval fit into that handoff.

Give Buying and Sales a shared next step.

Price history becomes more useful alongside customer requests for the same product. Buying can investigate a relevant offer, review the list and approve selling terms. Sales can then prepare a customer offer within the agreed access policy. Approval is a human decision; it does not place a purchase order.

Start with one workflow, representative source files and the exact buying and customer outputs your team needs. We agree product identity, commercial rules, permissions and acceptance before the pilot. Where records belong in an ERP, integration is scoped around those records and decisions.