Customers and Products

Commerce Operator selects a customer using the name, code and contact details. The customer belongs to a retail organization and carries an active state and eligibility note. These facts help the operator establish who the order is for before discussing a size recommendation or preparing a payment request.

Catalog Manager maintains apparel products with their SKU, name, base unit and standard USD price. The product identity needs to remain clear when a sales line is prepared and when fulfillment records refer to the garment being handed over. A recommendation makes sense only when the team and customer understand the product context.

• Customer context. Keep the customer code, address and eligibility note with the correct organization. Check that the selected customer is active before preparing an order and its related assessment.
• Product identity. Use a recognizable SKU and product name. The base unit describes the quantity being sold or handed over, while the standard price gives the operator a reference for preparing the order line.
• Assigned responsibility. The order owner identifies the Commerce Operator handling the transaction. Admin maintains the person’s authenticated team identity so review and execution can resolve who is acting.

Agree how customer records are created and maintained, including how the team resolves duplicate names. Decide which information belongs in the eligibility note and who may see it. Keep measurement information within the consent and access arrangements established for the assessment.

Review the product catalog before importing sales lines. Agree SKU spelling, base units and the size wording used when discussing each product. Standard product and order amounts use USD, so confirm that operating basis even when the organization has another currency setting. Define how Catalog Manager communicates a corrected price or product identity to the people preparing orders.

Use a customer shopping for a jacket. Commerce Operator confirms the customer code and organization, then selects the intended apparel product for the order line. Catalog Manager checks the SKU, base unit and standard price used in the discussion.

During rehearsal, use similarly named customers in different organizations. Confirm that the operator cannot carry the wrong customer into the order and assessment. Then select an inactive product or a mistyped SKU and resolve the issue before the priced sale is accepted.

Finish the case by reviewing the proposed size wording with the garment in view. A size label needs an agreed product meaning; the customer and reviewer should not have to infer which garment the estimate concerns. Begin the pilot with a simple order whose product context everyone can follow, then expand after the identity handoffs are clear.

• Customer Register — Active customer records show contact and eligibility context within the organization.
• Apparel Catalog — Active products show SKU, base unit and standard USD price for order preparation.
• My Sales Orders — Assigned orders keep the customer and current order state visible to the operator.

Continue through sale preparation and acceptance and consented fit review.