Operational Items

Operational Items define the shared item, product, service, resource, digital item, or other business object reused across Pinkapple ERP. They sit above module-specific records such as stock items, shared scan aliases, billable services, product designs, agriculture produce, pricing targets, and document transaction lines.

Use operational items to avoid each module creating its own inconsistent version of the same business object.

Workspace Reference

Workspace	How Users Reach It	What Users Usually Do There
Operational Items	Administration -> General Setup -> Operational Items	Create the shared item, product, service, resource, or digital record used downstream.
Operational Item Categories	Administration -> General Setup -> Operational Item Categories	Maintain the reusable category tree used by items, products, services, and downstream service setup.
Stock Items	Inventory -> Setup -> Stock Items	Turn an operational item into an inventory-managed stock item where quantity tracking is required.
POS, Production, Agriculture, Billing, And Inspections	Service-specific setup or operations workspaces	Reuse the operational item instead of creating duplicate item identities.

Categories

Operational item categories group related records and help users search, filter, price, stock, and report consistently.

Important category fields include:

• Shared Category Code: the system-facing reference shown after creation.
• Category Name: the user-facing name.
• Description: explains when the category should be used.
• Parent Shared Category: places the category inside a reusable category tree.
• Family: identifies whether the category is for goods, services, resources, digital items, or another type.
• Active: controls whether the category is available for new use.

The Family field matters because it helps downstream users distinguish stockable goods, billable services, schedulable resources, digital items, and other reusable records.

Do not create duplicate categories for the same business meaning. Use parent categories and clear naming when the difference is operationally important.

Item Records

An operational item identifies what the business sells, buys, stocks, produces, inspects, bills, or schedules.

Important item concepts include:

• Item Kind: goods, service, resource, digital, or other.
• Category: the reusable grouping selected before downstream modules use the item.
• Primary Unit of Measure: the base unit used by stock, pricing, production, logistics, and reporting.
• Variant Attributes: attributes such as size, colour, grade, material, or pack size.
• Stock Managed: whether quantity tracking is expected downstream.
• Sellable: whether the item can be sold or billed.
• Purchasable: whether the item can be procured.
• Manufacturable: whether the item can be produced or assembled.
• Active: whether the item is available for new transactions.

Scan Codes And Media

Operational items may carry scan-code style references such as barcodes, SKUs, PLUs, QR codes, RFID tags, supplier codes, or other identifiers. These help POS, warehouse, and procurement users identify the correct item quickly.

Media can be attached as images, documents, videos, audio, or links where the item needs visual identification, compliance documents, product sheets, or training material.

Downstream Impact

Operational items affect:

• Inventory stock setup and stock movement.
• POS sales, returns, shared item aliases, and Pricing item targets.
• Billing and pricing rules.
• Product designs, materials, BOMs, and production.
• Agriculture produce intake, grading, and settlement.
• Inspection checklists and measurement references.
• Document transaction line selection.

Changing an item that is already used downstream should be done carefully. Rename or deactivate only when users understand the effect on active workflows and reports.

Common Mistakes

• Creating separate items for the same product in POS, inventory, and billing.
• Marking an item as stock managed when the business only bills it as a service.
• Leaving the primary unit of measure unclear before pricing or stock movements.
• Using item names to hold variant details instead of structured attributes.
• Deactivating a record that still appears in active workflows.

Good Practice

Create the category tree first, then create clean item records with the correct kind, unit, and usage flags. Use one operational item as the master reference and let module-specific setup build on it.