Sales Managementdata

Pricing & Discounts

How are sale prices and discounts defined — tiers, margins, and time-boxed campaigns?

Pricing lives on the item: each article’s sale calculation defines minimum and maximum profit, two wholesale price tiers, and a point-of-sale-aware price tier, with partner-specific discounts layered on. Discount campaigns are separate, date-boxed records scoped to exactly the goods they should touch.

Referenced across4 other parts of continON

How it works

The sale calculation on an article sets the price structure once: minimum and maximum profit — each either an absolute figure or a percentage — a first and second wholesale price for tiered wholesale selling, and a POS price tier for point-of-sale-priced contexts. When a sale is entered, the chosen price tier on the sale header decides which of these prices the lines start from.

Discount campaigns are their own records with a name, a start and end date, and an active flag. A campaign is scoped by up to three levels of article classification, by warehouse, by supplier, and by the sale price tiers it applies to. During sale entry the applicable discount for a line is resolved by article, price tier, warehouse, and date — so an expired or out-of-scope campaign simply does not fire.

What the table carries

#MaintainedResolved against it
01Profit bounds on the itemMinimum and maximum profit are stored per article, as absolute values or percentages, framing what a sale price may be.
02Two wholesale tiersFirst and second wholesale prices support tiered wholesale selling from the same item record.
03POS-aware price tierA dedicated POS price tier prices point-of-sale contexts — a pricing tier, not a retail terminal.
04Classification-scoped campaignsDiscount campaigns target articles by three classification levels, plus warehouse, supplier, and price tier.
05Date-resolved applicationThe discount applied to a sale line is resolved by article, tier, warehouse, and date at entry time.

See pricing & discounts running in continON.

A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.