Before receiving customer orders#

Completing the Start page does not mean every customer must move immediately. Run one or two customer orders through the full process first.

Order channel#

• A new test order appears in both Intake history and Order management.
• The sender, source text, and attachments are complete.
• Someone owns unknown senders and duplicate orders.
• Automatic and manual forwarding do not create the same order twice.

Order review#

• Reviewers can check the customer, items, quantities, prices, and delivery request.
• The team knows when to edit, reject, or hold an order.
• An approver and a backup approver are assigned.
• Reviewers do not need to reopen a personal inbox or messenger to find the source.

Items and customers#

• Common items for the first live customers are registered.
• Customer terms are added as aliases when they differ from catalog names.
• Units and pack sizes match fulfillment rules.
• Customers with price risk have a price tier or specific price rule.

Before sharing an order portal, also check visible items, prices, options, and customer login access.

Sending approved orders#

• The team knows how to send approved orders to the ERP or fulfillment team.
• Carrier CSV sender and recipient fields are correct.
• Re-export and resend rules prevent duplicate shipments.

First-week checks#

Review unmatched items, wrong customer matches, price edits, and duplicate orders every day during the first week. When the same correction repeats, update the item alias or customer record instead of fixing each order separately.

Connect a second channel after confirming that the first one receives every order correctly.