Skip to main content

Products (SKUs)

What is a SKU?​

A SKU (Stock Keeping Unit) is a product definition — not a specific production run, but the product type itself. "HDPE 2-inch SDR-11 Smoothwall" is a SKU. You might have dozens of orders for it, but only one SKU definition.

Think of SKUs as the product catalog. Everything else in RunMark — lines, orders, schedules, labels — references a SKU.

SKU fields explained​

  • Part/product number — the identifying number for this product. Left free-text unless you've defined a part numbering scheme for it, in which case it builds itself.
  • Name — the product name. Be specific: include size, material, and spec. "HDPE 4-inch SDR-11" is a good name. "Pipe" is not. Specificity matters because lines and orders both reference the exact SKU name.
  • Description — optional additional detail. Use this for internal notes, customer codes, or spec references.
  • Unit — what quantity is measured in: feet, meters, units, kilograms, pounds, etc. This unit appears throughout orders, schedules, and labels.
  • Default run size — typical production run quantity in the SKU's unit. Used as a starting point when creating orders — you can always change it per order.
  • Feet per reel — for reel-based products, how many feet (or meters) go on one reel. When set, quantities convert automatically to reel counts everywhere — orders, the Demand List, and Inventory.

Variable product options​

Define variants — color, tape type, or anything else specific to how you make a product — directly on the SKU record instead of maintaining near-duplicate SKUs for each variant. Add an option group (a name and its list of values), and it becomes a selectable field wherever that SKU is used.

Combinatorial part numbers​

For a SKU that needs one, define a part-numbering scheme instead of typing a part number: pick the segments that make it up (category, size, color, and so on) and the order they combine in. As variant options are selected — on an order, for instance — the part number builds and validates itself from those segments automatically. Rules can also force or restrict a segment's values based on another segment's value (for example, a specific wall type always forcing a specific type code).

Change history​

Every edit to a SKU is logged — who changed what, and when. Open a SKU and switch to its History tab to see the full record.

Why SKUs must be created first​

Lines reference SKUs to define their capabilities and speeds. Orders reference SKUs to specify what to produce. Labels reference SKUs to print the product name. SKUs are the foundation — you can't configure lines or create orders until you have at least one SKU.

Recommended order: SKUs → Lines → Orders → Schedule → Labels.

Adding and editing SKUs​

Go to Products in the sidebar and click Add product. Fill in the name, unit, and default run size. After saving, the SKU is immediately available to reference in lines and orders.

To edit, click the SKU in the list and update any field. Changes apply to future references; existing scheduled blocks retain their original values.

Deleting SKUs​

danger

You cannot delete a SKU that is referenced by active orders or line configurations. Cancel or complete the active orders first, then remove the SKU from any line's capability list before deleting.