Products - Acosys Documentation

Used By

Administrator or module owner

Data Type

master data

Search Keys

Code, Name

When to Use This Form

When users need to create, review, or update Products.
When this data needs to be available as a choice in transactions, reports, filters, or settings.
When existing data needs correction because policies, accounts, prices, contacts, or operating rules have changed.

Before You Start

Make sure the user has access to this menu and the related reference data has already been prepared.
Check required fields first, especially codes, names, dates, accounts, customers, suppliers, products, divisions, or departments.
If the form uses active status, confirm the status before saving so the data appears in the correct selections.

Workflow

Open Report Products / Product List.
Create a new record, or select an existing record when the data needs to be corrected.
Fill in the required fields and complete supporting information that helps search, reporting, or transaction processing.
Review the code, name, status, accounts, grouping, and other references before saving.
Click Save. If the application shows a validation message, follow the message until the data is saved successfully.

Key Fields

Field	User Explanation	Status
Code `id`	Unique code used to identify Products. Use a consistent pattern so users can search and sort the data easily.	Required
Name `name`	Name shown in selections, transactions, and reports. Use wording that is clear for daily users.	Required
Product Group `productgroup`	Product or item reference used in stock, sales, purchasing, or production processes.	Required
Supplier `supplier`	Supplier reference used for purchasing, payables, or supplier reports.	Required
Tax Type `taxtype`	Tax information used for transaction calculation and tax reporting.	Required
Category `category`	Category stores information needed by Products. Fill it in according to the company data standard.	Required
Product Bundle `productpackage`	One bundled product can contain multiple items. Fill in this detail when the product category is a bundle so the system knows which items are included when the bundle is sold.	Required
Product Unit `units`	One product can have multiple units such as PCS, BOX, or DOZEN. This detail controls conversion, purchase price, selling price, discounts, barcodes, and unit availability in transactions.	Required
BOM Components `mrpbomcomponent`	One manufactured product can have multiple raw-material components. Fill in this detail so the system knows which materials are needed to produce the finished item.	Required
Production Operation List `mrpbomoperation`	One manufactured product can have multiple production steps. This detail describes the operation sequence, duration, and labor cost used in the manufacturing process.	Required

Details and Relationships

The header section defines the product identity. The detail sections define how the product is sold, converted, bundled, or manufactured in daily operations.

If a detail section is marked as required, the product is not fully ready to use until that detail has been completed. Fill in each detail carefully and make sure the values match your real business process.

One bundled product can contain multiple items. Use this detail when you sell bundles, hampers, promo sets, or service packages made up of more than one item.

If this product is a bundle, you should create at least one bundle detail row. Click the + or Add button to add a new item into the bundle.

In this detail form, users typically fill in the bundled item, item name, quantity, cost, and subtotal for each component. The system uses this structure when the bundle is sold or processed.

Practical tip: keep the bundle contents aligned with what actually leaves the warehouse. If the bundle composition changes, update this detail as well so stock movement and cost analysis stay accurate.

One product can have several units. For example, the same product may be sold in PCS, BOX, or DOZEN depending on how your company buys and sells it.

Because this detail is required, you should create at least one unit for this product. Click the + or Add button to create a new unit row.

This detail form usually includes unit name, quantity or conversion to the base unit, purchase price, purchase discount, purchase tax, net purchase value, selling price levels 1 to 7, quantity-based selling discounts, default selling discount, discount formula, division and department restrictions, and unit active status.

Start with the base unit first, usually with quantity = 1. After that, add higher units such as box or dozen so stock conversion and pricing remain consistent.

Simple example: if the base unit is PCS, then DOZEN can use quantity 12. That tells the system that 1 DOZEN = 12 PCS.

One manufactured product can have multiple BOM components. This detail lists the raw materials or supporting materials required to make one finished product.

If the product is manufactured internally and BOM is required in your setup, create at least one BOM component row. Click the + or Add button to add a new material.

This detail usually includes component product, product name, required quantity, and usage unit. The system uses this information for material planning and work-order preparation.

Practical tip: enter the quantity based on the real requirement to produce one finished unit. Consistent units will help prevent planning mistakes.

One manufactured product can have several production operations. This detail describes the work steps the product must go through from start to finish.

If production operations are required, create at least one operation row for this product. Click the + or Add button to add a new production step.

This detail usually includes operation or work process, operation name, operation unit, labor cost, duration, and duration unit. These values help the system estimate production time and labor cost.

Arrange the operations in the same sequence used on the shop floor, such as cutting, assembling, sewing, finishing, and packing. A clean sequence makes work orders easier for the production team to follow.

The more accurate the operation list is, the easier it is for the production team to understand workload, expected time, and labor cost per product.

After Saving

Active data can appear as a choice in transactions, reports, filters, or settings that use this reference.
Changes are normally used for new activity. Historical documents remain available for review.
If required data is incomplete or inconsistent, the application rejects the save and shows a validation message.

Common Issues

Data cannot be saved: complete required fields and read the validation message shown by the application.
Data does not appear in selection or search: check active status, access rights, filters, and the search keyword.
Duplicate code or name: use the existing record when it should be corrected, or use a different code for a new record.
Report values do not match: recheck reference data, accounts, dates, transaction status, and related filters.

Available Fields

The list below summarizes the fields available in this form. Field labels follow the English UI language file used by the application.

Field	User Explanation	Status
Code `id`	Unique code used to identify Products. Use a consistent pattern so users can search and sort the data easily.	Required
Name `name`	Name shown in selections, transactions, and reports. Use wording that is clear for daily users.	Required
Product Group `productgroup`	Product or item reference used in stock, sales, purchasing, or production processes.	Required
Supplier `supplier`	Supplier reference used for purchasing, payables, or supplier reports.	Required
Tax Type `taxtype`	Tax information used for transaction calculation and tax reporting.	Required
Category `category`	Category stores information needed by Products. Fill it in according to the company data standard.	Required
Active `isactive`	Status that controls whether the data can be used in new transactions or selections.	Optional
Product Bundle `productpackage`	Bundle composition detail. Use it when one product is sold as a package of multiple items.	Required
Product Unit `units`	Unit list containing conversion, purchase price, selling price, barcode, discount, and unit usage restrictions.	Required
Reward `salesproductrewardrules`	Product or item reference used in stock, sales, purchasing, or production processes.	Optional
BOM Components `mrpbomcomponent`	List of raw materials or supporting components needed to produce the item.	Required
Production Operation List `mrpbomoperation`	List of production steps including duration and labor-cost information.	Required
Factory `factory`	Factory stores information needed by Products. Fill it in according to the company data standard.	Required
Brand `brand`	Brand stores information needed by Products. Fill it in according to the company data standard.	Required
Author `author`	Author stores information needed by Products. Fill it in according to the company data standard.	Required
Last Updated `updatetimestamp`	Audit timestamp filled in automatically by the application.	Optional
Alias Code `aliasid`	Unique code used to identify Products. Use a consistent pattern so users can search and sort the data easily.	Optional
Available in POS `availableinpos`	Available in POS stores information needed by Products. Fill it in according to the company data standard.	Optional
Sales Discount `salesdiscrules`	Discount value or rule used when the transaction is calculated.	Optional
Sales Commission `salespersoncommrules`	Sales Commission stores information needed by Products. Fill it in according to the company data standard.	Optional
Points `salespointrewardrules`	Points stores information needed by Products. Fill it in according to the company data standard.	Optional
Service Staff Commission `servicedoercommrules`	Service Staff Commission stores information needed by Products. Fill it in according to the company data standard.	Optional
Use product serial number `usesn`	Product or item reference used in stock, sales, purchasing, or production processes.	Optional
Minimum `minimum`	Minimum stores information needed by Products. Fill it in according to the company data standard.	Optional
Maximum `maximum`	Maximum stores information needed by Products. Fill it in according to the company data standard.	Optional
Min. Reorder `minimumreorder`	Min. Reorder stores information needed by Products. Fill it in according to the company data standard.	Optional
Default Reorder `defaultreorder`	Default Reorder stores information needed by Products. Fill it in according to the company data standard.	Optional
Width `dwidth`	Width stores information needed by Products. Fill it in according to the company data standard.	Optional
Height `dheight`	Height stores information needed by Products. Fill it in according to the company data standard.	Optional
Length `dlength`	Length stores information needed by Products. Fill it in according to the company data standard.	Optional
Weight `weight`	Weight stores information needed by Products. Fill it in according to the company data standard.	Optional
Description `description`	Additional explanation for users who need context when reviewing this record.	Optional
Image `image`	Image stores information needed by Products. Fill it in according to the company data standard.	Optional
Created By `usercreate`	Audit information filled in automatically when the record is created.	Optional
Updated By `useredit`	Audit information filled in automatically when the record is updated.	Optional

Menu Location

Report Products / Product List
/form/product