Review and approve orders#
The review queue is the center of StackCube operations. Every channel creates candidates, and reviewers decide what becomes an approved order.
Manual order registration#
Use manual registration when an order arrives by phone, in person, or through a channel you have not connected yet. In the order list, select Manual registration, choose the customer, enter item name, quantity, unit, unit price, and add a memo if the source needs context.
Manual registration creates a pending order in the same review queue as every other channel. Review and approve it normally; do not use it to bypass customer, item, price, or duplicate checks.
Manual Channel Intake#
The manual registration modal also includes tabs for channel-originated intake.
| Tab | Use when |
|---|---|
| Manual registration | You need to enter line items directly from phone or in-person orders. |
| Manual email | You need to paste email body text or attach files later. |
| Manual KakaoTalk | You need to preserve a KakaoTalk message as the source. |
| Manual SMS | You need to preserve an SMS message as the source. |
| Manual order portal | You need to open a selected customer's portal and place an order on their behalf. |
Preserving source text helps future reviewers understand why a candidate was created and improves exception analysis.
Assignee-based review#
When customers have internal assignees, use the assignee filter to split the review queue by owner. This is useful when sales or operations teams are responsible for different customer groups.
Treat the assignee as a routing aid. Pending approval, price checks, item checks, and duplicate checks still determine whether an order is safe to approve.
Filters and Selected Actions#
Use channel, date, assignee, and keyword filters to narrow the order list. These filters help with channel incidents, queue routing, and duplicate checks for a specific customer.
Selected orders can be used for carrier export or deletion. Deletion removes the order and its line items, so reserve it for test data or incorrectly generated candidates.
Review checklist#
Check these fields before approval:
- Customer match
- Item match
- Quantity and unit
- Item default or customer tier price
- Delivery date and notes
- Duplicate risk
- Source message or attachment
Line-level decisions#
Reviewers can edit order lines before approving the order. Use line-level correction when only part of an order is unclear.
Avoid approving an order if a shipment-affecting item, quantity, or price is unresolved. Reject or leave the order pending instead.
Detail Edits#
Order detail lets reviewers adjust order lines, memo, shipping information, currency, and status.
Use order memo for internal review context. Verify shipping information before carrier export. Change currency only when foreign-currency orders are expected. When changing status, check item, price, duplicate, and ERP precheck warnings.
If ERP-required fields are missing, fill customer code, item code, quantity, and related basics before approval whenever possible.
Approval policy#
Define who can approve orders. In small teams, the reviewer may also approve. In larger teams, require a second approver for high-value orders or new customers.
After approval#
Approved orders can be exported for carrier upload, entered into ERP, or used as an operations record. The source channel and review history stay attached to the order.
Quality loop#
Repeated corrections should become setup improvements. Add aliases, update customer price tiers or tier rules, or change review policy when the same exception appears often.
Use exception handling to decide when to correct, reject, or pause approval.