The question this page answers
Which source customers own the orders in a selected ERP connection and sales channel, and which Connect account should each business customer use?
What you see
Choose an ERP connection and Source channel before loading customers. The choices use recorded connection and channel identities. Channels opens the channel settings; its Reconcile action carries the selected channel. The NetSuite connector's Order reconciliation action carries its connection. Choose the remaining scope explicitly.
The review initially shows unclassified relationships and All customers, including individuals. Customer kind and Customer relationship narrow the page. Each customer row shows its source identity, relationship, observed orders and unattributed orders. These counts belong to the displayed rows. Next and Previous move through available pages; there is no asserted whole-book total.
What to do
Open Review to inspect source facts, mapped and unmapped lines, and suggested accounts. Select the relationship. A business customer can use an existing account or create an account with explicit commercial details. A shared sales channel can support several accounts through their separate source customer identities.
Where retained ERP role details are available, the review shows the customer category, status and current currency. Hover or focus these details to inspect the observation time and revision. The current customer currency does not replace recorded order currencies. Individual records require an explicit account name; an ERP role or buyer name does not assign an account. The name field distinguishes an ERP business name that was requested but absent from one that was not collected or retained.
Select Review impact, read the affected customer orders, add a mapping note and deliberately apply. A suggestion alone saves nothing. Open account orders opens a customer's existing Connect account history without requiring another mapping change. A classified row can be moved between kinds, with who and when shown.
The future demand route is a separate choice. When changing it, inspect its planning impact and managed-from date. Unknown remaining units stay unknown beside the known subtotal. Historical attribution does not approve a future forecast or order plan, and reviewing retained orders does not import duplicate orders.
If your role can only read, the row opens View and offers no apply action. Permissions and source revision checks remain authoritative when applying a mapping.
ERP customer categories
Below the review, ERP customer categories lists every category your ERP has reported for its customers, with how many customers carry it. Rule shows what Tightly reads from the category name: a Tightly Connect account, Direct, internal transfer, or by sales channel when no keyword reads it (each customer follows its own channel). Choose one of the three relationships to decide the category yourself, or Rule to hand it back. One choice covers every customer in the category and applies from the next sync; a customer you reviewed one by one keeps your review. If your role cannot classify customers, the choices are shown but cannot be changed.
When it is empty or failed
An incomplete scope asks for a connection and channel. An unavailable selected identity requires another selection. A failed connection, channel or customer read offers Retry and does not substitute an unscoped list. No customers in the selected view is an empty result rather than proof that every order has been reconciled.