Carriers

Carriers

Purpose and when to use this record

Maintain the trucking or freight carriers used for commodity and manufacturing movements.

At a glance

• Identify it by: Name.

• Why care: Confirm item, formula, unit, warehouse, quantity, and production state together; mistakes can distort both material consumption and finished-goods cost.

Before you begin

You need the Brisk permission for the action you are taking on carriers. If a Create, Edit, or Delete control is absent, do not work around it with another user’s account; ask an administrator to review your role.

Create a carrier

Create a carrier after searching for the person, organization, item, location, or resource under alternate names and identifiers. Merge or correct an existing master record instead of creating a duplicate.

1. Select the business context first.

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

3. Review the identifying information shown on the screen against the source document or approved setup decision.

4. Save the carrier, then confirm Name on its detail page before continuing.

After saving: Verify this carrier in Manufacturing Orders before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a carrier

Delete this carrier 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.

Before confirming, check for related Manufacturing Orders. 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 Name. After confirmation, return to the Carriers list and make sure only the intended carrier was removed.

Review carrier details

Use the detail page as the shared record of what this carrier currently means. Verify Name before relying on it for a decision.

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

Next check: Verify this carrier in Manufacturing Orders before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Edit an existing carrier

Edit this carrier to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

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

2. Recheck the identifying information shown on the screen. These values are most likely to change material demand, production status, output quantity, and cost.

3. Save the change, return to the list, and confirm that the carrier now appears under the expected Name.

After the change: Verify this carrier in Manufacturing Orders before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Find and review carriers

Use the Carriers list to find the correct record before opening or changing it. Compare Name. Compare the full identifier rather than relying on a similar name.

Open the carrier whose Name match the task. If it is missing, clear the list filters and recheck the identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 1 user-relevant fields for this carrier, including 0 linked-record selections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this full reference.

Field	Required	What it controls
Name	Yes	Human-readable name for this carrier.

What happens next

Verify this carrier in Manufacturing Orders before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Common mistakes and troubleshooting

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

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