Skip to main content
Once StackCube’s AI intake has processed an incoming order, the resulting candidate lands in your review queue — alongside every other order from every other channel your team operates. Instead of switching between an email inbox, a chat window, and a shared spreadsheet to track what has come in, you work from a single list. Each candidate shows you exactly what the AI extracted, what it matched, and what it flagged, so your team can move through approvals quickly and confidently without hunting for context.

​
The unified review queue

Every connected channel — email, chat, portal submissions, and file uploads — feeds the same queue. Orders appear in the list as soon as the AI has finished processing them. You do not need to monitor individual channels or consolidate inputs manually; StackCube does that aggregation for you.

All channels, one screen

Email threads, chat messages, PDF attachments, and spreadsheet uploads all appear in the same list. No channel is treated differently.

AI-prepared candidates

Each entry in the queue is a structured order candidate with extracted fields, SKU matches, and pricing verdicts already applied — not a raw message you have to parse yourself.

Source evidence preserved

The original email thread, chat message, or file attachment is retained alongside each candidate so you can verify the AI’s extraction against what the customer actually sent.

Searchable order history

Approved and historical orders remain in the system and are fully searchable, giving you a complete auditable record of every order processed through StackCube.

​
Order statuses

Each candidate and individual line item carries a status that guides your review priority.
StatusWhat it means
OrganizedThe candidate is fully extracted, SKU-matched, and priced. It is ready to approve without changes.
ReviewOne or more fields need a human check before the order can be approved.
SKU matchThe AI could not confidently resolve an item to a catalog SKU. Assign the correct SKU before approving.
PendingThe candidate is waiting for further input or is part of a multi-step approval workflow.

​
Reviewing and approving an order

1

Open the candidate

Select an order candidate from the queue. You will see the full extraction: customer identity, line items, quantities, and submitted pricing, alongside the AI’s match results and any flags.
2

Check the SKU matches

Review each line item’s resolved SKU. For lines with a SKU match status, search your catalog and assign the correct SKU. Once all lines are resolved, the SKU flags clear.
3

Verify pricing

Confirm that the pricing on each line aligns with the customer’s configured pricing rules. Lines where a discrepancy was detected are highlighted for your attention. Correct the price or accept the override before proceeding.
4

Review the source evidence

If any extracted field looks unexpected, open the attached source — the original email, chat message, or file — to compare it directly against the candidate. This lets you catch extraction errors before they reach an approved order.
5

Approve lines or the full order

Approve individual line items as you clear them, or approve the entire order at once when all lines are resolved. Approved orders move to order history and become available for carrier CSV download.

​
Working with order evidence

Every order candidate in StackCube retains a direct link to its original source. For email orders, that means the full email thread. For chat orders, the original message. For file-based orders, the uploaded attachment. This evidence is stored with the order record and remains accessible after approval, giving you a complete audit trail from raw input to approved order.
After approval, orders do not disappear — they move into order history where they remain searchable and auditable.
You can search order history by customer name, order reference, SKU, date range, and approval status. Use history to look up past orders when a customer queries a delivery, to reconcile invoices, or to audit how a specific order was processed.
Approved orders are locked to preserve the audit trail. If a correction is needed after approval, contact your account team or use the order amendment workflow available in your plan settings.
If StackCube’s AI detects a potential duplicate — same customer, same items, close submission timestamps — the candidate is flagged in the review queue. Review the source evidence for both candidates before deciding which to approve and which to dismiss.
Approving an order is a final action within the review queue. Before you approve, confirm that all SKU matches are correct and all pricing has been verified. Downstream processes, including carrier CSV export, are based on the approved order data.