Skip to main content
GullySystem
Manufacturing

Price Lists and Schemes for Institutional food suppliers

Apply dated price lists and promotional rules to eligible transactions.

Sales and Distribution

Does this function belong in your operation?

Use when prices vary by customer group, channel, quantity or promotion.

A price or commercial offer changes.

Rice, dal and produce can follow different commercial arrangements within the same supply business. A hospital tender rate may remain fixed while another kitchen buys at a dated market rate. Configure item units, account eligibility and effective dates explicitly so a new vegetable rate does not silently overwrite an institution's agreed contract.

Bring the records the workflow depends on.

  • Institution contracts, customer assignments and item-wise price-list references.
  • Effective dates, purchase or sales units and the approved rule for market-linked revisions.
  • Authorised scheme conditions and rules for combining an offer with an existing contract rate.

Outputs to check

  • Dated price version showing which kitchen accounts and item units it covers.
  • Order-price explanation identifying the contract or market list applied to a supplied line.

Follow the price lists and schemes workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Create the price basis

    Record items, buyer groups and effective dates.

  2. 2. Define offer rules

    Set eligibility, limits and whether offers combine.

  3. 3. Approve publication

    Review exceptions and release the authorised version.

  4. 4. Apply to transactions

    Select the correct terms during quoting or billing.

  5. 5. Review overrides

    Retain manual discounts and preserve historical transaction prices.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Commercial manager

Approves new rates and confirms which customer contracts permit a change.

Order-desk and accounts staff

Apply the authorised version and investigate differences before an incorrect rate reaches the institutional bill.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Market rate changes during packing

Use the configured pricing event and retain the accepted version; do not reprice a confirmed indent merely because a list was edited.

Contract rate omitted

Refer the item for commercial review rather than falling back silently to another kitchen's market price.

Scheme conflicts with tender terms

Hold the proposed offer until its eligibility is approved, keeping the institution's agreed terms intact.

Can this work independently?

Pricing can be maintained independently, but quoting or billing must use the approved selection rules for consistent application. Customer groups and item codes provide eligibility. The price module does not establish stock availability, contractual acceptance or whether a promotion is legally permitted.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Dealer portal: Partner identities, submitted orders and permitted account information.

Configure, test and introduce the workflow.

  • Hand over price sheets, scheme letters and the discount habits of the counter. A note groups them into lists.
  • Decide who sits on which list and how far each role may go. Bills that pick the right rate come back. Try them. Staff raise sample bills from several lists. Corrections return as an adjusted set of lists.
  • Billing clerks and sales staff practise approvals. A reference sheet for the counter follows. The next offer is entered with its dates. A review after it ends checks what each party paid.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Changing the market list does not alter a customer line protected by a separately assigned contract rate.
  • A rate for a sack cannot be applied as a per-kilogram price without an authorised unit conversion.
  • Accounts can reconstruct the price version used for a disputed delivery without relying on today's list.
Institutional food suppliers

How the business operates.

You supply the kitchen, not the shelf. Each hostel, hospital ward kitchen or caterer sends an indent, expects the sacks and crates at a fixed hour, and weighs them on its own platform scale before signing.

Mess and canteen logins

Give each hostel, hospital kitchen or caterer a login tied to its price list and ledger, and let the mess manager place or repeat the daily indent from a phone.

Price lists with start dates

Maintain a rate list for each customer or tender contract, with the date each rate applies from. Contract end dates and the daily vegetable rate are added at set-up.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Institution, delivery location and authorised buyer
  • Indent, standing requirement and effective rate contract
  • Route picking and loading record
  • Signed delivery note, weight difference and rejection

Operational bottlenecks to check

Daily indents arrive by call, message and sheet

Calls, voice notes and photographed sheets all reach the order desk in different layouts, and one item is missed. The cook finds out at the gate.

Contract rates drift from billed rates

A rate agreed for a tender period lives in a letter, and bills are raised at the last price used. The customer’s auditor notices before you do.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Confirm the indent

    Record the institution’s requirement and delivery location. Retain changes to standing quantities rather than silently overwriting the earlier request.

  2. 2. Source and prepare the route

    Confirm availability and any proposed substitution, then prepare the route pick list using the agreed units.

  3. 3. Record receiving-gate decisions

    Capture the quantity accepted, short supply and rejected items against the delivery note. Keep the receiving person’s acknowledgement with the record.

  4. 4. Resolve quantity and rate differences

    Apply the contract version effective for the delivery and review unapproved substitutions or disputed weights before billing.

  5. 5. Consolidate and collect

    Build the agreed billing statement from supported deliveries, with each adjustment traceable to its source. Reconcile receipts and unresolved deductions.

Industry reports to connect with

  • Indents and standing quantities awaiting supply
  • Route shortages, rejections and delivery differences
  • Delivered quantities against contract-rate versions
  • Consolidated bills, deductions and outstanding balances

Questions before implementation.

When should institutional food suppliers consider price lists and schemes?

Use when prices vary by customer group, channel, quantity or promotion. A price or commercial offer changes.

What should we bring to the requirements discussion?

Bring anonymised examples of Institution contracts, customer assignments and item-wise price-list references.; Effective dates, purchase or sales units and the approved rule for market-linked revisions.; Authorised scheme conditions and rules for combining an offer with an existing contract rate. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Apply dated price lists and promotional rules to eligible transactions. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Commercial policy and permitted promotional terms must be approved by your business.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Changing the market list does not alter a customer line protected by a separately assigned contract rate. Use this check when reviewing the first working version.

Talk to us

Discuss price lists and schemes for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements