Products
What This Is
Products are the main catalog records you sell through Pyle. A product brings together the item name, SKU, category, brand, product type, pricing inputs, stock behavior, shipping details, and related media.
This is one of the main day-to-day records merchandisers and catalog operators work with.
When You Would Use It
Use Products when you need to:
- add a new sellable item
- update catalog details for an existing item
- control whether an item is active, discontinued, or featured
- adjust shipping, stock, or ordering-related fields
- connect the item to the right type, category, and brand
- prepare the item for any separate collection workflow your team uses
Do not use the product record when you only need to rename or restructure a category, brand, or product type. Those are managed separately.
Before You Start
Before you create or update a product, make sure:
- you can access the main
Productsarea in the admin - the brand, product type, and category already exist
- you know the bilingual product name you want to publish
- you understand that some related product details live in sub-sections such as attributes, images, documents, and videos
- you understand that collection membership matters to some storefront behaviors but is not exposed as a normal direct field in the inspected packaged product form
How To Use It In The Admin
- Open the main
Productsscreen in the admin. - Create a new product if you are adding a new item, or open an existing product to edit it.
- In the create dialog, set the basic fields:
- active status
- SKU
- barcode if available
- name
- brand
- product type
- product category
- After creation, use the product detail page to complete the rest of the setup:
- descriptions
- stock status and stock behavior
- pricing details such as MSRP and quantity limits
- shipping dimensions
- product associations such as brand, type, and category
- Save the product.
- Use the related blocks on the same page when you need to add attributes, images, documents, videos, cross-sells, or shipping classes.
What to pay attention to:
SKUis the operational identifier teams usually search by.Active,Discontinued, andFeaturedeach change the merchandising state in different ways.- The brand, type, and category choices affect downstream browse, shipping, and promotion behavior.
- Collection membership is not exposed as a normal field on the inspected packaged product page. If your implementation uses collections, handle that through the related import or generated workflow.
What It Changes In The Storefront
Products are first-class storefront records.
They affect:
- whether shoppers can open a product page
- what the shopper sees on the product page
- whether a product can appear in category, brand, and collection browse flows
- whether product-group selectors appear for switching between related products
Some shopper-facing changes are indirect. For example, changing category or collection context can affect filtering or grouped product selection rather than changing the product page text directly.
Common Tasks
Create a new product
Use the main Products screen and complete the initial create dialog, then finish the record on the product detail page.
Update pricing or shipping inputs
Use the product detail page to update MSRP, quantity limits, shipping dimensions, and stock behavior.
Change product classification
Use the association section on the product page to update the brand, product type, or category.
If the product also depends on a collection, finish that through the related collection workflow instead of expecting the main product page to manage it directly.
Add supporting content
Use the product sub-sections to add images, documents, videos, and attributes.
Bulk manage products
Use Excel import/export when you need to create or update many products at once.
Rules, Limits, And Things To Watch
- A product depends on its catalog context. If the brand, type, or category is wrong, downstream browse and rules can be wrong too.
- Some related fields are not managed from the first create dialog. You often need the full product page after creation.
- Collection membership can be managed indirectly. In the inspected packaged UI, it is not a normal field on the main product form.
- Changing the brand on an existing product can also affect collection-driven behavior, because the product may need to be re-aligned with the collection workflow your team uses.
- Some storefront behavior depends on related setup such as images, inventory, offers, or product groups.
- Bulk Excel workflows can create and update products, so teams should agree on which workflow is the source of truth.
Troubleshooting
I created a product, but it is incomplete
That is normal if you only used the create dialog. Open the product detail page and finish the shipping, stock, association, and supporting-content sections.
I changed a product, but the storefront still looks wrong
Check the related records too. Product pages depend on images, category context, offers, inventory, and sometimes product groups.
If the issue is collection-related, review the collection workflow too instead of checking only the main product page.
I cannot classify the product the way I want
Make sure the brand, product type, and category records already exist first.
I need to update many products at once
Use the Excel product export and import workflow instead of editing each product manually.
For a storefront-visibility checklist, see How to troubleshoot why a product is missing from the storefront.
Related Features
- Catalog & Merchandising
- Product Types
- Product Categories
- Brands
- Collections
- How to create and publish a product
- How to troubleshoot why a product is missing from the storefront
Sources
packages/admin/routes/web.phppackages/admin/src/Livewire/Admin/Products/CreateProductDialog.phppackages/admin/src/Livewire/Admin/Product/Page.phppackages/admin/resources/views/components/product/page.blade.phppackages/admin/src/Livewire/Admin/Tools/Excel/ExportDialog/ProductExport.phppackages/framework/src/Actions/Import/Product/Sheets/ImportProductRows.phppackages/framework/src/Listeners/Product/RemoveProductCollection.phppackages/storefront/src/Livewire/Storefront/Product/Page.phppackages/framework/src/Http/Resources/Storefront/ProductResource.php