Order portal#

The order portal is for repeat B2B customers who should place orders from a prepared catalog instead of sending free-form messages. It combines customer login, catalog visibility, customer-specific pricing, order submission, order history, and signup requests.

How the Order Portal Works#

Basic flow:

1. Configure the portal address and display name in Channels.
2. Prepare portal-visible items, options, and price tiers.
3. Customers request access from the portal, or operations creates portal login accounts in advance.
4. When operations approves a signup request, StackCube creates the customer profile and login account.
5. The customer logs in, adds catalog items to the cart, enters delivery details, and submits the order.
6. StackCube recalculates customer pricing server-side and creates a pending approval order.
7. The customer can check pending, approved, and rejected orders in Order history.

Portal orders are not automatically approved. Review item, quantity, price, delivery information, and duplicate risk in the order list before fulfillment.

What Customers Can Do#

Customers can use the portal to:

• Request access
• Log in and change password
• Update profile, contact, and delivery information
• Search portal-visible items
• Select options, add items to the cart, and submit orders
• Review their own order history and line details
• See order status changes

Accounts can be created directly in customer management or by approving a portal signup request. If the customer already exists, approval can connect a login account to that customer.

Signup Approval#

When a customer requests portal access, the request appears in the Signup requests tab in Customers. Operations can approve or reject it after review.

Review before approval:

• Company name and business registration number
• Contact name, mobile number, and email
• Requested login ID duplication
• Duplicate customer risk
• Customer code
• Internal assignee and price tier

Approving creates the customer profile and portal login account. When rejecting, leave an internal note so repeated requests have context.

For customer imports and signup processing, see customer imports and signup requests.

Customer-Specific Pricing#

Portal prices are calculated from the customer profile and price tier. The same item can show different prices for different customers, and submitted portal orders are recalculated on the server before order lines are saved.

Setup sequence:

1. Enter default item prices.
2. Create price tiers such as VIP, distributor, or wholesale.
3. Assign price tiers to customers.
4. Add fixed-price or discount rules for each tier.
5. Log in as a test customer and confirm portal prices.

For tier setup and rules, see customer-specific pricing.

Order History#

After login, customers can open Order history and review their own orders. The portal shows pending approval, approved, and rejected orders. Expanding an order shows line details and status history.

Because customers can see order status, keep status changes, rejections, and memo practices consistent.

Payment and PG Integrations#

The standard order portal flow creates a pending approval order. Customer checkout payment is not part of the default submission flow. If you add card or bank-transfer payment, design it separately from the portal rollout and align it with approval, tax invoice, credit, and monthly settlement policies.

Before adding a PG/payment flow, define:

• Whether payment is required before order submission.
• Whether payment links are sent after operations approval.
• Whether customer credit, tax invoice, or monthly settlement should stay in place.
• Where cancellation, partial shipment, and returns are handled.

Treat PG integration as a separate portal rollout decision, not a default prerequisite.

Setup Steps#

1. Choose the portal address and display name.
2. Enable order intake for the portal.
3. Decide whether prices are visible before login.
4. Choose list-style or grouped option display.
5. Confirm portal-visible items, images, and descriptions.
6. Prepare customer login accounts or the signup approval process.
7. Confirm customer price tiers and price rules.
8. Log in as a test customer and verify order submission and order history.

Manage portal address, pre-login price visibility, option display mode, and intake on/off in channel settings and intake history.

Good Rollout Pattern#

Start with customers who reorder frequently and have stable catalog and pricing rules. Keep email, KakaoTalk, SMS, or file upload available for customers who are not ready to change.

Do not open the portal to every customer at once. Start with a few customers whose catalog and pricing are already verified, then review signup requests, login issues, missing visible items, price tier errors, and order-history questions during the first week.