Handle review exceptions#

When the same review error repeats, update the customer or item setup. Leave an order pending when you cannot confirm how it should be handled.

StackCube review flags and approval controls — Check review flags, order amount, order state, approval, and rejection controls before fulfillment.

Unknown customer#

Orders from unregistered senders are still received without an assigned customer. Open the order and select an existing customer, or create one when you need repeat-order recognition, customer pricing, or ERP export.

If StackCube shows Check customer because several records conflict, choose the correct customer before approval. Check whether the customer exists under another name, whether the buyer used a new email or phone number, and whether the order belongs to a related branch.

Unmatched item#

Do not approve a line when the item affects shipment and the match is uncertain.

Use the source message, attachment, prior orders, and catalog aliases to decide whether to correct the line, reject the order, or leave approval pending. After a repeated correction, add the alias to the catalog instead of fixing the same line again.

Price mismatch#

Correct an obvious typo in the order. If reviewers keep changing the same price, check whether the customer's price tier or rule is missing or outdated.

Before approving, compare the submitted price, the configured item or tier price, and the sales agreement. Record which price to use so the next reviewer does not need to ask again.

Duplicate-looking orders#

Hold the order when the same customer, same item, and similar quantity appear close together.

Check the original message and any follow-up messages. Some duplicates are corrections, but some are intentional repeat orders. Approve only when the source evidence makes the intent clear.

Failed AI analysis#

Select Analyze again from the order menu. The order cannot be edited or approved until analysis finishes. If the same source keeps failing, confirm that its attachment opens and contact support with the order number.

When to reject#

Reject instead of editing when the source is not an order, the customer cancels, the item cannot be identified, or the order cannot be shipped as requested.

Add a reason another reviewer can understand. A memo may appear in a carrier export, so do not include sensitive internal information.

When the same exception repeats#

At the end of each day, group repeated exceptions:

Add customer aliases or contact links for repeated unknown sender issues.
Add item aliases for repeated unmatched item names.
Update customer price tiers or tier rules for repeated approved price overrides.
Adjust channel instructions when customers keep sending incomplete orders.