Product module
Product summary applet
- Code is the ParagonERP Product number. This is a next number.
- Description is the ParagonERP product description
- The other 2 fields can be used in case pivot is being used

Attributes applet
Attributes can be used to drive order characteristics like descriptions, prices, leadtime and vat. Most attributes however just have an information or reporting goal. When a module is mentioned, an attribute has a feature logic.
| Dutch | English | Description | Module |
| Vervolgomschrijving | Description 2 | For information only | |
| Color | Kleur | For information only | |
| Productstatus | Product status | A = Active, , P = Phase out, R = Replacement, O = Obsolete. | Future use on Order:: determine behavior on order. |
| Artikelgroep | Item group | Select products belonging to the same product group | Purchase proposals |
| Artikel Prijsgroep | Item price group | To set prices or discount per group of products | Sales discount |
| Garantie | Warranty | For information only | |
| Sales UOM | Sales UOM | If products are sold in 2 UOM's (each and m2) the 2nd UOM can be set here. | Order |
| Sales UOM Conversion | Sales UOM Conversion | Conversion of Sales UOM to default UOM | Order |
| Levertijd | Delivery time | Indication of the leadtime of a product which is not kept in stock | |
| Verkoopeenheid | Sales packing unit | For information only | |
| Alert verkoop | Alert sales order | ||
| Commercial item | Commercial item | Item description to use on external documents/sites. Can be overwritten per language in Associations | Order |
| Alert pick | Alert pick note | Alert can be shown on pick | |
| SKU | SKU | For information only | |
| Picklocatie | Pick location | Required to pick and ship goods | ParagonWMS, Pick |
| Putawaylocatie | Putaway location | Different from pick inIn case of bulk locations. | Future use: At receipt goods will be moved to putaway location |
| Producttype | Product type | Buy, Make, Kit, Consumable, Non-stock, Service. The Product type will determine how the product is sourced |
Future use automatically create Workorder based upon product type. |
| Alert levering | Alert shipment | Alert can be shown on pack and ship | |
| Maateenheid | Unit of measure | ||
| ABC code | ABC code |
ABC code is the result of an analysis which you would like to use to optimize warehousing ABC analysis could be volume based, amount based, or movement based.
|
Future use. BigQuery reporting |
| Flitscontrole | Check location quantity | Minimum quantity to check stock on default pick location. | |
| Land van oorsprong | Country of origin | Country of origin | |
| EAN code | EAN code | For information only | |
| UPC code | UPC code | For information only | |
| Brutogewicht | Brut weight | Weight with package material | |
| Nettogewicht | Nett weight | Weight without package material | |
| End of life datum | End of life date | Date product will not be available anymore | |
| Min Qty | Min Qty | PO proposals | |
| Max Qty | Max Qty | PO proposals | |
| Veiligheidsvoorraad | Security stock | Safety stock | |
| Inhoud | Volume | Volume of package | |
| AEEA code | WEEE code | Item classification for WEEE reporting | |
| Box length | Box length | For information only | |
| Box width | Box width | For information only | |
| Box height | Box height | For information only | |
| Label URL | Label URL | For information only | |
| Min bestelhoeveelheid | Min order quantity | For information only | |
| Item Duty % | Item Duty % | ||
| Vaste verrekenprijs | Purchase cost | Standard cost to calculate inventory adjustment value and COGS | Ship, Invoice |
| Alert inkoop | Alert purchase | Notes on purchase order, receipt | |
| Commodity code | Commodity code | For information only | |
| Levertijd | Lead time | Leadtime when products are not kept in stock | |
| Kwaliteitscontrole | Quality control | For information only | |
| Leverancier | Vendor list | Primary vendor | Vendor, PO proposals |
| Inkoper | Purchase responsible | Will be shown on Purchase proposals and Purchase order | Person, PO proposals |
| Gemiddelde voorraadwaarde | Average product cost | Average inventory cost. Calculated included landed cost. Display only | Inventory, Ship, Receive |
| Laatste inkoopkosten | Last landed cost | In mycompany currency. Including landed cost | Inventory, Receive |
| Laatste inkoopdatum | Last purchase date | Is already shown in related info. In supplier currency | |
| BTW | Tax | VAT High, Low or Zero. The actual % is taking from Tax setup module. Can be overwritten by country in associations. | Order, Invoice, Purchase order, Association |
| Webshop artikelcode | Webshop product number | For integration purposes: Webshop Product id |
Purchase cost
The purchase cost on a product cam be seen as a form of standard cost. It can be used for purchase pricing and journal entry creation, but only will be used in certain situations.
- Purchase pricing: ParagonERP uses a hierarchy to determine purchase pricing. It will first search for a vendor product price configuration, and if not found it will use the Purchase cost to set a price on a purchase order.
- Valuation: ParagonERP by default uses FIFO costing. It will valuate stock and create journal entries with the FIFIO values on purchase orders and inventory tranactions.
However in case no purchase price exist , or no inventory value has been set the system will use the purchase price as cost in valuation and journal entry creation.
Examples are:- The inventory quantity of a product is 0 and a stock adjustment is made: ParagonERP will use the purchase cost.
- A non-stock item is used for labour services. The purchase cost will be used for costing.
Interface configuration
Product id, name and number usage

| Product | Application | System API | Experience API |
| Database id (invisible) | n.a. | id | ItemId |
| Product number | Code | name | ItemName to be replaced by ItemCode |
| Description | Description | description | Description |
Trigger Product
A product has 1 or more Sales channels and an interface select date supporting integration with external applications. The sales channel will contain all applications the customer is integrated with, while the interface select date is used as a trigger to send a new or changed customer to an external application.
If any of the following fields are modified, the interface select date is set. This will trigger a transfer of the product to an external application like SimpleSimon.
- PRODUCT_TYPE: 'pgnProductType',
- PARAGON_ITEM_STATUS: 'pgnItemStatus',
- DESCRIPTION: 'description',
- COLOR: 'color',
- STYLE: 'style',
- SIZE: 'size',
- UOM: 'unitOfMeasure',
- PRODUCT_GROUP: 'productGroup',
- ITEM_PRICE_GROUP: 'itemPriceGroup',
- COMMERCIAL_ITEM: 'commercialItem',
- ABC_CODE: 'pgnAbcCode',
- COMMODITY_CODE: 'pgnCommodityCode',
- COO: 'pgnCoo',
- DELIVERY_TIME: 'pgnDeliveryTime',
- EOL_DATE: 'pgnEolDate',
- GROSS_WEIGHT: 'pgnGrosWeight',
- NET_WEIGHT: 'pgnNettWeight',
- PURCHASER: 'pgnPurchaser',
- SALES_UOM: 'pgnSalesUOM',
- EAN: 'pgnEan',
- UPC_CODE: 'pgnUpcCode',
- WEEE: 'pgnWeee',
- SALES_CHANNEL: 'pgnSalesChannel',
- WEBSHOP_PRODUCT_CODE: 'pgnWebshopProductCode',
- PICTURE: 'picture'