Order channels#
StackCube supports multiple order channels because B2B customers rarely move to one process all at once. The goal is to capture orders where they already happen and review them in one place.
Supported channels#
| Channel | Best for |
|---|---|
| Email orders | Purchase orders in message body, PDF, or Excel attachment |
| KakaoTalk orders | Fast repeat orders and informal buyer messages |
| SMS | Short urgent orders from field teams or stores |
| Excel and PDF upload | Existing customer order forms |
| Private order portal | Repeat buyers with stable catalogs and prices |
Rollout order#
Start with the channel causing the most manual re-entry but the least customer change. For many teams that is email forwarding or upload.
Add customer-facing channels later, after the catalog and pricing rules are reliable.
Review queue behavior#
All channels feed the same review queue. A reviewer sees the extracted customer, line items, quantities, price checks, delivery notes, and source evidence.
The channel determines how the order enters StackCube. It should not change how the team approves orders.
Channel Settings and Intake History#
The Channels page manages email aliases, existing mailbox integration, portal URLs, KakaoTalk skills, SMS webhooks, and shared intake history. Before turning a channel on for customers, send a test event and confirm the original content appears in intake history.
See channel settings and intake history for detailed setup.
Choosing the first channel#
- Email ordersUse when purchase orders already arrive by email.
- KakaoTalk ordersUse when KakaoTalk repeat orders and photo orders are common.
- SMS ordersUse when field teams or stores send short text orders.
- Excel and PDFUse when buyers send fixed order forms.
- Order portalUse when repeat buyers can self-serve from a catalog.