Customer Imports and Signup Requests#
When you manage many customers, start with CSV import in Customers. Customer data drives order matching, assignee filters, price tiers, portal login, and delivery details.
CSV Fields#
The import flow uses header mapping, so existing spreadsheet headers can be connected to StackCube fields during upload.
Important fields include customer code, customer name, internal assignee, login ID, login password, business registration number, use status, representative name, phone, fax, mobile, contact email, postal code, address, and memo.
When creating a new portal login ID, include an initial password. For updating an existing customer's login ID, the password can stay blank unless you intend to reset it.
Import Modes#
| Mode | Behavior |
|---|---|
| Create only | Stops if an existing customer code is found. |
| Skip existing | Adds only new customers and leaves existing customers unchanged. |
| Add and update | Updates matching customer codes and creates new ones. |
| Update existing only | Updates only existing customer codes and skips new rows. |
Use Create only for initial migration tests and Update existing only for operational corrections. Mixed create-and-update files have a larger blast radius, so review the preview rows carefully.
Internal Assignees#
The internal assignee column matches a team member by name or email. Email is safer when multiple people share a similar name.
Assigned customers can be filtered in the order list. Assignee assignment is a routing aid, not an approval rule.
Portal Accounts#
For repeat customers using the order portal, set login ID and password on the customer row.
Share portal credentials only after visible items and price rules are ready. Disable or remove portal access for inactive customers.
Signup Requests#
If customers request access from the portal, process them in the Signup requests tab in Customers. Review the company details, contact information, requested login ID, duplicate customer risk, assignee, and price tier before approving.
Approving creates the customer profile and portal account. When rejecting, leave an internal review note so repeated requests have context.