Get started with StackCube#

This guide covers the shortest practical path to a working StackCube setup. Start with sample data, then move to live order operations after the first channel and review flow are stable.

1. Review the sample flow#

Start with a sample workspace before changing any customer process. Confirm that the order queue, item matching, price check, approval, and CSV export flow matches how your team works.

Use the sample flow to answer three questions:

Which order channels create the most manual work today?
Which customers require special prices or item aliases?
Which carrier or ERP format should approved orders feed into?

2. Prepare operating data#

StackCube works best when the core operational data is clean enough for review.

Data	Minimum required
Items	SKU, item name, option, active status
Customers	Company name, contact, internal assignee, ERP code
Prices	Default prices, customer price tiers, or tier rules
Team	Admin users and reviewers

You can begin with a small catalog and expand after the first channel is stable.

3. Connect the first channel#

Choose one low-risk channel first. Email forwarding and spreadsheet upload are usually the easiest starting points because they do not require customers to change behavior.

After the first channel is connected, process several real examples end to end. Do not optimize every edge case before the team has approved a few orders.

4. Review and approve orders#

AI prepares order candidates, but your team confirms the result. Review customer match, item match, quantity, price, delivery note, and attachment source before approving.

Use rejection and correction patterns to improve item aliases, customer names, and price rules.

5. Go live#

Go live when the team can reliably complete this loop:

Order arrives from the selected channel.
StackCube creates a review candidate.
Reviewer fixes exceptions and approves.
Approved order is exported to the carrier or entered into ERP.
The order history remains visible to the team.