The group food library

Share dishes, prep items, the products in them and whole menus from the organisation library to your businesses. Updates go live at once and each business acknowledges them.

5 min readUpdated Today
organisationorganizationhead officegroupgroup foodfood libraryrecipesdishesprepproductsallergensmasterlibrarysupplier changerestaurant groupbrandlinked copyfrom head officemenusgroup menu

What it is

The group food library is the food part of the organisation library. Head office keeps master dishes and prep items there, with the products that go into them. Each business that uses one holds its own linked copy, and when head office changes the master, every linked copy follows.

So a supplier change, such as a bun that now contains sesame, is made once at head office, not by hand at every business.

What it holds

  • Dishes, with their recipes

  • Prep items, such as sauces and bases. A business holds one copy of each, used by every dish that needs it

  • Products inside them: the bought-in ingredients, with their allergens and the ingredients list from the supplier's spec

  • Menus, built from the library's dishes, with their sections. Each business sets its own sites, served times and page, and can add local specials. See Group menus

Each business's allergen chart, menus, public allergen page and exports are built from its own copies, as they are for its own dishes. A group menu never changes a dish's allergens: it only lists the business's own copies.

How it differs from the rest of the library

HACCP, SFBB, risk assessments, SOPs, documents, routines

Dishes, prep, products and menus

When an update changes the business

When the business reviews and takes it

As soon as head office publishes it

What the business does

Reviews it section by section

Acknowledges it afterwards

Locked parts

Chosen on a Required update

Set on the master, with the main parts locked from the start

The rules

  • Stricter moves at once, looser waits. An allergen head office adds shows at every linked business straight away. An allergen head office removes stays at each business until someone there confirms it.

  • A new dish waits for the business. The first time a business takes a dish, it arrives unconfirmed. It stays off that business's public allergen page, exports, audit pack and labels until someone there checks and confirms its allergens. Later updates go live with head office's confirmation.

  • Linking never changes a confirmation. If a dish a business already has is linked to a master, its confirmation stays as it was.

  • The business's own settings stay its own. Its confirmations, whether a dish is hidden from the public page, its own menus and its till links are never changed by head office. On a group menu, its sites, served times, page and page settings stay its own too.

  • A dish taken off a group menu stays. It leaves that menu at once, and stays on the business's chart and every other menu it is on.

  • A business can say it doesn't serve a dish. It takes the dish off its copy of a group menu with Not served here, and it stays off there until the business puts it back. Head office sees which businesses don't serve it. The dish still follows head office's updates.

  • Billing and records stay with each business. Nothing is merged.

The badge

In each business, a dish, prep item or product from the library carries a badge naming the organisation, such as From Your Group, on the web and in the app. The parts head office looks after are shown locked. See Group recipes and prep.

Getting dishes into the library

As with any master, you can start from a dish one of your businesses already has. Paddl copies it into the library with its prep items and products, and links that business's copy to it. Then choose who it is for and add it to businesses. See Adding Library Items to Businesses.

Who does what

  • At head office: organisation admins and library editors look after the masters and publish updates. Only admins can revert one

  • At each business: the owner or any manager confirms a new dish and acknowledges updates. The owner or a manager for the whole business confirms removals

See Organisation Roles.

Following an update

Each master has a History showing every version and, for each business, whether it is applying, applied, failed or skipped, and when it was applied and acknowledged. If the latest update was a mistake, an organisation admin can revert it: the previous version is published again, and any allergen that takes away waits at each business to be confirmed. See Publishing an Update to a Master.

If a master is deleted, or a business leaves

If head office deletes a master, each business keeps its copy as its own and is told. If a business leaves the organisation, its linked dishes become its own. Either way, a removal still waiting stays waiting until someone at the business confirms it.

Try Paddl free for 30 days

Compliance, training, and daily operations in one platform. Nothing is charged until the trial ends.

Start Free TrialView all features

Related Articles

Organisations

Organisations: Running Several Businesses Together

An organisation ties separate Paddl businesses together without merging them. What it is, who it is for, and what it can and cannot see.

Organisations

Creating an Organisation and Adding Businesses

Create an organisation from All businesses, add the businesses you own, invite franchisees, and what happens when a business leaves.

Organisations

The Organisation Library

Keep master HACCP plans, SFBB packs, risk assessments, SOPs, documents and routines in one library, starting from what businesses already have.

Organisations

Adding Library Items to Businesses

Roll a master out to chosen businesses and sites. It arrives ready for staff to sign, approved by you, in the businesses you run.

Back to Organisations