Group account prices break down at site level because the group agreement sits at the top of the account hierarchy, but each site is invoiced on whatever terms sit closest to it. In many systems the most specific price wins, so older site-level prices, agreed before the group deal or carried over from an acquisition, quietly outrank the group price list. Overcharges surface as queries from the customer’s head office. Undercharges rarely surface at all, so margin the agreement was meant to protect is given away site by site without a decision being made.
What is a group account in food wholesale?
A group account is a customer that trades through several sites under one parent account, such as a restaurant group, a care home operator or a contract caterer.
The agreement is negotiated with one procurement team at head office. Every site then orders against it.
On paper, that makes group accounts some of the simplest to manage. One set of terms is loaded against the parent account and inherited by every site underneath.
In practice, prices, delivery terms and invoicing details can sit at group, brand or region, and site level. The system decides which one applies to each order.
Why don’t all sites get the group price?
Because the most specific price usually wins, and it isn’t always the most recent one.
Most group accounts aren’t built from scratch. Sites that were customers before the group agreement often carry local prices agreed by a rep years earlier. Sites added through an acquisition bring their old terms with them.
Those site-level prices sit beneath the group price list and outrank it. The group view shows the agreement loaded and live, so nothing looks wrong from head office.
What does it look like in practice?
Take a wholesaler that signs a new group agreement with a regional restaurant group in April. Head office has negotiated a price list on core lines, standard payment terms and consolidated invoicing. The price list is loaded against the parent account and the commercial team confirms it’s live.
In May, the group’s procurement team runs its first compliance check. It finds a few sites paying above the group price on core lines. The query is raised against the agreement as a whole, credit notes are issued, and the account manager spends the next month rebuilding confidence in a deal that had only just been signed.
Nobody goes looking for the sites paying below the group price. They exist too, on lines where an old local deal was sharper than the new agreement. Customers don’t query being undercharged, so those prices carry on month after month.
Invoicing follows the same pattern. The agreement says invoices go to head office, but older sites still hold their own invoice-to details. Head office pays the invoices it receives, the rest sit with sites that assume head office has them, and the statement never reconciles at group level.
What else puts sites outside the group agreement?
The same structure catches other everyday changes. A site is sold to a different operator but stays on the parent account, still ordering on group terms. A site moves from one of the group’s trading brands to another and keeps the old brand’s pricing. A regional manager agrees a local price on a line the group list doesn’t cover, it’s added at site level, and it’s still there two renewals later.
Each one is small, and none of them shows up in the group view.
What does it cost when site terms overrule the group agreement?
The cost lands in two places.
Overcharges are found by the customer, usually by the procurement team that negotiated the deal. That puts the supplier on the back foot at the account that matters most.
Undercharges are found by nobody. Margin the agreement was meant to protect is given away at site level without a decision ever being made.
By renewal, head office has a list of discrepancies and the wholesaler has a group margin figure that doesn’t match what was agreed. Neither side trusts the other’s numbers, and the negotiation starts from there.
How do you check whether a group agreement is applied at every site?
Take your largest group customer and run three checks.
First, pick five sites, including the oldest on the account and the most recently added. For three core lines at each, trace where the invoiced price is actually coming from: the group, a brand or region, or the site itself.
Second, list every site-level price or terms override on the account, and note whether each one still has a reason to exist.
Third, compare the invoice-to details on every site against how head office expects to be billed.
If the price comes from different levels at different sites, the group agreement is only partly in force. If some overrides no longer have a reason behind them, those sites are still trading on deals that ended long ago. If invoices are going somewhere head office doesn’t expect, the statement will keep failing to reconcile, however carefully finance works through it.
What keeps group account pricing accurate over time?
Accurate group accounts come from looking past the agreement to the level where each site is actually invoiced.
That means reviewing site-level overrides whenever a group agreement is signed or renewed, rather than loading the new terms on top of the old ones. It means treating a site joining, leaving or changing brand as a reason to check its terms, not just its delivery address.
It also means group and site terms being visible together, so a local price that outranks the agreement shows up before the customer’s procurement team finds it.
None of this changes the commercial judgement behind the agreement. It makes sure the agreement is what actually gets invoiced.
How Allsop helps
At Allsop, we work with food and beverage businesses to bring more accuracy and control to complex customer accounts, through intelligent software for Customer Order Management, Data Workbench and Customer Margin Management.
That means group and site terms surfaced together, orders checked against the terms that should apply at each site, and fewer queries from a customer’s head office that your own team hasn’t seen first. Sales colleagues are empowered to grow share of wallet across every site in the group, while also hunting for new accounts.
Speak to Allsop, and we’ll look at how your largest group accounts are structured and where site-level terms are overruling the agreement. Or read more on the Allsop blog.
Frequently asked questions
What is a group account in food wholesale? A group account is a customer that trades through several sites under one parent account and one negotiated agreement, such as a restaurant group, a care home operator or a contract caterer. Terms are agreed with head office and meant to apply at every site, while orders, deliveries and often invoices happen site by site.
Why don’t all sites in a group account get the group price? In many systems the most specific price wins, so a site-level price sits beneath the group price list and outranks it. Sites that were customers before the group agreement, or joined through an acquisition, often still carry older local prices. Those prices are invoiced instead of the group terms, and the group view doesn’t show it.
How do you check whether a group agreement is applied at every site? Take your largest group customer, pick a handful of sites including the oldest and the newest, and trace where the invoiced price on a few core lines actually comes from. Then list every site-level override and check whether each one still has a reason to exist, and compare each site’s invoice-to details with how head office expects to be billed.
How can food wholesalers keep group account pricing accurate? By keeping group and site terms visible together and checking each order against the terms that should apply at that site, so a stray local price shows up before the invoice does. Allsop’s Customer Order Management and Data Workbench help food and beverage businesses surface group and site terms together and check orders against them.
