How Price Is Picked #

Quick answer #

IGFirstERP picks the final selling price from configured product prices, customer price groups, tier rules, and permitted overrides so pricing stays controlled instead of improvised at the counter.

Problem #

Pricing inconsistency causes margin leakage, staff abuse risk, and weak trust in operational numbers.

Who this is for #

• Pricing owners
• Sales supervisors
• Founders protecting margin and discount discipline

Prerequisites #

• Products and units configured correctly
• Selling price groups defined
• Tier pricing rules reviewed and activated where needed
• Override permissions assigned by role

Steps #

1. Set base product price and unit relationships.
2. Define selling price groups for customer segments (for example retail vs wholesale).
3. Configure tier pricing rules with scope, conditions, and priority.
4. Restrict manual overrides so only authorized roles can edit price on live transactions.
5. Test pricing behavior on representative transactions before rollout.

Common mistakes #

• Mixing unit margin logic with customer segment pricing
• Activating overlapping tier rules without clear precedence
• Allowing manual price edits for all cashier roles
• Discounting without approval rules and audit trail

Verification checklist #

• Same product returns expected price by customer type and quantity
• Tier rule priority resolves as intended
• Price changes are auditable by user role
• Unauthorized roles cannot override price at POS

Escalation #

If final price is unexpected, escalate with transaction sample, product variation, customer group, quantity context, and acting user role.

Related workflow links #

• Pricing Guardrails (MSP, Overrides, Permissions)
• SKU and Barcode Standards
• End-of-Day Sales Reconciliation

CTA #

View Pricing Plans

Book an Operations Call

Last reviewed #

2026-02-22