The packet is a decision file, not a persuasion memo
A partial-refund request usually arrives with emotion, urgency, and incomplete facts. The support specialist's job is to turn that into a decision file the owner can review without reopening five systems. The packet should state the customer's claim, the transaction facts, the evidence gathered, the policy that applies, and the decision requested. It should not argue for a refund before the facts are checked. A Philippines-based ecommerce specialist can collect the order record, the payment status, the fulfillment timeline, the carrier events, and the customer's messages. The specialist should not promise a refund, issue a credit, or tell the customer that the case will be approved. Those actions belong to the named owner or the approved refund workflow.
Start with the transaction and the promise
Record the order identifier, the items and quantities, the amount paid, the shipping method, the promised delivery window, and the date the customer contacted support. The promised window matters because a delay claim depends on what the store actually committed to, not on what the customer expected. Use the order confirmation and the published policy that applied at purchase time. If the customer's claim is about a partial shipment, record which items arrived, which are missing, and what the packing record shows. If it is about condition, record the photos, the carrier damage note, and the return authorization. Keep the customer's own words in a short quotation rather than paraphrasing them into a conclusion. The owner needs to see the claim, not the specialist's summary of the claim.
Separate carrier, warehouse, and payment evidence
Carrier tracking shows movement, not necessarily correct delivery. Warehouse records show what was packed, not necessarily what arrived. Payment records show what was captured, not necessarily what the customer is owed. Keep these evidence streams separate and label the time zone and cutoff for each. A clean packet makes it obvious which link in the chain is missing. When the streams disagree, record the disagreement. A carrier scan may show delivery while the customer says nothing arrived; a warehouse record may show two units while the customer says one. Do not resolve the conflict by choosing the record that supports the easiest outcome. Route the conflict to the owner with the specific question that needs an answer, such as whether a carrier claim or a replacement is appropriate.
Calculate only what the policy allows
The specialist can reproduce the arithmetic for the item price, tax, shipping, discount, and prior partial credit. The specialist should not decide whether a restocking fee, return shipping cost, or promotional discount should be waived. Use the policy version that applied when the order was placed, and show the calculation line by line so the owner can check it. If the policy is ambiguous, say so. A packet that labels an ambiguity is more useful than one that hides it behind a confident total. Quote the relevant policy language and link to the full policy. If the customer has already received a partial credit, show it and explain whether the new request is for the remainder or for a separate issue. Avoid double-counting the same remedy.
Work a realistic partial-shipment case
A customer ordered four lamps and received three. The warehouse record shows four units packed, the carrier scan shows the package delivered at the stated weight, and the customer photo shows three boxes. The specialist records the order, the packing record, the carrier event, the photo, and the customer's request for a refund of one lamp rather than a replacement. The packet notes that the weight evidence does not by itself prove what was inside the package. The owner reviews the packet and decides whether to send a replacement, issue a partial refund, or open a carrier claim. The specialist records the decision, the amount approved, the date, and the customer communication. If the decision is a refund, the packet is linked to the payment transaction so the finance reviewer can confirm that the credit matches the approval. The case is not closed until the destination record shows the result.
Protect payment and personal data
Refund packets often contain names, addresses, order history, and partial payment details. Share only the fields the reviewer needs, and never place full card numbers, bank credentials, or identity documents in a chat or an unapproved attachment. Use the payment provider's approved interface for the actual refund. The specialist can prepare the request but should not handle raw payment credentials. The PCI Security Standards Council, the Federal Trade Commission, and the Consumer Financial Protection Bureau publish general guidance on payment security, fair commerce, and consumer complaints. These references do not replace the store's own refund policy, payment-provider rules, or legal review. When a case involves a chargeback, fraud signal, or regulated product, route it through the approved escalation path immediately.
Review packet quality weekly
Sample a small number of partial-refund packets each week. Check whether the claim was recorded accurately, whether all three evidence streams were addressed, whether the policy version was correct, whether the calculation was reproducible, and whether the decision was recorded with an owner. Look for packets that recommend an outcome before the facts are complete. A repeated defect may point to a missing system field, an unclear policy, or a template that invites narrative instead of evidence. Fix the template or the source access before coaching the specialist. Keep the approved packet and the decision record together so a later reviewer can test the same case from the same evidence.
Sources and limits
The Federal Trade Commission publishes the Mail, Internet, or Telephone Order Merchandise Rule and data-security guidance; the Consumer Financial Protection Bureau and the PCI Security Standards Council provide additional context on consumer complaints and payment security. These sources inform general practice and do not determine the correct outcome for a specific order. Sources: https://www.ftc.gov/legal-library/browse/rules/mail-internet-or-telephone-order-merchandise-rule https://www.ftc.gov/business-guidance/privacy-security/data-security https://www.consumerfinance.gov/ https://www.pcisecuritystandards.org/