Foodservice Option Groups

Foodservice Option Groups

Purpose and when to use this record

Define an ordered group of foodservice choices, such as sizes or add-ons, and whether cashiers can use it.

At a glance

• Identify it by: Group Name.

• Why care: Warehouse, item, unit, quantity, and cost must describe the same physical movement. A wrong warehouse or unit can make availability and valuation misleading.

• Why care: Availability and publication flags affect future use without erasing history. Prefer disabling an obsolete setup record when existing transactions still refer to it.

Before you begin

You need the Brisk storespermission for the action you are taking on foodservice option groupsgroups. asIf parta ofCreate, theEdit, inventoryor module.Delete This generated referencecontrol is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Create a recordFoodservice Option Group

TheCreate evidencea packetFoodservice identifiesOption Group only when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and sourcemake locationlater selection harder.

1. Select the business context first.

2. Enter the required identifying and operational values: Group Name.

3. Review Active deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Foodservice Option Group, then confirm Group Name on its detail page before continuing.

After saving: Open Foodservice Options, and Items and confirm the Foodservice Option Group appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Delete a Foodservice Option Group

Delete this page.Foodservice Option Group only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

If the record is merely obsolete, use Active to remove it from future use while preserving existing references.

Before confirming, check for related Foodservice Options, and Items. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Group Name. After confirmation, return to the Foodservice Option Groups list and make sure only the intended Foodservice Option Group was removed.

ViewReview recordFoodservice Option Group details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Foodservice Option Group currently means. Verify Active before relying on it for a decision.

Compare the Foodservice Option Group with its source document or approved setup request before deciding that it needs correction.

Next check: Open Foodservice Options, and sourceItems locationand confirm the Foodservice Option Group appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Edit an existing Foodservice Option Group

Edit this Foodservice Option Group when the underlying policy or classification changed. First determine whether historical transactions should retain the old value; if so, deactivate the old choice and create a new one.

1. Open the detail page. Compare Group Name with the supporting document or approved request.

2. Recheck Active. These values are most likely to change warehouse availability, replenishment, quantities, and valuation.

3. Save the change, return to the list, and confirm that the Foodservice Option Group now appears under the expected Active.

After the change: Open Foodservice Options, and Items and confirm the Foodservice Option Group appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Find and review recordsfoodservice option groups

The evidence packet identifiesUse the viewFoodservice Option Groups list to find the correct record before opening or changing it. Compare Group Name. Compare the full identifier rather than relying on a similar name.

• The initial order emphasizes Sort Order, and sourceGroup locationName. Select a column heading when you need a different comparison.

Open the Foodservice Option Group whose Group Name match the task. If it is missing, clear the list filters and recheck Active rather than creating a replacement immediately.

Fields and business rules

Brisk stores 3 user-relevant fields for this action.Foodservice ConfirmOption user-facingGroup, stepsincluding before0 approvinglinked-record selections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation stepsbeforeapprovingpage.

Delete a record

stepsbeforeapproving

Field	Required	What packetit identifiescontrols
Group Name	Yes	Human-readable name for this action.foodservice Confirmoption user-facinggroup.
Sort thisOrder	No	The evidencesort packetorder identifiesvalue the view and source locationrecorded for this action.foodservice Confirmoption user-facinggroup.
Active	No	Whether this page.foodservice option group is active and available for use.

What happens next

Open Foodservice Options, and Items and confirm the Foodservice Option Group appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Common mistakes and troubleshooting

• The record will not save: Recheck Group Name and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Active, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Compare this Foodservice Option Group with the source document or approved setup decision, then check the downstream screen where it is used.