Commerce · CO1

Product Catalog & Pricing

4
Processes
156
Details worked out
24
Execution steps
4
Diagrams
CO1.01

Sales Part & Catalog Management

Defines and maintains sales parts as the sellable catalog items in IFS Cloud, connecting inventory or non-inventory master parts to sales-relevant data such as sales price group, unit of measure, tax codes and characteristics. Sales parts are the foundation for pricing, ordering and commerce because every price list, agreement and campaign line references a sales part and its sales price group.

Sales / Order Management
38 details
diagram
CO1.02

Sales Price List & Base Price Management

Maintains sales part base prices and the part-based and unit-based sales price lists derived from them, including quantity break pricing and assortment-node pricing. Price lists are connected to customers and customer price groups and are searched in a defined priority order when pricing customer orders and quotations.

Sales / Order Management
39 details
diagram
CO1.03

Customer Agreement & Pricing Management

Manages customer agreements that define negotiated prices, discounts and terms applied to future customer orders, including deal-per-part, deal-per-sales-group and deal-per-assortment pricing plus validity periods and cumulative amount/quantity limits. Agreements sit above price lists in the pricing priority ladder and can be inherited through the customer hierarchy.

Sales / Order Management
39 details
diagram
CO1.04

Campaign, Promotion & Discount Management

Defines sales campaigns and the deals within them (deal per part, deal per assortment and conditional sales promotions) that offer special prices or discounts to all, specified or grouped customers for a period. Sales promotions use buy/get conditions applied as negative charges to customer orders, and campaigns sit high in the pricing priority ladder with an option to be ignored if a lower price is found.

Sales / Order Management
40 details
diagram
What a license opens

Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.

Sign in to open it