Customer-specific pricing#

B2B order errors often come from customer-specific prices. StackCube uses item default prices, customer price tiers, and tier rules so reviewers can compare incoming order prices before fulfillment.

StackCube catalog price columns — Default item prices give StackCube a baseline before customer price tiers and price rules are applied.

StackCube pricing management page — The Pricing page manages price tiers and customer tier assignments.

Pricing models#

StackCube supports practical pricing structures through price tiers and rules:

Default item price
Customer price tier
Fixed price rule for a specific item or SKU
Discount percentage rule
Quantity or date-limited rule

Setup approach#

Start with the prices that create the highest risk. You do not need to model every historical exception on day one.

Recommended order:

Default item price
Price tiers for customer groups
Customer tier assignment
Fixed-price or discount rules
Quantity or date limits only where needed

Pricing Page Workflow#

The Pricing page has three operating areas.

Create tiers such as VIP, wholesale, or distributor in Price tier management.
Search customers and apply a tier in Customer tier assignment.
Add global or item-specific rules in Price rule settings for each tier.

StackCube price tier modal — The price tier modal records a tier code and display name.

Tier codes must be unique. Use clear display names, but keep code values short and stable for CSV and integration use.

Price Rules#

Rules can apply to all items or a specific SKU.

Condition	Meaning
Default	Always applies.
Quantity range	Applies only within a min/max quantity range.
Date range	Applies only between start and end dates.
Quantity + date	Applies only when both conditions match.

Type	Meaning
Fixed price	Uses a specific price for the condition.
Discount rate	Discounts from the default sales price.

Avoid overlapping rules with the same target, quantity range, and date range. Always set an end date for temporary promotions.

Price Rule CSV#

You can download, edit, and re-upload price rules. If a rule ID exists, the upload updates that rule. Without a rule ID, StackCube uses the target and conditions to add or match a rule.

CSV rules:

Enter either fixed price or discount rate, not both.
Use YYYY-MM-DD for dates.
Use the all-items target type for global rules.
Enter SKU for item rules.
After upload, save the price-rule settings modal to apply changes.

Review flags#

During review, compare submitted prices with the configured item default and customer tier rules. Investigate lines where the submitted price differs from the resolved price, no price exists, or a date-limited rule has expired.

Operating practice#

Treat price corrections as policy decisions, not only data entry. If reviewers keep overriding the same price, update the relevant price tier or tier rule.