Product data is operational infrastructure
A product description may seem like a small detail until it appears in billing, purchasing, stock and reports. Infinity includes barcode and product-master management alongside categories, subcategories, brands and item types. Give product-data ownership to named people and agree conventions before adding a large catalogue.
Keep identifiers consistent
Review item codes and barcodes for duplicates, incomplete values and unclear descriptions. Demonstrate the lookup and billing behavior using representative products, including any size or batch distinctions your business needs. A barcode should help the operator select the intended product; it should not hide uncertainty in the master data. Agree how product changes will be checked before they reach the counter.
Treat different prices as different responsibilities
Supplier cost, customer-specific price and store selling price serve different purposes. Infinity’s scope includes all three. During configuration, make the relevant source and scope visible to users. A price valid for one customer or location should not be assumed to apply everywhere. Ask the team to demonstrate how the configured rules select a price in a realistic transaction.
Control price variations
Infinity includes price-variation approval and posting. Use that workflow to separate proposing a change from applying it. Confirm who may approve, who may post and how the outcome is reviewed. For forecourt prices, the supplied scope also includes controlled transmission to PTS equipment; that integration must be authorized and matched to the actual equipment configuration.
Review the effect after a change
A price update should be checked at the point where it is used. Inspect a sample bill, the intended store or customer context and the relevant management report. Keep the supplier cost history available when investigating a margin change. The strongest product-master process combines clear ownership, controlled updates and a practical verification step.
Your practical checklist
- Resolve duplicate codes and unclear descriptions.
- Define responsibility for products and price changes.
- Demonstrate store and customer pricing with sample transactions.
- Verify approved changes in the intended operational context.
Common questions
Can Infinity maintain different selling prices by store?
Yes. Store-wise selling prices are included in the supplied pricing scope.
Does a supplier cost update always mean an automatic selling-price change?
Do not assume that. Confirm the pricing and approval rules used in your configured workflow.
Product scope is based on the supplied Infinity specification. Confirm modules, hardware compatibility and implementation responsibilities for your own setup. This guide does not make a competitor ranking or promise a business result.