Add and manage customers#

Customers connect incoming orders to the right pricing rules, portal pages, contacts, and review history. Create customer records before connecting high-volume channels.

StackCube demo customer list — Demo customer list with customer codes, names, account owners, portal login IDs, and contact fields.

Customer profile#

At minimum, keep these fields current:

Company name
Primary contact name
Email and phone number
Address and postal code
ERP or internal customer code

If your ERP already has customer codes, store them in StackCube so approved orders can be reconciled later.

Internal assignee#

Assign an internal owner when a customer usually works with a specific salesperson, operations manager, or fulfillment coordinator. The assignee appears beside that customer and is also available in the order review queue for filtering.

Use the assignee as an operating owner, not as automatic approval. The assigned person should know which orders they need to check, but the normal review and approval rules still apply.

Source recognition#

Keep the sender details that help StackCube resolve incoming orders to the right customer. A customer may submit orders through multiple channels, but the review queue should still resolve them to one customer profile.

Examples:

Email purchase orders from a buyer inbox
KakaoTalk messages from a store manager
Excel files from a distributor
Private portal orders from repeat buyers

Customer-specific pricing#

Use customer price tiers and tier rules for negotiated fixed prices, discounts, and special terms. This gives reviewers a configured price to compare before approval.

Keep the rule simple at first. Add exceptions only when the review queue shows repeat mismatch patterns.

Portal access#

For repeat customers, create a private order portal after portal-visible items and price rules are ready. A portal is most useful when the customer often reorders the same items.

StackCube customer portal and contact fields — Customer rows keep portal access, business registration, phone, mobile, and buyer email fields available for operations.

Do not force every customer onto a portal. StackCube is designed to support existing customer behavior and gradually reduce manual work.

If you already have a customer list or plan to accept portal signup requests, define the CSV import and approval workflow first. Import files can include customer code, name, internal assignee, login ID, contact details, and address.

See customer imports and signup requests for the detailed workflow.