A request and an offer arrive separately.

A customer asks for a product, while a supplier sends a spreadsheet containing it among hundreds of other lines. The useful connection is easy to miss when requests, offer files and buying history sit in different places. Finding the same product is the start of the decision, rather than its conclusion.

With the agreed intake connected, Pycache captures and structures supported requests as they arrive. The team can examine relevant supply alongside the requested product, quantity, target price where supplied and existing commercial history. Demand here means known requests and available sales evidence. It is not a forecast of future demand, and a customer enquiry is not a confirmed order.

Match the identity before judging the opportunity.

Use EAN and the relevant size, variant and pack details to establish that both sides mean the same product. Similar descriptions deserve a check. A request for a 30 ml serum should not silently become a match for the 50 ml version because the names resemble each other.

Keep requested units, request date and any stated target price with the request. Record timing requirements where the source provides them. Missing information remains a question for the operator, not a fact invented to complete a match.

One request, several supply options.

In a fictional example, one customer wants 48 units and another wants 24. Three suppliers offer the same product. The demand is still 72 units. Three alternative matches do not turn it into 216 units, reserve stock or establish that either customer will buy.

Review price and timing together.

Suppose the customers need those 72 units within ten days. A stock offer lists €7.20 per unit with a 24-unit minimum. A preorder lists €6.80 with a 120-unit minimum and availability in 45 days. Assume identical products, EUR unit prices and no freight or tax included.

The preorder is cheaper per unit but does not meet the stated timing, and its minimum quantity is greater than the requests. The stock offer needs its own checks: confirm supply, delivery, order minimum and selling terms. Product availability at the supplier is different from stock already in your warehouse.

That review also needs the original source, its date, any expiry and outstanding charges. A customer target price provides negotiating context; it does not automatically determine a quote or prove a margin. Supplier price comparison supplies the commercial context around the match.

Give Sales a reason to follow up.

A new supplier offer can be relevant to a customer who has asked for the product or bought it before. Bring known requests and available sales history into the review so the team can see both the product match and why that customer may be relevant.

Requested quantities, previous sales and commercial terms provide different kinds of context. A past purchase is not a new request, and a match is not a promise of demand. Use them to prepare a focused conversation and a reviewed offer.

Move from a relevant match to a reviewed offer.

Buying reviews the relevant supplier list and approves the selling terms. Sales can then identify appropriate customers and prepare the permitted customer-facing output. The approval's scope matters: discussing one attractive product must not imply that someone reviewed every other product in the list.

Supplier identity, purchase costs, margins and original files follow the agreed role policy. Server-side restrictions and export checks keep the reviewed Sales output within that policy. Matching alone does not authorise a sale, send a customer message or create a purchase commitment.

Begin with the requests your team already receives.

A pilot starts with representative requests and supplier files, a buyer and a Sales participant. Include an unmatched request, a similar product that should stay separate and an offer that looks attractive but fails a commercial requirement. Review the expected result with the people who do the work.

We agree how requests enter the workflow and which outputs the team needs. If customer or product records live in Odoo, scope the relevant ERP connection before including it. You can also see the connected buying-to-sales workflow on the product overview.