Sale orders

A buyer purchases a print for shipment. The sale order retains the shopper, shipping address, selected method, currency, line quantity and price. Financial status and fulfillment status answer different questions: the first describes payment, the second describes delivery work. An order event gives support staff a dated explanation of important changes.

Customer Service Rep starts from the published Sale Orders workspace when a shopper asks about a purchase. Its filters and record detail show the same sale order population. Order items hold the purchased SKU, quantity and unit price; events explain later payment, shipment or cancellation changes without replacing the original order.

• Purchase. Read the order number, shopper, basket and purchased lines together before answering a question.
• State. Check financial, fulfillment and fraud statuses separately; each answers a different operational question.
• History. Follow the dated order events and linked shipment when a case changes after placement.

Agree who may cancel an order and which reasons the team will use. Decide how service staff identify a guest purchase by email and order number. Check that line discounts and shipping charges remain visible when comparing the order with a shopper receipt. Record a note or event when an exception needs follow-up.

During the pilot, assign the exception owner and record the decision on the related order or catalog. Check the next handoff against the saved status, date and linked records before more staff start using the process.

Open a paid order and follow its item, event history and shipment. Then inspect an order under fraud review and make sure it stays visible to the authorized service owner. Rehearse cancellation on a separate case so the team can see both the reason and its financial consequence.

Use the same case to rehearse access. Have the next owner explain the saved record, perform the permitted action and show the resulting status to the following owner. Correct a broken handoff before expanding the pilot.

• Open Sale Orders — Shows the cases and current status for this module’s owner.
• Orders Under Review — Separates cases that need a second check or decision.

See the operating process for the connected handoff. Implementation gives the pilot sequence, and roles sets access before people start editing records.