Managing own-brand and private-label products in Foodworks - A worked example

This article applies to the following workspace types

Nutrition Labelling Enterprise

This example shows you how to use resource sub-types and custom fields together to record different information for own-brand and private label products.

For example, a manufacturer producing pasta sauces might need to record:

  • For all products: internal product code and specification review date.
  • For own-brand products only: brand and planned launch date.
  • For private label products only: retail customer, customer product code and customer approval date.

You'll create two sub-types and seven custom fields, then assign the sub-types to two recipes. Each recipe shows the shared fields plus only the fields relevant to its product type.

To complete Steps 1 and 2 you must be an Organisation Owner or Administrator.

Step 1: Create the resource sub-types

  1. Go to Organisation settings and select Resource sub-types.
  2. Select Create sub-type.
  3. Enter the name Own-brand.
  4. Set Base resource type to Recipe.
  5. Save the sub-type.
  6. Repeat these steps to create a second sub-type named Private label, also with Recipe as the base resource type.

For more information, see Create and use resource sub-types.

Step 2: Create the custom fields

Some fields apply to every recipe, while others appear only on recipes with a particular sub-type.

Field name Type Visible on
Internal product code Text Recipe, Own-brand, Private label
Specification review date Date Recipe, Own-brand, Private label
Brand Single select Own-brand
Planned launch date Date Own-brand
Retail customer Single select Private label
Customer product code Text Private label
Customer approval date Date Private label
  1. Go to Organisation settings and select Custom fields.
  2. Select Create field.
  3. Enter the field Name and choose its Type.
  4. Set Visible on as shown in the table.
  5. Complete the Field settings. For the single select fields, add your brands or retail customers as options. Turn on Required for any field that should always be completed.
  6. Save the field.
  7. Repeat these steps for the remaining fields.

Tip: Organise the fields into sections, such as Product information, Own-brand information and Private label information, to group them on each recipe's Custom fields tab.

For more information, see Use custom fields in your resources.

Step 3: Turn on the sub-types and fields in your workspace

Sub-types and fields are turned on separately, and both must be on for the fields to appear.

Turn on the sub-types

  1. Go to Workspace settings. Under the Data heading, select Resource sub-types.
  2. Tick Own-brand and Private label.

Turn on the fields

  1. Go to Workspace settings. Under the Data heading, select Custom fields.
  2. Tick each of the seven fields you created in Step 2.

Changes save automatically.

Step 4: Assign the sub-types to recipes

The two examples below show how the fields on the Custom fields tab change with the sub-type.

Recipe 1: Own-brand pasta sauce

Classic Tomato Pasta Sauce is sold under the manufacturer's own brand, Harbour Pantry.

  1. Open the recipe and click Edit.
  2. On the General tab, select Own-brand from the Resource sub-type dropdown.
  3. Open the Custom fields tab and complete the fields.
Custom field Example value
Internal product code OB-001
Specification review date 01/10/2026
Brand Harbour Pantry
Planned launch date 15/01/2027

The private label fields are not shown.

Recipe 2: Private label tomato paste

Tomato Paste is manufactured for a supermarket customer, Retailer A.

  1. Open the recipe and click Edit.
  2. On the General tab, select Private label from the Resource sub-type dropdown.
  3. Open the Custom fields tab and complete the fields.
Custom field Example value
Internal product code PL-042
Specification review date 01/10/2026
Retail customer Retailer A
Customer product code RA-20418
Customer approval date 02/10/2026

The own-brand fields are not shown.

Changes save automatically.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.