Skip to main content

Products

Products

Purpose and when to use this record

Control how a Brisk storesinventory productsitem asis partdescribed, ofpriced, categorized, imaged, and made available in a storefront.

At a glance

  • Identify it by: Store, Item, Slug, and Short Description.

  • Check its business context: Store, Item, and Default Fulfillment Warehouse.

  • Why care: Store, publication, consent, payment, and fulfillment states affect what customers see and what staff must act on; check the ecommercecorrect module.store Thisbefore generatedsaving.

    reference
  • 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 permission for the action you are taking on products. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Have valid Store, and Item records ready first. Those selections determine where this Product belongs and which later screens can find it.

Create a recordProduct

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

TheCreate evidencea packetProduct identifiesafter searching for the viewperson, organization, item, location, or resource under alternate names and sourceidentifiers. locationMerge or correct an existing master record instead of creating a duplicate.

  1. Select the business context first: Store, Item, and Default Fulfillment Warehouse.

  2. Enter the required identifying and operational values: Store, and Item.

  3. Review Is Published, Featured, Allow Backorder, Allow Shipping, Allow Pickup, and Allow Drop Ship deliberately; these choices control availability or workflow rather than merely describing the record.

  4. Save the Product, then confirm Created by, Last modified by, Custom fields, Deleted at, Store, and Item, plus the remaining screen fields on its detail page before continuing.

After saving: Preview the storefront listing and confirm price, availability, imagery, collections, and publication state before promoting it.

Delete a Product

Delete this Product 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 Is Published to remove it from future use while preserving existing references.

Before confirming, check for thisrelated action.Collections, Confirmand user-facingProduct stepsImages. beforeBrisk approvingmay refuse deletion when another record depends on this page.one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Store, Item, Slug, and Short Description. After confirmation, return to the Products list and make sure only the intended Product was removed.

ViewReview recordProduct details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Product currently means. Verify Store, Item, Slug, and sourceShort locationDescription before relying on it for a decision.

Follow Store, Item, and Default Fulfillment Warehouse to determine whether the issue is on this action.Product Confirmor user-facingon stepsone of those linked records.

Next check: Preview the storefront listing and confirm price, availability, imagery, collections, and publication state before approvingpromoting it.

Edit an existing Product

Edit this Product 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 Store, Item, and Default Fulfillment Warehouse with the supporting document or approved request.

  2. Recheck Is Published, Sale Price, Compare At Price, Default Fulfillment Warehouse, Min Order Quantity, and Max Order Quantity. These values are most likely to change storefront visibility, customer communication, payment, or fulfillment.

  3. Save the change, return to the list, and confirm that the Product now appears under the expected Is Published.

After the change: Preview the storefront listing and confirm price, availability, imagery, collections, and publication state before promoting it.

Find and review recordsproducts

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

The evidence packet identifiesUse the viewProducts list to find the correct record before opening or changing it. Compare Store, Item, Slug, and sourceShort locationDescription. Records with similar names or numbers can still belong to different Store, Item, and Default Fulfillment Warehouse.

  • Keyword search checks Name, Item Code, Slug, and Short Description.

  • Narrow the list with Store, and Item filters.

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

Open the Product whose Store, Item, Slug, and Short Description match the task. If it is missing, clear the list filters and recheck Store, Item, and Is Published rather than creating a replacement immediately.

Fields and business rules

Brisk stores 20 user-relevant fields for this action.Product, Confirmincluding user-facing3 stepslinked-record beforeselections approvingand 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

sourcelocation user-facingstepsbeforethispage.

Delete a record

user-facingsteps
Field RequiredWhat it controls
StoreYesThe evidencestore packetassociated identifieswith thethis viewproduct andlisting.
ItemYesThe item associated with this product listing.
SlugNoURL-safe identifier for this action.product Confirmlisting.
Short approvingDescription No The evidenceshort packetdescription identifies the view and source locationrecorded for this action.product Confirmlisting.
DescriptionNoDescription of this product listing.
Seo TitleNoThe SEO title recorded for this product listing.
Meta DescriptionNoThe meta description recorded for this product listing.
Seo KeywordsNoComma-separated focus keywords used for storefront SEO guidance and search metadata.
Featured ImageNoFile stored as featured image for this product listing.
Is PublishedNoWhether this product listing is published.
FeaturedNoWhether the featured option applies to this product listing.
Sale PriceNoThe sale price value recorded for this product listing.
Compare At PriceNoThe compare at price value recorded for this product listing.
Allow BackorderNoWhether this product listing allows backorder.
Allow ShippingNoWhether this product listing allows shipping.
Allow PickupNoWhether this product listing allows pickup.
Allow Drop ShipNoWhether this product listing allows drop ship.
Default Fulfillment WarehouseNoThe default fulfillment warehouse associated with this product listing.
Min Order QuantityNoThe min order quantity value recorded for this product listing.
Max Order QuantityNoThe max order quantity value recorded for this product listing.

What happens next

Preview the storefront listing and confirm price, availability, imagery, collections, and publication state before approvingpromoting thisit.

Common mistakes and troubleshooting

  • The record will not save: Recheck Store, and Item 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 Is Published, 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: Open Store, Item, and Default Fulfillment Warehouse from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.