Skip to main content
Manual price lookups are one of the most common sources of order errors: the wrong price list gets applied, a negotiated rate is overlooked, or a recent price change hasn’t been communicated to the person processing the order. StackCube eliminates that problem by letting you define pricing rules for each customer directly in the platform. When an order arrives, the AI intake engine checks every submitted price against the applicable rule automatically — before the candidate reaches your review queue. Lines that match are marked clean; lines with discrepancies are flagged so your team can resolve them with full context, not after the fact.

​
What per-customer pricing rules do

Individual price lists

Each customer in your account can have their own price list, reflecting negotiated rates, volume tiers, or contract pricing that differs from your standard catalog.

Automatic AI matching

When an order candidate is created from an incoming message or file, the AI checks each line’s submitted price against the rule for that customer — no manual lookup required.

Discrepancy flagging

Lines where the submitted price does not match the configured rule are flagged in the review queue, giving your team a clear signal to investigate before approving.

Customer portal visibility

Customers accessing their order portal only ever see their own prices. No customer can view another customer’s pricing rules or order history.

​
Setting up pricing rules

1

Navigate to the customer record

Open the customer you want to configure pricing for. Each customer has a dedicated settings area within StackCube where you manage their details, contacts, and pricing rules.
2

Add a price rule for each SKU

For each SKU the customer orders, set the agreed unit price. You can add rules one at a time or import a price list in bulk using a CSV upload. Rules are applied at the SKU level, so the AI can match against them precisely.
3

Set effective dates if needed

If a price is only valid for a specific period — for example, a promotional rate or a contract renewal window — you can set start and end dates on a rule. StackCube will apply the correct rule based on the order date.
4

Save and activate the rules

Once your rules are saved, they take effect immediately for all new incoming orders from that customer. Existing candidates already in the review queue are not retroactively re-evaluated.
5

Update rules as pricing changes

When a customer’s pricing changes, update the rule in their record. StackCube will use the new rule for all orders processed after the update. Keeping rules current is what keeps the AI matching accurate.

​
How AI pricing matching reduces errors

Without per-customer pricing rules, a team member reviewing an order has to look up the correct price externally — in a contract document, a spreadsheet, or their memory — and compare it manually to what the customer submitted. That process is slow and error-prone, especially across dozens of customers with different rates. With StackCube’s pricing rules in place, the AI does that lookup automatically for every single line of every incoming order. Your team only needs to act when something doesn’t match. The comparison becomes the exception, not the routine.
Build out your pricing rules before you connect your first order channels. The AI matching step is only as useful as the rules it has to check against. Starting with complete rules means your first batch of candidates arrives in the review queue with pricing already verified.

​
Customer portal and pricing visibility

When your customers log in to the StackCube order portal to submit orders or check order status, they see only their own pricing. The portal is scoped to each customer’s account — no customer can view the rates, order history, or details that belong to another customer. This isolation applies to pricing rules, order candidates, and approved order records alike.

​
Frequently asked questions

If there is no pricing rule configured for a given SKU and customer combination, the candidate line is flagged in the review queue for manual price verification. The absence of a rule never causes an order to be silently approved at the wrong price — it always surfaces for human review.
Each customer has a single active price list at any time, but individual SKU rules within that list can carry different effective dates. Use date-scoped rules to manage promotional rates, contract tiers, or seasonal pricing without needing to maintain separate lists manually.
Yes. From the customer’s pricing settings, you can export their current rules as a CSV file. This is useful for sharing with the customer for confirmation, reconciling against a contract, or importing into another tool.