Customer and product records

Customer records carry the account name, code, primary address, contact and channel. Product records carry the SKU, name, category, unit of measure, substitution choice and list price. Both belong to an operating organization. The Order Desk Agent chooses these records when entering an order rather than retyping a customer or product name into each transaction.

The order also names its owner, a Team Member linked to a User. That relationship connects a business assignment to a person who can sign in. Admin should check which team members are active and which organization each belongs to before assigning new orders.

• Customers. Keep the account identity, address and credit or eligibility note current for order entry and review.
• Products. Keep the SKU and unit of measure clear so line quantities and fulfillment quantities refer to the same item.
• People. Link each team member to an organization and user before making that person an order owner or reviewer.

Choose an authoritative source for customer codes and product SK us. Decide who can deactivate a customer or product, and how teams will handle open orders that still refer to the record. A customer’s credit and eligibility note is context for review; it is not a substitute for the review decision recorded on an order revision.

Agree how a product substitution may be requested. The catalog and each line both carry a substitution setting. The team should review those choices before allocating stock or promising a different item. The catalog also records whether inventory is tracked, but quantities on an order still need fulfillment evidence before the team treats the request as shipped.

For organizations, set the time zone and currency consistently. The order and product records use USD amounts, so finance should agree how any organization using another currency will enter and interpret those amounts. That decision belongs in the operating setup, before historical orders are imported.

Create a customer with a usable address and contact, then a product with a SKU and unit of measure. Put that product on a Draft order owned by an active team member. Ask Order Reviewer to inspect the customer note, address, SKU, ordered units and price alongside the order. Correct any master data error at its source, then confirm what happens to an order already in Review.

Repeat with a product whose substitution setting differs from the line’s setting. The reviewer and Fulfillment Coordinator should see the intended rule for this transaction. Keep the reason for any changed product visible with the order evidence rather than relying on a verbal agreement.

• My Customer Orders — The assigned owner sees orders tied to the customer and product records they use.
• Orders Awaiting Review — The reviewer checks customer and product context for confirmed orders.

Use order preparation to check master data in a real transaction.