How per-set SKUs are counted and shared across rows

Learn how a per-set SKU's sets are rounded up once on the design-wide total and then shared proportionally across rows, and how to set up hinges, profiles and hardware for per-set pricing.

1. SKUs priced 'per set' carry catalog additional properties: procurement_per_area, procurement_per_length, or procurement_set_size (one set covers X area / X length / X units), plus procurement_unit for display. The quotation first sums the SKU's consumption across the ENTIRE quotation (per-SKU total quantity/area/length maps), converts to the procurement unit, and ceiling-divides by set size to get total sets. Each row then shows its proportional share: (row consumption / total consumption) x total sets. That is why a single row can legitimately show a fractional quantity like 0.4 sets — rounding-up happens once at design level, never per row, so per-row values intentionally do not each round up. minimum_procurement_size_for_pricing (another catalog property) floors the design-level set count; the same minimum-floor logic also applies to plain per-unit SKUs, spread proportionally across rows. Hidden rows are excluded from the totals before sets are computed; per-area rows whose stored area is unset derive their area from the row's own width x depth geometry. One protective rule: a row's total already carries its own count (self quantity x count plus contained items at their true quantities), so contained items' prices are not inflated by set rounding or a minimum. If set counts look wrong, verify the SKU's procurement properties and whether some consumption sits in hidden rows.

   ✓ ১৬ অক্টোবর, ২০২৬ তারিখে প্রোডাক্টে যাচাই করা হয়েছে

2. For hinges, set the Procurement Set Size additional property to 2 on the hinge SKU so that one set equals two hinges and the quotation prices them per set instead of per piece.

3. To price a profile per set, set its rate with the unit 'Per Set' (Edit SKU Properties > Pricing), then define what one set means on the profile's Properties > Additional Properties (Default Properties): 'Procurement per Length' (the length of one set, for example 10) and 'Procurement Unit' (for example Foot or Metre).

4. For hardware such as dowels and shelf pins, the quotation shows quantities per piece by default.

   ✓ ১৬ অক্টোবর, ২০২৬ তারিখে প্রোডাক্টে যাচাই করা হয়েছে

5. To have hardware such as dowels and shelf pins counted in sets or packets you must add the relevant procurement property (set size, per-area or per-length) to the SKU.

   ✓ ১৬ অক্টোবর, ২০২৬ তারিখে প্রোডাক্টে যাচাই করা হয়েছে

6. Only one quantity logic can be active at a time.

7. For two hardware categories only — profile handles (except edge profile handles) and hanger rods — that are priced per set with a procurement_per_length property, the quotation computes the number of stock lengths ('sets') by true 1D bin packing over each individual required cut length, instead of the usual sum-all-lengths-and-ceiling-divide. This models reality: three 2m handle cuts cannot come out of two 3m stock lengths even though 6m/3m = 2, so bin packing reports 3 sets where naive math says 2. Expect the billed set count to be equal to or HIGHER than total-length division whenever individual pieces don't tile neatly into the stock length. Eligibility is strict: the category must be profile_handles_hardware (a SKU whose handle_type is edge_profile_handle is excluded) or hanger_rod_hardware, the SKU's display unit must be per_set, the property must be procurement_per_length (not per-area or set-size), and the set size must parse to a positive number — otherwise the SKU silently falls back to normal per-set math. If a client questions the profile-handle set count, reconstruct it from the individual member lengths against the stock length, not from the summed length.