Supplier price-change approval workflow for restaurants: review before use

Price-change approval is a gate between supplier communication and operational use. A message can contain a new value without making clear whether it replaces a list, applies to one account, covers one pack, or merely illustrates a negotiation position. It may also mix a base price with delivery, deposit, surcharge, rebate, or tax information. A disciplined record keeps the source wording visible and adds the restaurant’s interpretation in clearly named fields. This makes a later invoice question more precise: was the line outside the approved scope, or did the restaurant approve the wrong identity?

Define the candidate before comparing it

Start by assigning an internal request key and attaching the source document or message as received. Capture supplier item code, restaurant item identity, description, pack count, net quantity, purchase unit, comparison unit, currency, price component, account, site, channel, effective date, and any stated end or review date. Record received date separately from effective date. If a document says a change applies to a product family but not to every pack, keep that boundary. If the supplier names a cause, preserve it as a supplier statement and do not recast it as independently verified market evidence.

• Use a stable request identifier and retain the original attachment, portal record, or message with its received timestamp.
• Keep old and proposed values tied to the same identity and unit basis before calculating a difference or percentage.
• Show base amount, freight, deposit, rebate, surcharge, tax presentation, and other components separately when the source distinguishes them.
• List affected sites, account, contract, ordering path, open purchase orders, recipes, and reports without assuming that every consumer must change.
• Write a specific question for missing notice, scope, pack, currency, or effective-date information and name the person responsible for answering it.

Check impact without turning an approval into a forecast

Once identity and scope are stable, inspect the records that could be affected. An open order may use the previous reference, a recipe may use a base unit, and an invoice may arrive after the proposed effective date. Map those relationships and send each one to its owner. The review can state that a recipe or order needs reassessment; it should not promise a customer price change, forecast demand, assert a margin result, or claim a saving. If the proposal is conditional on contract language or local tax treatment, hold the approval until the responsible reviewer resolves that condition.

Clearly labeled illustrative calculation: compare one unit basis

Make the decision reconstructable

A complete approval record lets another operator see the candidate, evidence, comparison basis, questions, impact map, authority, conditions, and final state. Keep a rejected or superseded proposal rather than deleting it, especially when an invoice or order later refers to the same item. If a proposal is approved for one site or date, make the limitation prominent and link it to the reference that purchasing will use. If it is held, describe the missing evidence and owner. The workflow should make deliberate continuity possible: a restaurant may keep a relationship, ask for clarification, negotiate, restrict use, or switch after separate review, but the price-change gate itself should not decide that strategy.

1. 1Register the request. Assign a request key, preserve the source message or document, and record received date, supplier, account, site, and responsible reviewer.
2. 2Lock the identity. Confirm item code, restaurant mapping, pack, units, currency, charge components, and effective boundary before making any comparison.
3. 3Test the evidence. Check notice, contract or account context, source wording, stated reason, and missing fields; distinguish supplier claims from operator verification.
4. 4Map consequences. List open orders, recipes, budgets, menus, approved lists, invoices, and substitutions that may require a separate owner review.
5. 5Decide with conditions. Approve, hold, reject, or request clarification under the local authority matrix, recording conditions, date, role, and permitted scope.
6. 6Publish the handoff. Link the approved reference or open question to purchasing and affected owners, retain prior states, and watch the first relevant transaction.