Product Specifics 'Specs' form at SKU-level (the source of SKUs for Bill of Materials) #397

New Issue

2026-06-29T08:38:03Z

rob commented

2026-06-29 08:38:03 +00:00

This form should be as free form and abstract as possible. We will offer some eStack default common sense fields, and allow users to add more. At first, the only data that is connected elsewhere would be the Component SKUs.

Product Specs form on SKU-level Info tab
Provide default recommended fields
Ability to Create ‘Sections’. or ‘Headers’ This creates an Header title for associated fields underneath on the form. Users can customize according to their business requirements.
Ability to add and remove fields under the Sections or Headers
Have a section called Component SKUs. Here the user can add SKU/Qty lines using a SKU picker then entering the qty in the next field.
Toggle switch or checkbox to enable Component SKUs and another checkbox to ‘Deduct Inventory of Component SKU’ or similar. Mark the components ‘Shipped’ somewhere if need be in the backend to accommodate inventory deduction.
Page is Printable in XML with images of component SKUs Images should be 165 px wide to match what the older folk here are used to seeing. http://via.placeholder.com/165x165
Rob will make csv file to set as the super basic eStack Specs tab defaulttemplate, and another csv with ZR’s specific fields and header sections. Users can add or remove fields except when a field calls for a SKU (or is tied to other data).
Support templates of Headers and associated fields. That way we can make industry specific specs that can easily load later for different business models. Quickbooks does this when setting up your businesss the first time in regards to typical expense accounts. If you're an oil lube station, your specs (product attributes) will be very different. Or even a phone accessories company

This form should be as free form and abstract as possible. We will offer some eStack default common sense fields, and allow users to add more. At first, the only data that is connected elsewhere would be the Component SKUs. - Product Specs form on SKU-level Info tab - Provide default recommended fields - Ability to Create ‘Sections’. or ‘Headers’ This creates an Header title for associated fields underneath on the form. Users can customize according to their business requirements. - Ability to add and remove fields under the Sections or Headers - Have a section called Component SKUs. Here the user can add SKU/Qty lines using a SKU picker then entering the qty in the next field. - Toggle switch or checkbox to enable Component SKUs and another checkbox to ‘Deduct Inventory of Component SKU’ or similar. Mark the components ‘Shipped’ somewhere if need be in the backend to accommodate inventory deduction. - Page is Printable in XML with images of component SKUs Images should be 165 px wide to match what the older folk here are used to seeing. http://via.placeholder.com/165x165 - Rob will make csv file to set as the super basic eStack Specs tab defaulttemplate, and another csv with ZR’s specific fields and header sections. Users can add or remove fields except when a field calls for a SKU (or is tied to other data). - Support templates of Headers and associated fields. That way we can make industry specific specs that can easily load later for different business models. Quickbooks does this when setting up your businesss the first time in regards to typical expense accounts. If you're an oil lube station, your specs (product attributes) will be very different. Or even a phone accessories company

rob added the Discussion Planning labels 2026-06-29 08:38:03 +00:00

rob closed this issue

2026-06-29 08:38:03 +00:00

Sign in to join this conversation.

No Label Discussion Planning

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#397