Skip to main content

Fulfillment Methods

Fulfillment Methods

Purpose and when to use this record

Define the pickup, delivery, shipment, or other handoff choices available to sales and ecommerce orders.

At a glance

  • Identify it by: Name.

  • Why care: These master records supply defaults and choices to later transactions. Correct duplicates and inactive records before staff build more activity on the wrong record.

Before you begin

You need the Brisk storespermission for the action you are taking on fulfillment methodsmethods. asIf parta ofCreate, theEdit, managementor 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 recordfulfillment method

Brisk Fulfillment Methods create screen displayed with fictional documentation-demo data.
The Fulfillment Methods create screen in the Brisk documentation demo.

TheCreate evidencea packetfulfillment identifiesmethod only when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and make later selection harder.

  1. Select the business context first.

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

  3. Review Tracking Url against the source locationdocument or approved setup decision.

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

After saving: Open Orders, Sale Fulfillments, and Stores and confirm the fulfillment method 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 fulfillment method

Delete this page.fulfillment method 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 Orders, Sale Fulfillments, and Stores. 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 Fulfillment Methods list and make sure only the intended fulfillment method was removed.

ViewReview recordfulfillment method details

The evidence packet identifiesUse the viewdetail page as the shared record of what this fulfillment method currently means. Verify Name, Description, and sourceTracking locationUrl before relying on it for thisa action.decision.

Confirm

Compare user-facingthe stepsfulfillment method with its source document or approved setup request before approvingdeciding that it needs correction.

Next check: Open Orders, Sale Fulfillments, and Stores and confirm the fulfillment method appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Edit an existing fulfillment method

Edit this fulfillment method 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 Name with the supporting document or approved request.

  2. Recheck the identifying information shown on the screen. These values are most likely to change future transactions, defaults, assignment, pricing, and reporting.

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

After the change: Open Orders, Sale Fulfillments, and Stores and confirm the fulfillment method 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 recordsfulfillment methods

Brisk Fulfillment Methods list screen displayed with fictional documentation-demo data.
The Fulfillment Methods list screen in the Brisk documentation demo.

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

  • The initial order emphasizes Name. Select a column heading when you need a different comparison.

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

Fields and business rules

Brisk stores 3 user-relevant fields for this action.fulfillment Confirmmethod, user-facingincluding steps0 beforelinked-record approvingselections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation user-facingstepsbeforeapproving arecord

user-facingstepsbefore
Field Required What packetit identifiescontrols
NameYesHuman-readable name for this action.fulfillment Confirmmethod.
Description YesDescription of this page.

fulfillment

Deletemethod.

Tracking UrlNoThe evidencetracking packeturl identifies the view and source locationrecorded for this action.fulfillment Confirmmethod.
approving

What happens next

Open Orders, Sale Fulfillments, and Stores and confirm the fulfillment method 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 Name, and Description 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 page.fulfillment method with the source document or approved setup decision, then check the downstream screen where it is used.